npx claudepluginhub choam2426/geasThis skill uses the workspace's default tool permissions.
Create a structured Product Requirements Document.
Generates a concise 1-2 page structured PRD from product ideas or feature descriptions, resolving ambiguities and enforcing decisions for engineering teams.
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 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.
Share bugs, ideas, or general feedback.
Create a structured Product Requirements Document.
$ARGUMENTS — a feature idea, problem statement, or mission.
# PRD: <product/feature name>
## Problem
What problem are we solving? Who has this problem? How do they deal with it today?
## Objective
What does success look like? Define 2-3 measurable outcomes.
## Target Users
Who is the primary user? What are their characteristics and needs?
## Scope
### In Scope
- Feature 1
- Feature 2
### Out of Scope
- Feature X (why: too complex for initial release)
- Feature Y (why: not validated)
## User Flows
Describe the key user journeys step by step.
## Requirements
### Functional
| # | Requirement | Priority | Notes |
|---|-------------|----------|-------|
| 1 | ... | P0 | ... |
### Non-Functional
- Performance: ...
- Accessibility: ...
- Security: ...
## Success Metrics
How will we measure if this is working?
## Open Questions
What do we still need to figure out?