harness

Use when executing a living plan via Claude Code's /batch tool for worktree-isolated parallel execution, or when user says "batch", "batch execute", "run batch", "parallel batch", "run the plan in parallel", "execute without checkpoints", "hands-off execution", or "use batch mode"

Use when starting new feature work, creative design, or when user says "brainstorm", "design a feature", or "let's think about"

Use when investigating a bug, diagnosing an error, or when user says "debug", "fix bug", "investigate issue", or "root cause"

Use when ready to archive the plan and create the PR, when user says "we're done", "complete this", "wrap up", or after /harness:reflect finishes

Use after reflect to classify learnings, update metrics, and propose agent evolution, or when user says "evolve", "self-improve", "classify learnings"

Use when initializing structured documentation for a repository, when CLAUDE.md exceeds 120 lines, or when user says "set up docs" or "initialize harness"

Use when executing a living plan with agent teams, or when user says "orchestrate", "execute the plan", "start building", or "run the plan"

Use when creating an implementation plan from a design doc, bug analysis, or refactor scope, or when user says "create a plan", "plan this", or "write the plan"

Use when auditing docs for staleness, broken links, or bloat. Also use when user says "docs feel stale", "prune docs", or when CLAUDE.md exceeds 120 lines.

Use when resuming an in-progress refactoring, checking goal progress, or when user says "refactor status", "where are we", or "continue refactoring"

Use when planning an incremental refactoring, extracting responsibilities from a large class, or when user says "refactor", "extract", "strangler fig", or "decompose"

Use when capturing learnings and updating docs after review, when user says "reflect", "retrospective", "update docs", or after /harness:review completes

Use when implementation is done and code needs quality review, when user says "review the code", "check the code", or after /harness:orchestrate completes all tasks

Use when proposing modifications to agent definitions based on review escapes, metric anomalies, or universal learnings — invoked by /harness:evolve Phase 3

Use when auditing documentation health, finding stale or orphaned guides, checking CLAUDE.md bloat, or when /harness:prune is invoked

Use during /harness:review Phase 4 to check code changes against active learnings from docs/LEARNINGS.md for violations

Use when breaking up a god class, extracting responsibilities from an oversized module, incrementally replacing legacy code, or when old and new must coexist during a refactor — symptoms include classes over 500 lines, modules with mixed concerns, or "we can't rewrite this all at once"