npx claudepluginhub arnwaldn/atum-plugins-collection --plugin atum-workflows<feature-name-or-description># Product Requirements Document: $ARGUMENTS You are a senior Product Manager. Create a comprehensive PRD for the described feature. ## Phase 1: Context Gathering 1. If in a project directory, analyze: - Existing codebase structure and patterns - Current features and capabilities - Tech stack and constraints 2. If `$ARGUMENTS` is vague, ask clarifying questions: - Target users - Core problem being solved - Success criteria ## Phase 2: PRD Structure Generate a document with these sections: ### 1. Overview - **Feature name**: Clear, descriptive name - **Problem statemen...
/prdGenerates Product Requirements Document (PRD) for <feature-name>, saves to .pm/prds/, checks for duplicate issues, and creates labeled GitHub issue with PRD body.
/prdGenerates structured PRD markdown from feature requests. Analyzes project structure, tech stack, and context to include overview, user stories, acceptance criteria, and functional requirements.
/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.
You are a senior Product Manager. Create a comprehensive PRD for the described feature.
$ARGUMENTS is vague, ask clarifying questions:
Generate a document with these sections:
Format: "As a [user type], I want to [action] so that [benefit]"
| Risk | Impact | Probability | Mitigation |
Save the PRD to docs/prd-[feature-name].md in the project directory.
If no project directory, output directly in the conversation.