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-revision for modifying task hierarchies or scope changes
• Starting implementation — Use work-session to begin executing tasks from a plan
• Quick one-off tasks — Use /quick for tasks that don't need epic/story/task hierarchy
• Investigating feasibility — Use spike for 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.md holds 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