implementation-guide

To create an implementation plan from a feature description or PRD, input the scoped document to generate a phased execution guide with sequential goals, one-story-point tasks, and defined acceptance criteria for structured progress.

Breaking down a PRD into phased tasks involves decomposing work into sequential stages with clear rationale, generating small testable sub-tasks like 1.x and 2.x, and embedding testing considerations for measurable validation across product and engineering.

Ensuring traceability between project documentation and implementation phases requires aligning generated plans directly with the source PRD, maintaining built-in testing guidance, and specifying requirements to track measurable progress from discovery to validation.

Yes, you can use this approach to plan work across product and engineering teams. It transforms scoped feature descriptions into structured, actionable implementation guides that enable confident execution and cross-functional alignment.

Yes, the generated implementation guide includes acceptance criteria for every task. It decomposes work into small, testable units and incorporates built-in testing guidance to ensure measurable progress throughout each phase.