Create an implementation plan

Create an implementation plan

Produce the artifact a human will review and approve. Input (ticket ref / research path): $ARGUMENTS

Be skeptical and thorough. Work with the user — ask questions when the ticket or research is ambiguous rather than guessing.

Steps

1. Read the ticket and the research document(s) in thoughts/shared/research/ fully.
2. Read every code file the research references so the plan is grounded in reality.
3. Draft the plan as a sequence of phases. Each phase has:
   • Changes — the specific edits/files involved,
   • Success criteria, split into:
     • Automated — exact commands (tests, typecheck, lint, build),
     • Manual — what a human should click/observe.
4. Write it to thoughts/shared/plans/<slug>.md with checkboxes (- [ ]) per phase so the implementer can tick them off.
5. Stop here. Present the plan path and a 3-line summary, then ask for approval:

   Plan ready: thoughts/shared/plans/<slug>.md
   Approve to implement, or tell me what to change.
   

Catching a misunderstanding here — before any code exists — is the entire point.