
Transforms loose ideas or refined concepts into structured PRDs through progressive interview, thin E2E slices for risky unknowns, and optional codebase exploration. Use when asked to "write a PRD", "create a PRD", "design a feature", "flesh out this idea", "turn this into a spec", "product requirements", "spec this out", or /prd-designer. Outputs a markdown PRD at docs/prds/{name}.md. Optionally creates a GitHub issue via gh CLI. Dependencies: gh CLI (optional, for issue creation).
Deep research on an idea before writing a PRD. Explores existing solutions via web search, analyzes competitors, assesses technical feasibility, and optionally explores the codebase. Use when asked to "research this idea", "investigate this feature", "what already exists for X", "explore solutions for X", "do research before the PRD", "look into X", or /research. Outputs a structured research document at docs/research/{name}.md. Suggests running /prd-designer as the next step. Dependencies: WebSearch (optional).
Reviews implementation plans and ideas through a tribunal of AI personas (Skeptic, Critic, Advocate) that analyze in parallel, then a jury synthesizes findings and grills the user with pointed questions across iterative rounds. Use when asked to "review my plan", "review my idea", "challenge my design", "stress test this approach", "get feedback on my plan", or /review-idea. Produces a verdict report with strengths, weaknesses, risks, and action items.
Stages and commits git changes using semantic commits with logical grouping. Use when the user asks to "commit my changes", "commit these changes", "commit staged files", "commit unstaged files", "commit specific files", "make a commit", "create commits", or /commit. Defaults to staged-only scope. Warns if unstaged changes exist. Groups related changes into separate semantic commits with meaningful titles and body descriptions. Supports three scopes: staged (default), unstaged, or specific files/paths provided by the user.
--- name: storytelling-tests description: Enforce storytelling test patterns with Arrange-Act-Assert structure and domain-specific testing language (DSTL). Use when asked to "write tests for", "create tests", "add tests", "review my tests", "check my tests", "improve test coverage", "make these tests better", "refactor these tests", or "test this function". Also use when planning test implementation, designing test strategy, or when a plan includes steps to add or create tests. Also triggers whe
Build, audit, and improve Claude Code skills through guided interview and generation. Use when user says "create a skill", "build a skill", "make a new skill", "write a skill", "improve this skill", "audit this skill", "review my skill", "skill from scratch", "turn this into a skill", or /skill-builder. Produces guide-compliant skill directories with SKILL.md, references, and scripts.