superlite

superlite

  A software factory. Approve a plan once, then it builds the code.

Use it

Install it (below), open a session in your project, and say what you want. superlite shows a one-screen intro the first time; /superlite:intro brings it back and /superlite:help has every detail.

Each run starts its own session automatically (superlite-cli session ensure): a branch superlite/sessions/ in your checkout, or a parallel worktree if another run is still open. Shipping closes it. See Sessions.

Say what you want

Or use a command

Plain words work just as well; the commands are shortcuts.

Who orchestrates

- Human orchestrator. You get a plain-language review plan with diagrams (a .review.md, about two pages, with a rough time and cost), and nothing is linted, dispatched or sent to an agent until you reply approve. Any clear approval counts (yes, go ahead, looks good, or similar), including a longer note. After that you are not asked again: any change to scope is recorded as a ruling and listed at the end under "Changed from the approved plan". Small inline work needs only your yes in chat.
- AI orchestrator. It plans, lints, dispatches and rules on open choices itself, with no review plan and no questions.

Both stop for destructive, outward (push, merge, publish) or security-sensitive actions, and superlite never commits during a run: finished tasks are hidden checkpoints. A checkpoint is a hidden save of one task under refs/superlite/*. At session end, shipping asks once: "Commit to " or "Leave uncommitted".

Watch a run

Let it run. Watch .superlite/ in your project: progress.md has the rulings and the log, test-summary.json the latest test result, metrics.jsonl and the run history the time and cost per agent.

A read-only view, offered when you approve the plan…