prd-implementation-planning

To turn an approved PRD into actionable tasks, this Skill deconstructs user stories into manageable, hour-sized work items, assigns specific AI skills, and estimates effort. It bridges product strategy and development execution by defining granular tasks, dependencies, and priorities directly appended to the PRD.

The best way to map user stories to development skills is by referencing a predefined skill catalog, such as a REFERENCE.md file. This Skill assigns specific AI skills to each generated task, ensuring the implementation plan aligns technical capabilities with the required work items.

Effort estimation works by assigning standardized sizes (XS, S, M, L, XL) to each implementation task derived from the PRD. Alongside priority levels (P0, P1, P2), these estimates help sequence the logical workflow and manage task dependencies for accurate project planning.

Yes, you can track development progress because the Skill initializes a tracking framework within the implementation plan. It sets up structures to monitor task status, start and completion dates, and commit hashes, ensuring continuous visibility after the PRD is approved.

Yes, you need a predefined task structure and skill catalog references for comprehensive project planning. The Skill requires adherence to these predefined structures to accurately break down user stories, map skills, estimate effort, and define logical task dependencies.

Defining task dependencies when converting a PRD ensures logical workflow sequencing for the development team. By mapping these relationships alongside effort estimates and priorities, the implementation plan facilitates a smooth transition from product strategy to execution.