request-to-prd

To turn a rough bug report or feature request into a structured PRD, paste the informal request text into the skill. It classifies the intake, extracts core problems and constraints, and outputs a first-draft product requirements document with functional requirements and testing decisions.

Issue decomposition for product intake is the process of breaking down informal bug reports or feature requests into structured components. This skill classifies the request type, extracts actors and desired outcomes, and separates implementation decisions from human-only open questions.

Write a first-draft PRD with repo-aware context by providing the request text alongside repository docs, code, and tests. The skill reviews existing domain vocabulary, answers key questions internally to record assumptions, and produces a standardized PRD grounded in current system behavior.

Yes, you can generate a PRD for mixed requests containing both bugs and feature requests. The skill automatically classifies incoming text as a bug, feature, or mixed request, then extracts the core problem, actors, and constraints to produce a comprehensive first-draft PRD.

Generating a PRD from a feature request does require manual input for open questions. While the skill self-grills assumptions and drafts implementation decisions, it explicitly separates human-only unknowns and open questions that need follow-up review and clarification.

The best way to draft product requirements from informal customer issue descriptions is using an automated intake classifier. This skill parses the text, grounds the spec in repo-aware domain vocabulary, and outputs a standardized PRD detailed enough to guide implementation planning.