prd-generator_skill

Overview

This skill generates a comprehensive Product Requirements Document (PRD) from an existing product development plan. It produces a ready-to-use docs/PRD.md including vision, personas, MVP features, user flows, acceptance criteria, and success metrics. Use it to turn planning artifacts into a developer-friendly specification for iOS/macOS products.

How this skill works

The skill reads the most recent product-plan-*.md file and optional competitive-analysis or market-research files to extract problem analysis, target users, MVP scope, positioning, and success criteria. It maps those inputs into the PRD sections (overview, personas, features, flows, non-functional requirements, timeline, and metrics), fills in acceptance criteria and gherkin-style cases for each core feature, and flags missing clarifications to ask the user. The output is a structured docs/PRD.md formatted for handoff to engineering and design.

When to use it

• You have an approved product development plan and need a developer-ready PRD.
• Preparing for an MVP implementation sprint for an iOS or macOS app.
• Translating research and competitive insights into prioritized product requirements.
• Onboarding new team members who need a single source of truth for scope and metrics.
• Before App Store submission to verify success criteria and non-functional requirements.

Best practices

• Provide the latest product-plan-*.md file and any competitive or market research files before running the skill.
• Confirm platform-specific constraints (iOS/macOS versions, device targets) up front.
• Review generated acceptance criteria and approve or refine edge cases with engineering.
• Use the PRD as a living document: update version, status, and critical decisions as they occur.
• Answer flagged open questions early to avoid rework during implementation.

Example use cases

• Convert a product-agent run output into a PRD for a two-month MVP schedule.
• Augment a product brief with competitor gaps to prioritize unique features in the PRD.
• Create an onboarding and core feature flow with gherkin acceptance criteria for QA.
• Produce a release-ready PRD that includes performance, security, and accessibility requirements.
• Generate deferred feature lists and a Phase 2 roadmap for stakeholder review.