status

Start a behavior brainstorm session for a new feature — the mandatory first phase of BDK feature work.

Enter or resume the RED phase — write failing behavior tests from the approved spec, with signature-only stubs in source.

Retro-review an existing feature against the behavior-first standard (Cooper + Wlaschin) without entering the phased workflow.

Verify that a past Claude Code session properly ran the /bdk:audit protocol — locates the session transcript by ID and grades each audit checkpoint.

The RED→GREEN gate — verify genuine red, run the test-quality reviewer, send in the EDFH adversary, then unlock implementation.

Set up BDK in the current project — detect the stack, write .bdk/config.json, install the doctrine rules file, and prepare gitignore entries.

Enter the REFACTOR phase — behavior-preserving structural improvement with zero new tests, protected by the green suite.

Escape hatch — a test is wrong or the desired behavior changed; reopen RED with a logged reason so tests can be edited again.

Shift TDD gears for the active feature — 4 (default full cycle), 5 (skip-ahead for obvious implementations), or low (exploratory throwaway tests).

Escape hatch — refactoring exposed genuinely new public contract; open a new RED for that surface instead of silently testing internals.

Close out the active BDK feature — final green verification, no new tests since RED, throwaway scaffolding deleted, spec finalized and archived.

Escape hatch — allow Claude to read one specific source file during BRAINSTORM, logged.