spec

To convert vague product requests into structured PRD documents, this skill decomposes user requirements through a phase-based workflow, enforcing a reusable template that clarifies development direction and reduces engineering communication gaps.

The phase-based workflow for writing product requirement documents spans from Phase 1 context collection to Phase 6 PRD completion, systematically distinguishing and documenting requirements to produce a comprehensive draft.

Yes, you can use this skill to break down a PRD into repository issues. It automatically prepares handoff documents and decomposes requirements to guide build, QA, and docs stages with clear data definitions.

To include acceptance criteria and exception handling policies in a specification, this skill enforces boundary rules, rejection and approval judgment criteria, and exception processing policies directly within the generated PRD template.

Yes, this PRD generation skill works for both solo product owners and development teams who need formalized requirements, templates, and issue breakdowns to guide planning, development, and governance.