plan-task
Take one task from the current slice's task list and turn it into a concrete plan: which files to touch, what code to write, how to verify. Output lives at M###-S##-T##-PLAN.md.
Anti-Pattern: "The task summary is enough, I'll figure out files during execution"
No. Tasks without pre-committed file paths drift. An agent (human or AI) asked to "add signup form" will discover mid-stream that the form lives in three different places and pick the wrong one. File paths in the task p
[Description truncada. Veja o README completo no GitHub.]