How this command is triggered — by the user, by Claude, or both
Slash command
/claudster:prd <feature or problem>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /prd — requirements discovery Produce a Product Requirements Document for: **$ARGUMENTS** If empty, ask what the feature/problem is and stop. Goal: turn a fuzzy idea into a crisp, testable spec that `/feature-plan` can consume. ## Discovery (ask, don't assume) Interview the user to fill gaps. Ask only what you can't infer from the codebase / `STACK.md`. Cover: - **Problem & users** — what hurts, for whom, why now. - **Outcome** — what "done" looks like in user terms; how we'd measure it. - **Scope** — must-have vs nice-to-have vs explicitly out. - **Data & constraints** — sources, fiel...
Produce a Product Requirements Document for: $ARGUMENTS
If empty, ask what the feature/problem is and stop. Goal: turn a fuzzy idea into a crisp, testable spec
that /feature-plan can consume.
Interview the user to fill gaps. Ask only what you can't infer from the codebase / STACK.md. Cover:
Ask in small batches; stop interviewing once the spec is testable.
.github/agent-docs/prd/<feature-slug>.md# PRD — <feature>
**Created:** <ISO date> • **Status:** draft
## Problem
<who, what, why.>
## Goal & success criteria
- <measurable outcome>
## Functional requirements
- FR-1: <requirement — phrased so a test can verify it>
## Non-functional requirements
- NFR-1: <perf/security/a11y/...>
## Out of scope
- <explicitly excluded>
## Data
| Field / source | Shape | Notes |
|---|---|---|
## Edge cases & failure modes
- <empty / error / permission / boundary>
## Open questions
- <unresolved — needs a decision before planning>
Output the PRD path and the FR list. Suggest: "Next: /feature-plan <feature>." Don't design the
implementation here — PRD is the what, the plan is the how.
npx claudepluginhub saajunaid/junai --plugin claudster/prdGenerates Product Requirements Document (PRD) for <feature-name>, saves to .pm/prds/, checks for duplicate issues, and creates labeled GitHub issue with PRD body.
/prdCreates a Product Requirements Document (PRD) for a product or feature via phased workflow with clarifying questions, task tracking, review, technical expansion, and backlog items.