planning
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
- All outputs go to
.claude/folder (PROJECT.md, tasks.db, features.json, kanban.html) - 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
More from srstomp/pokayokay
architecture-review
Use when auditing project structure, planning refactors, improving code organization, analyzing dependencies and module boundaries, or identifying structural issues. TypeScript/JavaScript-primary with language-agnostic patterns.
299figma-plugin
Use when building Figma plugins, creating design automation tools, implementing sandbox/UI communication, or working with the Figma Plugin API for node manipulation, styles, and components.
79security-audit
Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations.
48testing-strategy
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.
28sdk-development
Use when building TypeScript SDKs, extracting shared code into packages, creating developer tooling libraries, designing clean API surfaces, or publishing to npm (public or private). Covers typed clients, error handling, multi-target bundling (ESM/CJS/browser).
28session-review
Use after completing work sessions to analyze agent behavior patterns, prepare session handoffs for continuity, document completed work, identify blockers, or preserve context for the next session.
27