implement

Implement

Execute an implementation plan created by /create-plan. Read the plan thoroughly, execute each step in order, and report on the completed work.

Variables

plan_path: $ARGUMENTS (path to the plan file, e.g., plans/2026-01-28-add-guest-research-command.md)

---

Instructions

Phase 1: Understand the Plan

1. Read the plan file completely. Do not skim — understand every section.
2. Verify prerequisites:
   • Are there open questions that need answers before proceeding?
   • Are there dependencies on external resources or user decisions?
   • If blockers exist, stop and ask the user before proceeding.
3. Confirm the plan is ready:
   • Status should be "Draft" or "Ready"
   • All sections should be filled out (no placeholder text remaining)

---

Phase 2: Execute the Plan

1. Follow the Step-by-Step Tasks in exact order.

   • Complete each step fully before moving to the next
   • If a step involves creating a file, write the complete file — not a stub
   • If a step involves modifying a file, read the file first, then apply changes precisely

2. For each task:

   • Read any files that will be affected
   • Make the changes specified
   • Verify the change is correct before proceeding

3. Handle issues gracefully:

   • If a step can't be completed as written, note the issue and adapt if the intent is clear
   • If you're unsure how to proceed, ask the user rather than guessing
   • Document any deviations from the plan

---

Documentation Check

After completing each implementation chunk:

1. Check if the changes created a new system or significantly modified an existing one
2. Read docs/_index.md — does a doc exist for this system?
3. If no doc exists and the changes are significant (new system, new command, new integration):
   • Create one using the template in docs/_templates/
   • Add an entry to docs/_index.md
4. If a doc exists but is now stale:
   • Update the relevant sections
   • Add a dated entry to the doc's History table
5. Update HISTORY.md with what was implemented
6. Commit the documentation updates: docs: update documentation for {system}