From supergraph
Converts conversation context into a structured Product Requirements Document (PRD) and optionally posts it to GitHub Issues. Use when requirements came from discussion rather than a formal spec.
How this skill is triggered — by the user, by Claude, or both
Slash command
/supergraph:prdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn conversation into a machine-readable PRD. Gives `/supergraph:plan` a concrete spec to work from.
Turn conversation into a machine-readable PRD. Gives /supergraph:plan a concrete spec to work from.
Announce: "📋 /supergraph:prd — extracting requirements..."
head -60 CONTEXT.md 2>/dev/null || echo "No CONTEXT.md"
Use domain vocabulary from CONTEXT.md in the PRD — never invent new terms for existing concepts.
Gather from current conversation context:
Ask one clarifying question if a critical piece is missing. Do not ask multiple questions at once.
# PRD: [Feature/Fix Name]
## Problem
[One paragraph: what is broken or missing, and why it matters]
## Solution
[One paragraph: the approach — what will be built]
## User Stories
- As a [role], I want [action] so that [outcome]
- (2-5 stories max)
## Acceptance Criteria
- [ ] [Observable, testable condition]
- [ ] [Observable, testable condition]
- (Each maps to a test in /supergraph:plan)
## Implementation Decisions
- [Technology/pattern chosen and why]
- [What was explicitly ruled out and why]
## Testing Decisions
- [Unit: what gets unit tested]
- [Integration: what needs integration tests]
- [E2E: what needs Playwright coverage, if any]
## Out of Scope
- [Explicitly not included in this work]
## Notes
- [Domain terms: add to CONTEXT.md if new]
- [Dependencies on other work]
- [Security considerations]
Show PRD to user. Ask: "Does this capture what you need? [yes / adjust]"
Incorporate feedback, re-present if needed.
If user confirms and repo has GitHub remote:
gh issue create \
--title "[PRD] <feature name>" \
--body "$(cat <<'EOF'
[PRD content]
EOF
)" \
--label "enhancement,ready-for-agent"
Report issue URL.
Save to docs/supergraph/plans/YYYY-MM-DD-prd-<slug>.md.
If the PRD introduced new domain terms:
# Append to CONTEXT.md
printf '\n## <term>\n[definition from PRD]\n' >> CONTEXT.md
✅ /supergraph:prd complete
- PRD: docs/supergraph/plans/YYYY-MM-DD-prd-<slug>.md
- Issue: #N (if posted)
- Acceptance criteria: N
- Next: /supergraph:plan
npx claudepluginhub datit309/supergraph --plugin supergraphGenerates a PRD from the current conversation context and codebase understanding, then publishes it to the project's issue tracker (GitHub, GitLab, or local) after user confirmation.
Synthesizes the current conversation into a PRD and publishes it to the project issue tracker with a ready-for-agent label. Useful when you've discussed a feature and need a structured PRD without further interview.
Generates a Product Requirements Document (PRD) from the current conversation context and codebase understanding, saving it to a configured backend (GitHub, Jira, or Inkdrop).