do-create-tasks

To break a PRD and Tech Spec into actionable tasks, provide the feature slug to generate a structured, incremental task plan. The system creates a tasks.md file and individual numbered task files with clear dependencies and test suites for user approval.

Structuring implementation tasks with tests involves generating a sequenced list of executable steps directly from project documentation. This creates traceable task files that enforce directory structure and naming rules while including specific unit and integration test requirements.

Generating a task plan without runtime execution requires parsing PRD and Tech Spec documents to produce static markdown files. The system outputs a high-level task list for explicit user approval before creating any files, ensuring no code is executed during planning.

Yes, you can enforce specific directory structures and file naming conventions for task planning. The system automatically generates outputs under a strict ./prds/prd-[feature-slug]/tasks/ path, creating a tasks.md file and numbered _task.md files to maintain project consistency.

Yes, user approval is required before individual task files are created. The system first presents a high-level task list generated from the PRD and Tech Spec, waiting for your confirmation before writing the tasks.md and numbered task files to the directory.