/ak:plan Rename settings route --fast

Use when:

Use for small, low-risk, already-understood changes.

Expected:

A compact plan.md and phase files with research, red-team, and validation skipped; still includes codebase analysis and no implementation code.

/ak:plan Rebuild checkout architecture --deep --html

Use when:

Use for complex work that benefits from research, validation, and a visual plan artifact.

Expected:

Deep-mode researchers, per-phase scouts, red-team, validation, and final authoritative plan.html with inline diagrams or UI mockups.

/ak:plan validate plans/checkout-redesign/plan.md

Use when:

Use before implementation when assumptions or acceptance criteria may be thin.

Expected:

Critical-questions validation interview, plan-file edits when needed, and a whole-plan consistency sweep before any cook recommendation.

/ak:plan Add rate limiting to public APIs --auto

Use when:

You want the planner to pick one mutually exclusive workflow mode from task complexity.

Expected:

Inspects live ak plan help, selects one mode, writes files-first plan.md and phase stubs, and does not implement code.

/ak:plan Migrate sessions to a durable store --hard

Use when:

The work is risky enough for two researchers plus red-team.

Expected:

Runs two researchers and red-team, writes the plan files, and hard-stops if contradictory mode flags are combined.

/ak:plan Split search indexing from query API --parallel

Use when:

Independent plan slices can be researched in parallel.

Expected:

Assigns non-overlapping phase ownership, researches those slices in parallel, and still writes one files-first plan tree.

/ak:plan Compare queue versus cron for digest mail --two

Use when:

You need two researched approaches before choosing.

Expected:

Produces two approach sections with trade-offs, keeps one recommended path, and writes plan files without implementing either option.

/ak:plan Choose monolith versus service split for billing --debate

Use when:

A contested architecture choice needs an explicit debate pass.

Expected:

Runs the debate workflow, records competing positions and a decision, and writes the plan without code changes.

/ak:plan Design webhook retry semantics --ultra

Use when:

Plan selection is high-stakes and should use a verifier pass.

Expected:

Builds one evidence packet, fans read-only plan candidates, lets a verifier pick one unchanged, and writes that plan to disk.

/ak:plan archive plans/checkout-redesign/plan.md

Use when:

A finished plan should move to the archive without further edits.

Expected:

Moves the completed plan into the archive location and reports the archived path without editing implementation code.

/ak:plan red-team plans/checkout-redesign/plan.md

Use when:

An existing plan needs an adversarial review before cook.

Expected:

Runs the red-team interview against the live plan files, records findings, and refuses cook while accepted findings remain.