create-prd_skill

Overview

This skill plans product features interactively and generates a detailed Product Requirements Document (PRD). It asks targeted clarifying questions, accepts compact option-style answers, and produces a structured, developer-ready PRD file. The output is explicit, verifiable, and written for junior engineers and automation.

How this skill works

The skill first reads a user feature request and, when needed, prompts 3–5 clarifying multiple-choice questions formatted with numbered prompts and lettered options. The user replies with combined selections (for example, "1A, 2B") and the skill uses those answers to assemble a full PRD with sections like Goals, User Stories, Functional Requirements, Design and Technical Considerations, Metrics, and Open Questions. Finally, it saves the PRD to a file path under prds/[feature-name].md and confirms the next step to convert it into executable format.

When to use it

• You need a complete PRD for a new feature before engineering work begins.
• You want clearly verifiable acceptance criteria for QA or automation.
• You need a living document that junior developers or AI agents can implement from.
• You want to align stakeholders with explicit goals and non-goals.
• You prefer an interactive planning flow to refine scope quickly.

Best practices

• Provide a concise initial feature request to speed the Q&A step.
• Answer clarifying questions using the numbered/lettered format (e.g., "1A, 2B") to avoid ambiguity.
• Keep acceptance criteria specific and testable (UI text, API responses, state changes).
• Number functional requirements to make task breakdown and tracking easier.
• Review and update the saved PRD file path and file name for clarity before sharing.

Example use cases

• Drafting a PRD for a new onboarding flow that must persist across sessions.
• Creating requirements for an admin-only reporting dashboard with specific metrics.
• Defining an MVP for a file-sharing feature with clear success metrics.
• Converting product manager notes into a developer-ready PRD for sprint planning.
• Standardizing PRDs across multiple small features for consistent QA criteria.