Installs just this skill. Get the whole plugin for auto-invocation.
โก How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/skill-prd
๐๏ธ Context preview
The summary Claude sees to decide when to auto-load this skill.
Write an AI-optimized PRD using multi-AI orchestration โ use when scoping a new feature or product
๐ Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
๐ฆ Ships with octo
</> SKILL.md
skill-prd.SKILL.md
---name: skill-prd
description: Write an AI-optimized PRD using multi-AI orchestration โ use when scoping a new feature or product
context: fork
agent: Plan
---# STOP - SKILL ALREADY LOADED
**DO NOT call Skill() again. DO NOT load any more skills. Execute directly.**
---## PHASE 0: CLARIFICATION (MANDATORY)
Before writing ANY PRD content, you MUST ask the user these questions:
```
I need to understand your requirements before creating the PRD.
1. **Target Users**: Who will use this? (developers, end-users, admins, etc.)
2. **Core Problem**: What specific pain point does this solve? Any metrics?
3. **Success Criteria**: How will you measure if this succeeds?
4. **Constraints**: Any technical, budget, or timeline constraints?
5. **Existing Context**: Is this greenfield or integrating with existing systems?
Please answer these (even briefly) so I can create a more targeted PRD.
```
**WAIT for user response before proceeding to Phase 1.**
If user says "skip" or provides the feature description inline, extract what you can and note assumptions.
**After drafting the PRD but BEFORE self-scoring, dispatch the draft to a second provider for adversarial review.** A single-model PRD has blind spots โ cross-provider challenge surfaces wrong assumptions, uncovered scenarios, and contradictory requirements.
Dispatch the PRD draft to a different provider (Codex, Gemini, or Sonnet as fallback) with this prompt:
> "Challenge this PRD. What assumptions are wrong? What user scenarios are missing? What requirements contradict each other? What will the first user complaint be? What risk does this PRD ignore?"
**After receiving the challenge:**
- Revise the PRD to address valid challenges
- Note dismissed challenges in the Risks section if they have partial merit
- Add to PRD footer: `Adversarial review: applied`
**Skip with `--fast` or when user requests speed over thoroughness.** See `prd.md` command for full dispatch syntax.