LEX AI Docs Hub: Mode Reference
The ten canonical LEX AI mode keys, intent-to-mode selection rules, the kickstart and finalize tool for each mode, and how the non-step-loop shapes differ.
LEX AI Docs Hub: Mode Reference
Canonical mode keys, as accepted by lex-mcp --mode and by switch_to_mode: brief, forward, backward, edit, review, test, input, deploy, mvp_generator, mvp_completion.
Mode selection rules
- Requirements not yet written down ->
brief - New app from scratch ->
forward - Initial MVP only ->
mvp_generator - Finish or expand an MVP ->
mvp_completion - Existing app feature change ->
edit - Audit or review request ->
review - Reverse documentation request ->
backward - Test suite missing or untrusted ->
test - Input-data format changed ->
input - Get the app running in an environment ->
deploy
Session tools per mode
Mode | Kickstart | Finalize |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forward lifecycle
- Kickstart with
kickstart_workflowfor a new repo orkickstart_runfor an existing one. Both read.lex/contract.mdwhen Brief mode has produced one. - Execute the step loop with
get_plan_step-> step agent ->notify_step_complete. - Finalize in two stages: audit instructions first, then the completion call once
plans/technical_docs/audit-report.mdexists on disk.
Shapes other than the step loop
- Edit, review, test, and input are flat catalogues rather than 20-step coordinator loops. They finalize into a consolidated report.
- Backward is documentation-focused and delivers no code changes.
- MVP generator is checkpoint-gated with explicit scope caps and local git only.
- Deploy is sequential but has no fixed local step count: the step bodies are served by the remote deployment handbook, and synthesising one locally is not permitted.
- MVP completion reuses the forward machinery but covers steps 9 to 19;
get_plan_steprefuses any step below 9.
See Mode chooser and Mode switching.
Was this helpful?
Your feedback shapes what we write next.
