generate-task-breakdown

Task breakdown from PRDs involves transforming high-level product requirements and architecture documents into detailed epics and tasks. This Skill automates that process by generating markdown files with clear acceptance criteria and progress tracking mechanisms.

Setting up progress tracking for agile epics involves creating structured files to monitor task status. This Skill generates a docs/progress/ directory alongside docs/tasks/ to track the development lifecycle and define clear deliverables for iterative development.

Yes, generating a task breakdown from architecture diagrams and a PRD is the core function. The Skill reads these documents to produce structured markdown files in docs/tasks/ and docs/progress/, detailing specific tasks like implementing authentication middleware or designing database schemas.

Yes, this task breakdown approach works without external dependencies. The Skill operates independently to parse your documentation and generate the structured markdown files required for project planning and execution.

The best way to organize development tasks from requirements analysis is structuring them into epics with granular tasks and acceptance criteria. This Skill creates dedicated docs/tasks/ and docs/progress/ files to ensure clarity and efficient execution.

You should not use automated task breakdown when you lack existing product requirements or architecture documentation. The Skill requires these inputs to generate actionable development tasks and set up progress tracking mechanisms effectively.