Working out a decision by dialogue before any task — discuss the idea, weigh options with trade-offs, record the decision in BRIEF.md, and hand it to task or plan. Use this skill when the user wants to discuss first and only then (maybe) act — "let's discuss", "before doing it let's talk", "help me decide", "help me…
Code review without edits — the working diff, a branch against its base, a PR, a range of commits, or a named module. Each finding with a file:line proof, a severity, and a failure scenario; the unproven is filtered out by verification; the result is a verdict (ok / ok with notes / changes needed), and for a full…
Documents "why it's this way" and "where the gotchas are" as a navigable graph. Each node is one decision/invariant/gotcha with a file:line proof. Use this skill whenever the user asks to record architectural decisions, rationale, or gotchas as a graph — "build a decision graph", "document the architecture as a…
Systematic hunt for a bug's root cause without fixing it — build a feedback loop that goes red on the bug, read the error in full, hypotheses with testable predictions, minimal experiments, a log of what was rejected; the root, once found, goes back to task for the fix. Use this skill when the cause of a breakage is…
Planning and decomposing a large initiative that breaks into several separate tasks — discuss the nuances, build a tree (DAG) of tasks with dependencies, and lay it out into waves of parallel execution. Use this skill when the scope is not "one task" but an epic of many tasks — the observable boundary is the work…
Entry point for any development task — feature, bugfix, refactor, integration, migration. Use this skill whenever the user sets a task to change code — "do it", "add", "fix", "correct", "rewrite", "refactor", "implement", "fix this", "add feature" — even without the words "task" or "skill". Also trigger on the flags…
Running one wave of a PLAN in parallel — a fan-out of spec drafters, ONE human gate over the whole wave, a fan-out of executors in their own worktrees, then sequential merges, verification, and a single PR for the wave. Use this skill when a plan's wave is ready to run and its leaves are independent — "run the wave"…