From octo
Generates a structured PRD for a given feature using multi-provider AI orchestration and a 100-point scoring framework.
How this command is triggered — by the user, by Claude, or both
Slash command
/octo:prdcommands/The summary Claude sees in its command listing — used to decide when to auto-load this command
### MANDATORY COMPLIANCE — DO NOT SKIP **When the user explicitly invokes `/octo:prd`, you MUST follow the orchestrated PRD workflow below.** You are PROHIBITED from writing the PRD directly without the required clarification, research, scoring, and `orchestrate.sh` steps. ### EXECUTION MECHANISM — NON-NEGOTIABLE **You MUST execute this command by calling `orchestrate.sh` as documented below. You are PROHIBITED from:** - ❌ Doing the work yourself using only Claude-native tools (Agent, Read, Grep, Write) - ❌ Using a single Claude subagent instead of multi-provider dispatch via orchestrate...
When the user explicitly invokes /octo:prd, you MUST follow the orchestrated PRD workflow below. You are PROHIBITED from writing the PRD directly without the required clarification, research, scoring, and orchestrate.sh steps.
You MUST execute this command by calling orchestrate.sh as documented below. You are PROHIBITED from:
Multi-LLM orchestration is the purpose of this command. If you execute using only Claude, you've violated the command's contract.
This command is already executing. The feature to document is: $ARGUMENTS.feature
Before writing ANY PRD content, ask the user:
I'll create a PRD for: **$ARGUMENTS.feature**
To make this PRD highly targeted, please answer briefly:
1. **Target Users**: Who will use this? (developers, end-users, admins, agencies?)
2. **Core Problem**: What pain point does this solve? Any metrics on current impact?
3. **Success Criteria**: How will you measure success? (KPIs, adoption rate, time saved?)
4. **Constraints**: Any technical, budget, timeline, or platform constraints?
5. **Existing Context**: Greenfield project or integrating with existing systems?
(Type "skip" to proceed with assumptions, or answer inline)
WAIT for user response before proceeding.
Check provider availability first:
set -euo pipefail
# Check if multi-provider research is available
CODEX_AVAILABLE="false"
if command -v codex >/dev/null 2>&1; then
CODEX_AVAILABLE="true"
fi
GEMINI_AVAILABLE="false"
if command -v gemini >/dev/null 2>&1; then
GEMINI_AVAILABLE="true"
fi
AGY_AVAILABLE="false"
if command -v agy >/dev/null 2>&1; then
AGY_AVAILABLE="true"
fi
If multiple providers are available, dispatch parallel research for richer context:
🐙 Multi-provider research mode:
# Parallel research dispatch (if providers available)
if [[ "$CODEX_AVAILABLE" == "true" ]]; then
orchestrate.sh prd-research "<feature>" codex &
fi
if [[ "$GEMINI_AVAILABLE" == "true" ]]; then
orchestrate.sh prd-research "<feature>" gemini &
fi
if [[ "$AGY_AVAILABLE" == "true" ]]; then
orchestrate.sh prd-research "<feature>" agy &
fi
wait
If single-provider only, do MAX 2 web searches:
Do NOT over-research. Move to writing quickly.
Include these sections:
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.
If an external provider is available, dispatch through Octopus routing:
review_provider=""
command -v codex >/dev/null 2>&1 && review_provider="codex"
[[ -z "$review_provider" ]] && command -v agy >/dev/null 2>&1 && review_provider="agy"
[[ -z "$review_provider" ]] && command -v gemini >/dev/null 2>&1 && review_provider="gemini"
if [[ -n "$review_provider" ]]; then
"${HOME}/.claude-octopus/plugin/scripts/orchestrate.sh" spawn "$review_provider" \
"You are a skeptical product reviewer. Challenge this PRD:
1. What ASSUMPTIONS are wrong or untested? (e.g., assumed user behavior, market conditions, technical feasibility)
2. What USER SCENARIOS are missing? (edge cases, error states, migration paths, day-2 operations)
3. What REQUIREMENTS CONTRADICT each other? (e.g., 'real-time' + 'offline-first', 'simple' + 'enterprise-grade')
4. What will the FIRST user complaint be?
5. What is the biggest RISK this PRD ignores?
PRD DRAFT:
<paste PRD content>"
fi
If no external provider is available, launch Sonnet:
Agent(
model: "sonnet",
description: "Adversarial PRD review",
prompt: "Challenge this PRD. What assumptions are wrong? What scenarios are missing? What requirements contradict? What will the first user complaint be?
PRD DRAFT:
<PRD content>"
)
After receiving the challenge:
Adversarial review: applied (provider: <provider>)Skip with --fast or when user explicitly requests speed over thoroughness.
Write to user-specified filename or generate one.
BEGIN PHASE 0 - ASK CLARIFICATION QUESTIONS FOR: $ARGUMENTS.feature
npx claudepluginhub nyldn/claude-octopus --plugin octo/prp-prdGenerates interactive, problem-first Product Requirements Document (PRD) via phased questioning, market research, and hypothesis validation.
/create-prdCreates a Product Requirements Document via structured elicitation interviews, creative techniques, scale-adapted depth, and adversarial review.
/prp-prdGenerates interactive Product Requirements Document via problem-first questions, market/codebase research using subagents, and hypothesis-driven spec output.
/prp-prdGenerates a product requirements document through iterative problem discovery, market research, and hypothesis-driven questions.
/write-prdCreates a structured Product Requirements Document from a feature idea or problem statement by gathering context conversationally.