/grow

Create a pi skill named `grow` (invoke with `/grow`) that runs the prospective growth ritual — maintaining two images of the system, as it is and as intended, and deriving proposed goals from their diff.

Write the skill as a directory at `~/.pi/agent/skills/grow/` containing exactly one file: `SKILL.md`.

The SKILL.md must have this frontmatter:

---

name: grow

description: Runs a prospective ritual — updates a self-documented image of the system as it is, compiles the user’s expressed intent into an image of the system as intended, and derives proposed goals from the diff for the user to ratify. Use only when the user invokes /grow. Rare and manual; compiles expressed intent only, never generates desire.

---

The body of SKILL.md must contain:

1. A “Scope” section with clear rules:

- Prospective only: grow models what the system is and should become. It never conducts retrospectives — that is /learn’s territory.

- It compiles intent the user has actually expressed — in conversation, memory, diary, standing documents. It never invents a goal or a want of its own.

- Every goal is a proposal until the user explicitly ratifies it in dialogue.

- Manual invocation only, at a rare cadence — weeks, not days.

2. A “Two Images” section with clear rules:

- The images live at `~/.pi/agent/memory/image-current.md` and `~/.pi/agent/memory/image-intended.md`. They are owned by grow; the remember ritual does not load them at startup.

- Both files share one identical skeleton, in this order: Identity & Purpose; Capabilities (one line per skill); Memory (stores and their contracts); Rituals & Loops; Environment & Interfaces; Tensions & Limitations.

- Every section is written as claims about the system, one claim per line, so that the diff between the two images is line-granular and meaningful section for section.

- image-intended.md carries one extra final section, “Delta”, holding proposed goals not yet ratified.

3. An “Update the Current Image” section with these exact steps in this order:

- Survey the actual system: the skills directory, the memory stores including semantic memory’s accumulated lessons, AGENTS.md, recent diary, the git log.

- Update image-current.md by incremental deltas: edit the lines that changed, add lines for what is new, delete lines for what is gone. Never redraw from scratch.

4. An “Update the Intended Image” section with these exact steps in this order:

- Gather expressed intent from the user’s own words: this conversation, diary, memory, standing documents. Where intent is ambiguous or stale, ask the user rather than infer.

- Compile it into the same skeleton by incremental deltas.

5. A “Derive the Delta” section with these exact steps in this order:

- Diff the two images section by section.

- Translate each material difference into a candidate goal: one line, concrete enough to hand to /build.

- Present each candidate with its reasoning. The user ratifies, amends, or rejects, one at a time.

- Move each ratified goal to working memory as an open thread for /build. Delete rejected goals. Leave the rest in the Delta section.

6. A “Close” section with these exact steps in this order:

- Read back the diff of both images and the disposition of every goal.

- Commit with the message “grow: <YYYY-MM-DD>”.

7. A final “Golden Rules” section repeating this exactly three times, one per line:

- If in doubt, ask. Never invent a want the user has not expressed.

- If in doubt, ask. Never redraw an image when a line edit will do.

- If in doubt, ask. Never treat a goal as ratified without an explicit yes.

8. Every memory path must be exact as shown above, and the ritual order — Current Image, Intended Image, Delta, Close — is exact and literal. Do not reorder, merge, or skip.

Write the directory and file, then verify the skill exists at `~/.pi/agent/skills/grow/SKILL.md`.