From core-claude-plugin
PRD creation with EA agent using AskUserQuestion for clarification, validation with reviewer, then BA extracts stories. NO HITL in this phase - continues to design-phase.
npx claudepluginhub metasaver/claude-marketplace --plugin core-claude-pluginThis skill uses the workspace's default tool permissions.
> **ROOT AGENT ONLY** - Called by commands only, always invoked at root level.
Generates context-aware PRDs using expert techniques from Cagan, Torres, Biddle, with repo scanning for tech stack and token-efficient, structured outputs.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
ROOT AGENT ONLY - Called by commands only, always invoked at root level.
Purpose: Create PRD (EA with AskUserQuestion), validate (reviewer), extract stories (BA) Trigger: After analysis-phase completes Input: prompt, complexity, tools, scope Output: PRD + Epics + User Stories (NO HITL - continues to design-phase)
1. Check/Create Project Folder
│
▼
2. Spawn EA Agent ──► AskUserQuestion until 100% understood
│ ──► Creates PRD (prd-creation skill)
│
▼
3. Spawn Reviewer ──► Validates PRD (document-validation)
│ ──► If invalid: return to EA with issues
│
▼
4. Spawn BA Agent ──► Creates story outlines
│
▼
5. Continue to design-phase (NO HITL HERE)
docs/epics/* for existing foldersdocs/epics/{PREFIX}{NNN}-{name}/Spawn: core-claude-plugin:generic:enterprise-architect
/skill prd-creation{projectFolder}/prd.mdIMPORTANT: EA asks clarifying questions via AskUserQuestion (NOT HITL). This is iterative clarification, not approval.
Spawn: core-claude-plugin:generic:reviewer
/skill document-validation to validate PRDSpawn: core-claude-plugin:generic:business-analyst
extract-stories{projectFolder}/user-stories/| Complexity | Epics |
|---|---|
| < 15 | 1 |
| 15-29 | 1-2 |
| 30-44 | 2-3 |
| >= 45 | 3+ |
NO HITL in this phase. Proceed directly to design-phase.
HITL approval happens AFTER design-phase completes (single approval for PRD + execution plan + stories).
| Step | Agent | Mode | Output |
|---|---|---|---|
| 2 | enterprise-architect | create-prd | PRD draft |
| 3 | reviewer | validate | Validation |
| 4 | business-analyst | extract-stories | Epics + Stories |
ONE story per target file. Consolidate multiple requirements for same file.
EA prioritizes codebase investigation before questions:
metasaver.projectType{
"status": "complete",
"projectFolder": "docs/epics/msm007-feature",
"prdPath": "docs/epics/msm007-feature/prd.md",
"prdApproved": true,
"epics": [{ "id": "msm-feat", "title": "...", "stories": ["msm-feat-001"] }],
"stories": [{ "id": "msm-feat-001", "epic": "msm-feat", "agent": "..." }]
}
Called by: /audit, /build, /architect, /ms
Spawns: enterprise-architect, reviewer, business-analyst
Calls: /skill prd-creation, /skill document-validation, /skill user-story-template
Next: design-phase (architect enriches stories, then single HITL for all docs)