Shepherd

Use Shepherd for long autonomous builds. Keep it simple: approved spec, approved plan, verified milestones, final proof.

When To Use

• Use when the work spans multiple milestones, hours, or days.
• Use when the user asks for autonomous end-to-end delivery.
• Do not use for one-shot fixes, single-file edits, short debugging sessions, or work that needs approval after every small step.

Workflow

Setup:      intent -> spec -> review -> verification -> standards -> plan
Milestone:  select -> implement -> refactor -> evidence -> QA -> architect -> close
Finish:     final QA -> final architect -> validators -> cleanup/report

Advance only when the current stage has proof. If proof is missing, repair, waive, or stop.