PRD Analyzer & Implementation Planner
Transform product requirements into actionable implementation plans with visual kanban tracking.
When NOT to Use
- Revising an existing plan — Use
plan-revisionfor modifying task hierarchies or scope changes - Starting implementation — Use
work-sessionto begin executing tasks from a plan - Quick one-off tasks — Use
/quickfor tasks that don't need epic/story/task hierarchy - Investigating feasibility — Use
spikefor time-boxed technical investigation before committing to a plan
Key Principles
- Plan state lives in ohno (
.ohno/, epics → stories → tasks managed via MCP tools/CLI);.claude/PROJECT.mdholds the project overview - Break work into epic → story → task hierarchy (tasks ≤ 8h each)
- Assign skills to features based on type (api-design, database-design, etc.)
- Flag ambiguities before planning — don't assume unclear requirements
Quick Start Checklist
- Read the full PRD/brief document
- Extract goals, features, constraints, and dependencies
- Classify priorities (P0-P3) and flag ambiguities
- Break features into epics → stories → tasks with estimates
- Create the epic/story/task hierarchy in ohno via MCP tools and write
.claude/PROJECT.md - Identify first skill to run and hand off
Skill Assignment
| Feature Type | Primary Skill | Secondary Skills |
|---|---|---|
| REST/GraphQL APIs | api-design | testing-strategy |
| Database schemas | database-design | — |
| SDK/library | sdk-development | — |
| Auth/Security | api-design | — |
| Testing infrastructure | testing-strategy | — |
| AWS/Cloud provisioning | cloud-infrastructure | — |
| Serverless/Lambda | cloud-infrastructure | api-design |
| Container deployment | cloud-infrastructure | ci-cd |
References
| Reference | Description |
|---|---|
| prd-analysis.md | Deep dive on document analysis |
| task-breakdown.md | Detailed breakdown methodology |
| kanban-setup.md | Legacy pre-ohno kanban generation (reference only — plan state lives in ohno) |
| skill-routing.md | Skill assignment logic |
| project-md-template.md | PROJECT.md template and format |
| database-schema.md | ohno internal SQLite schema (reference only — manage via MCP tools/CLI, never write the DB directly) |
| features-json.md | Legacy pre-ohno features.json format (reference only) |
| anti-patterns.md | Analysis, breakdown, and output anti-patterns |
| design-integration.md | Design plugin detection, UI/UX workflows, design-first routing |
| kanban-template.html | HTML template for interactive kanban board |
Runtime Notes
- Claude Code: dispatch yokay-planner via the Task tool with
subagent_type: "pokayokay:yokay-planner". - Codex: there is no subagent dispatch. Execute the agent's role inline — read the corresponding
agents/yokay-<name>.mdand follow its Behavioral Defaults, Critical Rules, and Output Contract directly in the current session.