generate-task-breakdown

To generate development tasks from product requirements, this skill transforms your PRD and architecture documents into organized epics and manageable tasks with acceptance criteria. It outputs structured task lists directly into your docs/tasks/ directory.

The best way to break down large features into manageable tasks is by parsing product requirements to generate specific models, services, and UI components. This approach ensures every generated task includes clear acceptance criteria for agile development.

Progress tracking for development roadmaps works by creating structured files in docs/progress/ that monitor task status, commits, and blockers. This mechanism ensures your implementation plan remains trackable throughout the development lifecycle.

Yes, you can use this task breakdown approach for Scrum project planning because it structures work into epics and tasks with acceptance criteria. It supports agile methodologies by creating structured task lists and progress tracking files.

Yes, you need architecture documentation and product requirements to create a development roadmap. The skill relies on these input documents to accurately organize work into epics and generate executable development tasks.