Review code changes for correctness, error handling, scope creep, and style. Use when the goal mentions reviewing a PR, diff, or file.
Walk through a stack trace or error log to find the root cause. Use when the goal mentions debugging, investigating an error, or tracking down a bug.
Write a Conventional Commits message describing a code change. Use when the goal mentions creating a commit, writing commit message, or committing changes.
Outline unit tests for a function or module before writing them. Use when the goal mentions writing tests, test plan, or test coverage.
Keep effort proportional to risk โ prefer the cheapest sufficient workflow, escalate only on evidence, refuse over-analysis on simple tasks. Use when choosing depth, level, or workflow shape.
Map required capabilities to persona roles and available skills. Detect missing skill coverage and decide whether to acquire a skill, request one, or proceed generically. Use when scoping a workflow.
Coordinate multi-persona work with a shared blackboard, role boundaries, hand-off contract, conflict resolution, and final synthesis. Use when a task benefits from more than one persona.
Gather enough context before acting โ read code, docs, specs, prior decisions; identify the source of truth; refuse to speculate. Use when investigating, researching, or before any non-trivial change.