Flight Deck is for work that outlives a context window: multi-hour runs, background jobs, waiting on a decision, or any request like “where were we” or a status report. It keeps state in files that cannot be summarized away.
STATUS.md is rewritten in place to say only what is true now, LOG.md records decisions and dead ends, and an owner page shows a short status plus the decisions, tasks and gates that need a person.
What You Get
- A STATUS.md that is rewritten on every state change and read first after a compaction
- An append-only LOG.md of decisions, corrections and dead ends
- An owner page template with phase, milestones, a board of key work items and answerable asks
- Rules for consuming answers: record the decision, delete the item, then act
- A OWNER.md fallback for agents without the Artifact tool
Common Use Cases
- Running a multi-hour build with background jobs
- Answering a status question or producing a progress deck from one source of truth
- Collecting decisions from an owner who is not watching the session
- Resuming work after a context compaction without re-running paid jobs
What Makes It Unique
Status is rewritten in place, never appended, so every line is current, and evidence is recorded with its actual numbers so paid experiments are not repeated. Owner asks carry everything needed to answer them, including a recommendation, and a go on a one-way door must be typed in chat. A scheduled pass with no chat can consume answers but never passes a gate or publishes a page.
Under The Hood
The skill is instructions plus an HTML owner-page template and reference files. The agent writes STATUS.md and LOG.md in the repository, checks that listed processes are really running, and when the Artifact tool exists it publishes the page template and writes status and items to its database, then reads the saved answers. A reference describes scheduling a headless Claude Code pass with a shell command that reads a prompt from a file. The skill does not tell the agent to fetch general web pages.