Plan Runner

Use the plan file as the working progress tracker. Continue the next clear task, update the file as work happens, validate when practical, and stop when complete, blocked, or a decision is needed.

Workflow

1. Read the plan file first.

   • If no plan file is provided or the target is ambiguous, ask for the exact file.
   • Treat the plan as authoritative unless repository evidence proves it is stale.

2. Inspect current state before editing.

   • Check git status and relevant diffs so unrelated user work is not mixed into the run.
   • Read only the files needed for the next clear plan item.

3. Execute one coherent progress slice.

   • Prefer small, safe, validated changes over broad rewrites.
   • If the next step needs a product, design, or ownership decision, ask before continuing.
   • If missing requirements block progress, ask for the specific information needed.