pre-dev-subtask-creation

You create zero-context subtasks by generating documents with exact file paths, test scaffolding, verification commands, and rollback instructions. This ensures engineers can execute tasks autonomously without prior codebase knowledge.

Yes, you can generate TDD-aligned subtasks that enforce a complete red-green-refactor cycle. Each subtask document includes concrete code, commands, and verification steps to guide the test-driven development process from start to finish.

The best way to break down large features is to generate bite-sized, atomic subtasks with header-defined metadata. This enforces explicit file paths, commit steps, and rollback instructions within each document for precise execution.

No, you do not need to manually specify file paths and commit steps. The subtask generation enforces header-driven templates that automatically include exact file paths, test scaffolding, verification commands, and commit steps within each document.

You should store subtask documentation in the docs/pre-dev/ directory. Committing the generated subtask documents to this location ensures they are integrated into your automated workflow and accessible for execution.

A limitation is that the automated subtask generation relies on strict template adherence, requiring exact file paths and test scaffolding. Complex workflows may need manual adjustments if the zero-context assumptions do not fit highly coupled codebase architectures.