MVP workflows
The two MVP modes: the capped six-checkpoint generator with its boot-check gate and local-only git, and MVP completion, which runs forward steps 9 to 19 to reach full product scope.
MVP workflows
There are two MVP modes. MVP generator scaffolds a small, deliberately capped first version fast. MVP completion takes an approved MVP and expands it to full-product scope. Use them in sequence, or pick the one that matches where you are. Brief routes its new_mvp scenario to the generator and complete_mvp to completion.
MVP generator — a capped first cut
Slash command: /lex-mvp. A reduced-scope forward workflow with six checkpoints instead of twenty steps, and local git only — no remotes, no pushes.
/lex-mvp
↓
kickstart_mvp(project_path, problem_statement, project_name?, resume=False)
list_mvp_checkpoints() # optional — the 6 checkpoints
run the lex-mvp-planner / lex-mvp-scoper agents
submit_mvp_plan(plan={...}) # problem, stakeholder, demo, criteria, out-of-scope, sources
submit_mvp_scope(entities, requirements, rationale)
scaffold_mvp() # server writes the deterministic skeleton
run the lex-mvp-implementer agent
record_implementation(files_written, notes)
run_boot_checklist() # gate — must pass to finalize
finalize_mvp() # writes mvp/<run_id>/MVP-REPORT.mdKickstart is not itself a checkpoint; the six are plan, scope, scaffold, implementation, boot-check and finalize. resume=True restores a session from .lex-mvp/manifest.json.
Hard caps
submit_mvp_plan and submit_mvp_scope return ok: false if you exceed:
- 10 requirements, each of at most 240 characters
- 5 entities, with at most 8 fields each
- a demo walkthrough of fewer than 3 steps
The caps exist so an MVP stays demonstrable in one sitting. If the scope genuinely does not fit, ship the MVP anyway and grow it with MVP completion. Calculations carry no numeric cap, but they must be real: dumb values still flow through the actual calculation pipeline.
Server-written skeleton, agent-filled bodies
scaffold_mvp() writes a deterministic skeleton — Inputs/, Uploads/, Reports/, demo/ with sample data, tests/ with a smoke test, plus model_structure.yaml, lex_config.py, requirements.txt and README.md. It never overwrites a file that already exists. The implementer agent only fills stub bodies with dumb-but-valid code.
run_boot_checklist() runs 15 requirements — 12 critical, 3 recommended — and finalize_mvp() refuses to close while any critical one fails. One of them, no-django-bootstrap, fails if manage.py, settings.py, urls.py, apps.py, asgi.py or wsgi.py appear: the Lex CLI owns those files, and an MVP that writes its own will not boot under lex start.
Git stays local. The mode runs git init -b main when there is no repository and makes one best-effort commit per completed checkpoint, staging only that checkpoint's own paths — never a remote, never a push. A failed commit never fails the tool, and LEX_MVP_NO_GIT=1 disables commits entirely.
Run artifacts land in mvp/<run_id>/ — 00-plan.md, 00-scope.md, 01-scaffold-manifest.md, 02-implementation.md, 03-boot-check.md, MVP-REPORT.md. Unlike the other flat modes, MVP keeps no _index.md; the report sits in the run folder.
MVP completion — expand to full product
Completion uses the same coordinator loop as forward but runs steps 9 to 19 — eleven steps, with planning steps 0 to 8 assumed done by the earlier MVP run. get_plan_step refuses any step below 9 and points back at step 9, so an agent cannot quietly restart planning.
kickstart_run(...) # existing project — MVP already done
loop step N = 9..19:
get_plan_step(step=N)
run lex-step-NN or lex-step-11-refactor
notify_step_complete(step=N, ...)
finalize_workflow() # stage 1 — returns audit instructions
# the coordinator writes plans/technical_docs/audit-report.md itself
finalize_workflow(audit_complete=True) # stage 2At step 11 the server chooses lex-step-11 or lex-step-11-refactor from project state; the coordinator never picks. Step 11 cross-checks the latest planning docs against the existing code and reconciles any drift before writing new code.
Completion is one of only two modes that touch GitHub. It commits and pushes after each step, opens a pull request from the run branch at finalize and squash-merges it, so run it on a repository where that is welcome. In the current build that merge is attempted unconditionally. See Git and GitHub and Forward.
There is no dedicated slash command: enter completion with switch_to_mode(target_mode="mvp_completion"), or let finalize_brief hand off to it. See Mode switching.
Was this helpful?
Your feedback shapes what we write next.
