syntaxninja-dojo

Use when a structured PRD document is needed for the ralph loop — generates prd.json and progress.txt

Use when task scope exceeds one context window and decomposes into independent pass/fail stories with clean iteration boundaries

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — merge, PR, or cleanup

Use when starting feature work that needs isolation from the current workspace or before executing plans that could leave the branch in a broken state

Use when a hard problem was just solved and the solution should be captured as a learning for future reference

Use when 3+ distinct occurrences suggest a skill should be updated with a new trigger, anti-pattern, or verification step

Use when creating a new skill or pattern for the dojo — guides the SKILL.md and PATTERN.md format, CSO lint rules, and index registration

Use when receiving code review feedback — requires technical verification of each suggestion before implementing, not blind agreement

Use when implementation is complete and a comprehensive code review is needed — dispatches parallel review agents and merges findings

Use when a large task needs to be broken into independent, verifiable stories with pass/fail acceptance criteria

Use when requirements are unclear, ambiguous, or have multiple valid interpretations — before planning or implementing

Use when facing 2+ independent tasks that can be researched or implemented by agents without shared state or sequential dependencies

Use when an approved plan exists and implementation should begin — executes steps sequentially with verification checkpoints

Use when executing an implementation plan with independent tasks that can be delegated to subagents within the current session

Use when implementing any feature or bugfix where tests can be written first — write the test, see it fail, make it pass, refactor

Use when a task requires multiple steps and benefits from a structured plan before implementation begins

Use when starting any session — establishes how to find and use skills, requiring Skill tool invocation before ANY response

Use when any task is received — silently enforces smallest viable change set and proposes decomposition for large tasks

Use when implementation is complete and verification has passed — dispatches the sensei agent for fresh-context quality review

Use when encountering any bug, test failure, unexpected behavior, or error message — before proposing any fix

Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims