Remove pi specific content from README

This commit is contained in:
2026-08-21 02:51:38 -04:00
parent 170bc6de66
commit 27d78bd5ec
+9 -19
View File
@@ -1,6 +1,10 @@
# pi Skills # Skills
This directory holds custom skills for [pi](https://github.com/earendil-works/pi), a coding agent harness. Each skill adds specialized capabilities that extend what pi can do. A collection of reusable agent skills that extend an LLM coding assistant's capabilities. Install any skill by cloning or symlinking it into your agent's skills directory — for example, for pi:
```bash
git clone https://github.com/user/my-skill ~/.pi/agent/skills/my-skill
```
## Current Skills ## Current Skills
@@ -10,20 +14,6 @@ This directory holds custom skills for [pi](https://github.com/earendil-works/pi
| [find-skills](./find-skills/) | Discovers and installs new skills | | [find-skills](./find-skills/) | Discovers and installs new skills |
| [gog](./gog/) | Google Workspace CLI (Gmail, Calendar, Drive, Contacts, Sheets, Docs) | | [gog](./gog/) | Google Workspace CLI (Gmail, Calendar, Drive, Contacts, Sheets, Docs) |
## Adding a Skill
To install a skill from elsewhere, clone or symlink it into `~/.pi/agent/skills/`:
```bash
git clone https://github.com/user/my-skill ~/.pi/agent/skills/my-skill
```
Or for development:
```bash
ln -s /path/to/my-skill ~/.pi/agent/skills/my-skill
```
--- ---
## phased-execution ## phased-execution
@@ -32,7 +22,7 @@ Runs phased build pipelines in isolated subprocesses. Ported from [opencode](htt
### Overview ### Overview
This skill orchestrates a project's development as a sequence of phases, each executed by the LLM in its own fresh pi process. Phases are managed via files — not chat context — so even very long-running pipelines don't bloat your session history. This skill orchestrates a project's development as a sequence of phases, each executed by the LLM in its own fresh process. Phases are managed via files — not chat context — so even very long-running pipelines don't bloat your session history.
Each phase: Each phase:
1. Reads the master plan (`.agent/PLAN.md`) and any already-completed phases 1. Reads the master plan (`.agent/PLAN.md`) and any already-completed phases
@@ -52,7 +42,7 @@ Each phase:
│ │ ├── todo/ # Pending phases: 01_name.md, 02_name.md, … │ │ ├── todo/ # Pending phases: 01_name.md, 02_name.md, …
│ │ └── complete/ # Finished phases │ │ └── complete/ # Finished phases
│ ├── reports/ # Per-phase executor reports, stderr, validation logs │ ├── reports/ # Per-phase executor reports, stderr, validation logs
│ └── phase-sessions/ # Resumable child pi sessions │ └── phase-sessions/ # Resumable child sessions
``` ```
### Usage ### Usage
@@ -99,7 +89,7 @@ PHASE_MODEL=anthropic/claude-sonnet-4-5 PHASE_COMMIT=1 bash ~/.pi/agent/skills/p
### How It Works ### How It Works
1. `run-phase.sh` / `auto-phase.sh` finds the project root (walks up from `PWD` for `.agent/phases/todo/`) 1. `run-phase.sh` / `auto-phase.sh` finds the project root (walks up from `PWD` for `.agent/phases/todo/`)
2. For each phase, it spawns a **separate pi subprocess** with `--mode json` to capture structured output 2. For each phase, it spawns a **separate process** with `--mode json` to capture structured output
3. `progress.mjs` streams live progress (tool calls, assistant text) to the terminal and writes the final report to `.agent/reports/` 3. `progress.mjs` streams live progress (tool calls, assistant text) to the terminal and writes the final report to `.agent/reports/`
4. After the child exits, `.agent/validate.sh` is run as the quality gate 4. After the child exits, `.agent/validate.sh` is run as the quality gate
5. On success: phase moves to `complete/`, report is printed 5. On success: phase moves to `complete/`, report is printed