spec-prd

To generate a Product Requirements Document, this Skill guides you through clarifying questions and automatically references upstream artifacts like Bounded Context Maps and Feature Breakdown Structures. It requires your input on feature goals, problem statements, success criteria, and user stories to produce a consistent Markdown file.

Automating feature specification involves answering guided questions about your feature requirements. This process leverages upstream artifacts like personas and value streams to ensure traceability, resulting in a standardized Markdown document with architecture traceability sections.

While you can create a PRD without them, having upstream artifacts like Bounded Context Maps, Feature Breakdown Structures, personas, and value streams significantly enhances traceability. The Skill automatically detects and references these artifacts to enrich the feature specification.

Yes, you can promote functionalities within a Feature Breakdown Structure during the PRD generation process. The Skill supports automatic PRD ID generation and allows functionality promotion directly while defining your feature requirements.

Guided PRD generation handles success criteria and user stories by requiring them as explicit inputs. You define these elements alongside feature goals and problem statements, which the Skill then integrates into a structured Markdown output with a status section.