pre-dev-subtask-creation

To break down large engineering features into zero-context subtasks, use a fixed template that generates granular, 2-5 minute steps with exact code, commands, and tests, allowing any engineer to execute without prior domain knowledge.

The best way to structure subtasks for strict TDD cycles is to apply a fixed template supporting RED-GREEN-REFACTOR phases, providing explicit verification and rollback guidance alongside exact code commits for each step.

You can create zero-context subtasks by filling a fixed template with the Title, Agent Note, Goal, Prerequisites, Files, and Step structure, ensuring every incremental task includes exact code and commands for autonomous execution.

Yes, this process works for large features requiring defined incremental steps by breaking the work down into 2-5 minute gated, repeatable tasks with exact code, commands, and commits.

You need a fixed template for engineering task breakdown when strict TDD, clear verification, and incremental steps are required, ensuring granular subtasks with complete code enable autonomous work without domain knowledge.