implement-next-phase
Invoking this skill
Use when the partner attaches this skill and provides the sketch plan path. That plan includes YAML todos (one per phase, each content matches the corresponding ### Phase N - … heading in ## Sketch) plus a ## Sketch section in the file body.
Non-negotiable: Until the partner explicitly approves proceeding (for example: "go ahead," "implement," "proceed with Phase 2"), you do not edit application code, tests, config, or assets for the work. Preparation (reading, searching, analysis, questions) is allowed; building is not, until that approval.
Chat during preparation: Do not deliver a research report, findings recap, or summary of what you learned. Do not restate or summarize the sketch, the plan, or the codebase in chat. The partner already has the plan. In chat, write only: concise questions when something blocks you or is unclear; brief asks when the plan or todos need fixing; and—when you have no further questions—a single short line requesting approval to implement, naming the active phase by its todo content (for example: ready to implement Phase 1 - … when you approve). No other preparation prose in chat.
Git staging (before each phase cycle)
Every time this skill starts a fresh phase cycle—the first pending phase in the plan, or the next pending phase after earlier ones were implemented—run git add -A, then read and prepare. Do not commit. Do not begin step 1 below until staging is done.
This checkpoints work from the prior phase (or any other unstaged edits) before new preparation or implementation begins.