create-prd

Optional environment variables:

• GHPM_PROJECT - GitHub Project name to associate issue with. If not set, the command will query available projects for the repository owner and prompt for selection.

<usage_examples>

Detailed input (skips clarification):

/ghpm:create-prd Build a user authentication system with email/password and OAuth support for enterprise customers who need SSO to reduce IT friction during onboarding

→ Detailed input (30+ words, has who/what/why) → Proceeds directly to PRD generation

Vague input (triggers clarification):

/ghpm:create-prd Add a dashboard

→ Vague input (4 words, missing who/why/scope) → Presents clarifying questions:

1. Who is the primary user? (Internal team, Customers, Admins, Developers)
2. What problem does this solve? (Efficiency, Missing capability, UX, Compliance)
3. What's the scope? (MVP, Feature complete, Production-ready, Enterprise-grade)

After user responds → Generates PRD with enriched context

Complex feature (typically detailed enough):

/ghpm:create-prd Add real-time collaboration features to the document editor, similar to Google Docs, so remote teams can co-edit documents without version conflicts

→ Detailed input → Proceeds directly to PRD generation

With project association (auto-prompt):

/ghpm:create-prd Implement dark mode across the application for users with visual sensitivities to reduce eye strain

→ If GHPM_PROJECT not set, prompts: "Which GitHub Project should this PRD be added to?" with available projects

With project pre-set (skip prompt):

export GHPM_PROJECT="MyOrg/Q1 Roadmap"
/ghpm:create-prd Implement dark mode across the application for users with visual sensitivities to reduce eye strain

→ Skips project selection prompt and uses pre-set project

</usage_examples>

<operating_rules>

• For vague input: Use AskUserQuestion tool to gather context before generating the PRD. See <vagueness_detection> for criteria.
• For detailed input: Proceed directly to PRD generation. Make reasonable assumptions and explicitly record them under Assumptions and Open Questions.
• Do not create or persist local markdown artifacts (no local PRD files). All artifacts must live in GitHub issue bodies/comments.
• Use Markdown in the issue body. Make the PRD self-contained.
• Keep scope crisp; if the request is broad, define a "V1" and park the rest in Out of Scope / Future Ideas.
• Clarification should be quick (max 4 questions) - do not interrogate the user. </operating_rules>

<prd_structure>

Required PRD Structure (Issue Body)

Use this exact outline:

# PRD: <Concise Name>

## Summary
## Problem / Opportunity
## Goals (Success Metrics)
## Non-Goals / Out of Scope
## Users & Use Cases
## Requirements
- Functional Requirements
- Non-Functional Requirements
## UX / UI Notes (if relevant)
## Data / Integrations (if relevant)
## Risks / Edge Cases
## Assumptions
## Open Questions
## Acceptance Criteria (high level)
## Rollout / Release Notes (brief)
## Implementation Notes (non-binding)
(Keep this section minimal; do not over-prescribe.)

</prd_structure>

<input_validation>