From rt
Interactively generates detailed Product Requirements Documents (PRDs) for features via clarifying questions. Includes user stories, requirements, and saves to prds/[feature-name].md.
npx claudepluginhub richtabor/agent-skills --plugin rtThis skill uses the workspace's default tool permissions.
Generate a Product Requirements Document through interactive planning.
Generates Product Requirements Documents (PRDs) for features via clarifying questions on goals, users, and scope. Structures into user stories, requirements; saves to tasks/prd-[feature].md.
Generates structured Product Requirements Documents (PRDs) by gathering project context from files and commits, asking 3-5 clarifying questions with lettered options, and producing sections like user stories, functional requirements, non-goals, and success metrics.
Generates complete PRDs via guided feature discovery, product context integration, clarifying questions, and optional codebase analysis. Outputs user stories, Gherkin criteria, metrics, and launch plans.
Share bugs, ideas, or general feedback.
Generate a Product Requirements Document through interactive planning.
Read the user's feature request. If unclear, ask for a brief description.
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".
After answers, create a detailed PRD with these sections:
# 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.
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.