When progress keeps getting lost
A migration, a substantial interface, or a difficult repair can span several sessions. Long Horizon stores the goal, verified progress, failed approaches, and remaining checks in project files.
Finish a large project / 01
Long Horizon
Keep the goal intact when the work outgrows a session.
01 / Build
02 / Repair
03 / Continue
STATE.MD / MANAGER OWNS THIS
A finish line that stays put
Goal: a homepage that works in Firefox and Chromium.
Check: navigation fits at 390px.
Phase: executing.
Worker: fresh executor A.
One bounded
piece of workA new worker receives the goal, scope, and evidence it needs.
piece of workA new worker receives the goal, scope, and evidence it needs.
The manager keeps the contract and saved progress. Executors build. Independent auditors inspect.
Each round earns its place
A fresh executor handles one bounded step. A separate auditor checks the result. A failed audit sends the step back for repair; it does not quietly weaken the acceptance checks.
What you keep
A durable state file, round briefs, work artifacts, evidence, and audit verdicts. A fresh worker can continue from inspected progress instead of reconstructing the conversation.
What it needs
Fresh independent agents must be available. Self-review cannot replace the auditor. Saved state does not schedule a future run, and the skill does not authorize publishing or merging.
The example, without playback
Round 1 builds the homepage. An independent audit finds clipped navigation. Round 2 repairs wrapping and passes the original browser check. The manager saves the evidence. A fresh worker in round 3 reads that state and continues to the next bounded step. Human review still controls release.
Give it a clear task
Name the outcome, allowed scope, and evidence that would convince you. For example: build a homepage that works in Firefox 140 and Chromium, with readable navigation at 390px.
$long-horizon Build and verify the homepage in bounded rounds. Check Firefox 140, Chromium, and navigation at 390px.