Spec Product Prd

What it does

This skill, Spec Product Prd, automatically generates detailed product specifications (PRDs) based on existing solution documentation. It transforms recommended decisions from a "solution.md" file into a structured PRD document (prd.md), ensuring clear deliverables for development teams, QA testers, and stakeholders. The generated PRDs focus on verifiable acceptance criteria, avoid open questions, and prevent redundant information compared to the original solution documents.

When to use it

This skill is useful in these scenarios:

• When a "solution.md" file has already been created outlining recommended decisions for a feature.
• To formally freeze delivery specifications (scope, acceptance criteria, milestones, risks and dependencies) for independent PRD review.
• As part of a structured product development lifecycle where solution documentation precedes PRD creation.

Key capabilities

• Generates PRDs from existing "solution.md" documents.
• Focuses on scenarios, business rules, and testable acceptance criteria (AC).
• Ensures all uncertainties are documented in a verification checklist instead of appearing as open questions.
• Avoids duplicating information already present in the "solution.md" file.
• Uses a predefined template for PRD structure (prd-template.md).
• Extracts key deliverables including goals, scope (In/Out), core scenarios, functional items with priorities, and business rules.

Example prompts

Here are some example prompts you can use:

• "I'm using the spec-product-prd skill to generate a PRD based on solution.md."
• "Generate a product specification from this solution document (points to solution.md)."
• “Create a prd.md file for this feature, referencing the existing solution.”

Tips & gotchas

• Prerequisite: The skill requires a preceding "spec-context" skill to be executed first to determine the FEATURE_DIR. If spec-context fails, the process will stop.
• Input Dependency: A valid and complete requirements/solution.md file is essential. Attempting to generate a PRD without it will result in failure.
• Template Adherence: The generated PRD will adhere to a predefined template; while structure can be adapted, unknown information should not be assumed as fact.