This page describes the pinned development build. There is no public release to install today, so the commands below explain the operating model rather than offer setup instructions.
Coldstart gives six names to six deliberate entrances. Four sit around the life of a work session: plan it, start it, inspect it without starting, and close it. Two sit outside the loop and maintain the harness itself. Six is the count in the build reviewed here, not a promise about what a release will ship.
Each of the six is something you could do by hand. Coldstart's difference is not a new ability; it is a stable place and a named moment for each one, so the same project files carry the agreement across fresh sessions.
Scroll sideways for the rest of the diagram
One day with the six commands
You want managers to be able to download the orders they are looking at as a CSV file.
| Situation | Manual workflow | Coldstart entrance | Observable result | Nearest limit |
|---|---|---|---|---|
| The change is larger than one safe session | Write notes or begin coding and organize later | /prep | Plan files and a saved route to the first session; no application code | A detailed plan can still rest on a bad assumption |
| The plan exists and you are ready to work | Paste a handoff and ask the agent to inspect the repo | /coldstart | The saved route and active plan are read; scope is announced before work | The announcement is intent, not containment |
| You only want to see where things stand | Ask for a summary and hope the agent stops there | /orientate | Current saved state and installed inventory are printed without a write | A read-only report can still report stale state |
| The authorization check fails at the end | Explain the failure in chat and remember to revisit it | /done | Named checks and the blocked result are recorded for the next session | A weak check or inaccurate writeback remains weak evidence |
| Renames and queued work have accumulated | Search, clean and rebuild indexes by hand | /cleanup and /maintenance | Findings are proposed; generated views are rebuilt and compared | They check the harness, not the application outcome |
The ordinary workflow is perfectly adequate for a small change you will finish today. The named entrances earn their cost when reconstruction, handoff and upkeep repeat often enough that “I will remember” has become part of the operating risk.
What the names mean
/prep is the planning entrance. It turns a project idea or a later planned area into durable plan
files and does not build the application.
/coldstart is the working entrance, and the only one. It reads the saved address to current
work—a resume pointer—then the active plan, announces the session boundary and continues into
the plan.
/orientate is the inspection entrance. It prints saved state and inventory, makes no write and
does not proceed into work.
/done is the closing entrance. It walks the named checks and records what happened, including a
failed or unrun check, before rewriting the route for the next session.
/cleanup runs the slower, judgment-heavy sweep and proposes responses. /maintenance rebuilds
replaceable views from their authored sources and re-measures named harness conditions. Neither is
a general code-cleanup command.
Each name is one entrance to one declared behavior, and reaches it whether you type the command or make a matching request in your own words. What that buys is repeatability: the step happens the same way each time. It does not prove that the plan, the code, the check or the recorded judgment behind it is correct.
Next
One of the six deliberately stops before it does anything. Continue with looking without touching to see what a read-only entrance prints, and where it refuses to go next.