issue-decomposer

To decompose a PRD into implementation-ready issues, paste the product request or feature description into the Skill. It breaks the document into small, scoped issues with explicit dependencies, acceptance criteria, and file-level context for coding models.

Issue decomposition in software engineering planning is the process of breaking down feature requests into sequenced tasks. This Skill resolves vague scope by grilling requirements, producing handoff-ready text with clear contracts, interfaces, tests, and validation stopping points.

You prepare vague feature requests for engineering handoff by using the Skill to ask clarifying questions that resolve missing contracts and unsafe assumptions. It tightens the scope into explicit draft issues containing required files, interfaces, and risks for safe execution.

Yes, you can use decomposed issues for smaller coding models. The Skill drafts implementation issues with enough explicit detail, file-level context, and validation stopping points that a coding model can execute the work without needing the original planning conversation.

For safe issue execution, you need explicit contracts, file-level context, tests, and validation stopping points. The Skill ensures drafted issues contain these elements, alongside clear scope and dependencies, to prevent unsafe assumptions during implementation.

The limitation of automated PRD decomposition is that it requires explicit contracts and clear scope to function safely. If the original product request lacks detail, the Skill must first ask clarifying questions to resolve vague requirements before drafting any implementation issues.