prd-tasks

To generate tasks from a PRD, you provide an approved Product Requirement Document file path. The skill parses the requirements, performs codebase pre-research, and outputs structured individual task files in a designated directory.

Breaking down large user stories is handled by parsing the approved requirements document and splitting the content into granular, actionable task files. Each task file includes specific acceptance criteria, implementation notes, and dependencies.

Yes, updating PRD status in an index file is supported during task generation. When the skill parses requirements and creates individual task files, it also updates the tracking index to reflect the new workflow state.

Yes, an approved Product Requirement Document is required. The skill specifically parses approved PRD requirements to ensure the generated task files represent finalized implementation goals ready for development.

Yes, the task generation process performs pre-research on codebase specifics. It analyzes your existing codebase before creating structured task files to ensure the generated development tasks align with your current architecture.

The generated task files follow a structured, detailed format. Each file represents a specific requirement or user story and includes consistent sections for acceptance criteria, implementation notes, and dependencies.