joshsymonds/gambit

brainstorming

Turns a rough idea into an approved epic contract with immutable requirements, anti-patterns, and a first wave of executable tasks.

brainstorming

Turns a rough idea into an approved epic contract with immutable requirements, anti-patterns, and a first wave of executable tasks.

executing-plans

Executes an approved epic one wave at a time, dispatching a worker per task and stopping at a checkpoint after each wave. Use when an approved epic contract and native wave plan exist in the current root session, when resuming work after a previous…

debugging

Investigates a bug to its root cause with evidence and a failing test, then hands the understanding off — it does not implement the fix.

executing-plans

Executes an approved epic one wave at a time, dispatching a worker per task and stopping at a checkpoint after each wave.

debugging

Investigates a bug to its root cause with evidence and a failing test, then hands the understanding off — it does not implement the fix.

executing-plans

Executes an approved epic one wave at a time, dispatching a worker per task and stopping at a checkpoint after each wave.

refactoring

Restructures code that already has a green test suite, without changing behavior.

review

Runs an independent multi-dimension review of completed work and adversarially verifies every finding before reporting it.

verification

Substantiates a completion or readiness claim with freshly gathered evidence.

writing-skills

Validates that a new or modified skill actually changes model behavior before it ships.

refactoring

Restructures code that already has a green test suite, without changing behavior.

review

Runs an independent multi-dimension review of completed work and adversarially verifies every finding before reporting it.

verification

Substantiates a completion or readiness claim with freshly gathered evidence.

writing-skills

Validates that a new or modified skill actually changes model behavior before it ships.

review

Runs an independent multi-dimension review of completed work and adversarially verifies every finding before reporting it. Use after every native wave in the current root session is complete, after refactoring verifies, or before merging to main. Triggers…

writing-skills

Validates that a new or modified skill actually changes model behavior before it ships. Use when creating a new skill, modifying an existing skill, writing or rewriting a SKILL.md file, auditing a skill's description for discoverability, or when user mentions…

brainstorming

Turns a rough idea into an approved epic contract with immutable requirements, anti-patterns, and a first wave of executable tasks. Use when user has a new feature idea, rough concept, or unexplored approach. Include when planning before code, breaking a…

debugging

Investigates a bug to its root cause with evidence and a failing test, then hands the understanding off — it does not implement the fix. Use when a test is failing, when a bug is reported, when behavior is unexpected or intermittent, when a build or…

finishing-branch

Integrates a finished branch — merge, pull request, keep, or discard — after verifying tests on the result. Use when every native epic wave is completed, when ready to integrate after review approval, when choosing between merge / PR / keep / discard for a…

refactoring

Restructures code that already has a green test suite, without changing behavior. Use this implementation mechanic to restructure covered code without changing behavior only when explicitly invoked by name or called by an active Gambit workflow owner; do not…

task-refinement

Refines prepared work briefs until each one is executable by a junior engineer without questions. Use this implementation mechanic to refine prepared work briefs only when explicitly invoked by name or called by an active Gambit workflow owner; do not select…

test-driven-development

Drives new behavior or a bug fix through the RED-GREEN-REFACTOR cycle, test first. Use this implementation mechanic for new behavior or bug fixes requiring test coverage only when explicitly invoked by name or called by an active Gambit workflow owner; do not…

testing-quality

Audits an existing test suite for tests that pass without catching bugs, and specifies the replacements. Use this implementation mechanic to audit an existing test suite only when explicitly invoked by name or called by an active Gambit workflow owner; do not…

verification

Substantiates a completion or readiness claim with freshly gathered evidence. Use this implementation mechanic to substantiate a completion or readiness claim only when explicitly invoked by name or called by an active Gambit workflow owner; do not select it…

finishing-branch

Integrates a finished branch — merge, pull request, keep, or discard — after verifying tests on the result.

task-refinement

Refines prepared work briefs until each one is executable by a junior engineer without questions.

test-driven-development

Drives new behavior or a bug fix through the RED-GREEN-REFACTOR cycle, test first.

testing-quality

Audits an existing test suite for tests that pass without catching bugs, and specifies the replacements.

finishing-branch

Integrates a finished branch — merge, pull request, keep, or discard — after verifying tests on the result.

task-refinement

Refines prepared work briefs until each one is executable by a junior engineer without questions.

testing-quality

Audits an existing test suite for tests that pass without catching bugs, and specifies the replacements.

using-gambit

Use only when the user explicitly asks Gambit to route a concrete software task and has not already named a public workflow owner.

using-gambit

Use only when the user explicitly asks Gambit to route a concrete software task and has not already named a public workflow owner.