Every command lightsout offers — what it does, when to reach for it, and what it leaves behind.
Shape a vague idea into a buildable direction through dialogue — checks whether it is one idea or several, offers 2–3 competing approaches with trade-offs and a recommendation, and converges on a design stated in plain words.
Produce a rigorous, implementation-ready plan for a feature — one a fresh-context agent can implement without guessing.
Plan a ticket alone — self-answers every question below a written escalation bar, shows you one proposal, and rolls onward per the `auto-plan` config block.
Run the lightsout deterministic implementation pipeline on a plan file.
Build one ticket straight from its body, with the repo's own gates as the only bar, and commit what passes.
Pick a parked run back up where it stopped, in the workspace that run recorded — same manifest, same work list, nothing repeated.
Take the current branch from committed work to merged and cleaned up, and write a typed result.
Drain the tracker of automatable tickets in parallel worktrees, relaying any question to this terminal or to a mailbox directory.
Create a work order, and change and show its record of the plans it holds, the mode they implement in, and its request to ship.
Write a ticket's planning status, its tracker workflow status, or both.
The engine's own check of a writing agent's change, run by that agent before it reports.
Burn down a repo’s standards-check findings (duplication, size, structure, boundary violations) in verified, resumable batches via the lightsout refactor pipeline.
Raise a repo’s unit-test coverage until its own coverage script passes, in verified, resumable batches via the lightsout coverage pipeline.
Check the repo against its standards packs and report every finding, machine checks and agent review alike.
Run every rule’s check against its own fixtures, so a rule that no longer detects what it claims fails loudly.
Report each rule’s coverage and how often agents decline it — which standards are actually holding.
Show what lightsout sees in this repo: config, harness, packs, any run still parked — and, for one run, what it is doing right now.
Show where a plan's hours and money went: every level of the run down to each harness process, with its time, tokens and cost.
Check the install end to end — config, harness, gates, standards — and name what is missing.
Collect what slowed the agents down across recent runs, so the next fix is the one that pays.
Feed this repo’s friction back to the lightsout engine as a change proposal.
Turn the spoken read-out of lightsout interview questions on or off for this project — `/lightsout:voice on` and `/lightsout:voice off`.