create-prd
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install richtabor-agent-skills-create-prd
Repository
Skill path: skills/create-prd
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Open repositoryBest for
Primary workflow: Research & Ops.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: richtabor.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install create-prd into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/richtabor/agent-skills before adding create-prd to shared team environments
- Use create-prd for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: create-prd description: Plan features interactively. Asks clarifying questions, then generates a detailed PRD document. user_invocable: true --- # Create PRD Generate a Product Requirements Document through interactive planning. ## Process ### 1. Understand the Feature Read the user's feature request. If unclear, ask for a brief description. ### 2. Ask Clarifying Questions Ask 3-5 clarifying questions to understand scope and requirements. Format with lettered options: ``` 1. Who is the primary user? A) Logged-in users only B) All visitors C) Admin users 2. Should this persist across sessions? A) Yes, save to database B) No, session only ``` User can respond with combinations like "1A, 2B". ### 3. Generate PRD After answers, create a detailed PRD with these sections: ```md # PRD: [Feature Name] ## Introduction Brief overview of the feature and why it's needed. ## Goals - Primary goal - Secondary goals ## User Stories ### [Story Title] **Description:** As a [user], I want [action] so that [benefit]. **Acceptance Criteria:** - [ ] Specific, verifiable criterion - [ ] Another criterion - [ ] Typecheck passes - [ ] (UI changes) Verify in browser ## Functional Requirements 1. Requirement one 2. Requirement two ## Non-Goals What this feature explicitly won't do. ## Design Considerations UI/UX notes, mockup descriptions. ## Technical Considerations Architecture notes, dependencies, potential challenges. ## Success Metrics How to measure if this feature is successful. ## Open Questions Any unresolved decisions. ``` ### 4. Save PRD Save to `prds/[feature-name].md` (create `prds/` directory if needed). ``` PRD saved to prds/[feature-name].md Next: Run /create-prd-json to convert to executable format. ``` ## Guidelines - Be explicit and unambiguous - Write for junior developers and AI agents - Avoid jargon - Number requirements for easy reference - Acceptance criteria must be verifiable, not vague - Good: "Button displays 'Save' text" - Bad: "Button looks good"