Open source · Claude Code package

Claude Code does too much itself, and calls it done too soon. Flight Deck fixes that.

Flight Deck is a package of skills and hooks for Claude Code. It fixes seven default weaknesses at once: no delegation, no sense of model tier or effort, no pushback on over-engineering, loose testing discipline, a short memory, and no cost discipline. Install it once, and mission control becomes the default.

Notify me on new versions

The problem, axis by axis

Seven default weaknesses. One fix each.

Out of the box, Claude Code runs everything itself, treats every task the same, and forgets what it already knows. Flight Deck reroutes each of these to the crew station built for it.

Delegation

Runs everything itself, one thread at a time

Splits work into lots and delegates each to a subagent, in parallel

Model tier

Same tier for a typo fix and an architecture call

Routes each lot to the tier its difficulty earns: cheap for mechanical work, default for most of it, top tier reserved for judgment calls

Reasoning effort

One fixed effort level for everything

Calibrates effort per lot alongside the tier

Over-engineering

Adds abstraction layers, defensive code, and tests nobody asked for

Pushes back by default: no layer until a second real use case exists, no guard against inputs that cannot occur

Testing discipline

Calls it "done" on the strength of a diff

Picks the proof before writing code, runs the repository's own named check, cites the output

Memory and docs

Re-derives what is already known, skips the project's own notes

Recalls persistent memory and reads local docs before planning anything substantial

Cost

No sense of what a session is spending

Keeps the top tier in planning and verification only; execution goes to the cheapest tier that clears the bar

Install

One prompt installs it.

Paste this into a fresh Claude Code session.

installer prompt

Install the Flight Deck skill package for me from https://github.com/CaseReed/flight-deck, following these steps exactly and stopping for confirmation where noted.

1. Clone the repo into a temporary directory (for example /tmp/flight-deck) and read its README.md, CLAUDE-md-activation.md, skills/, and hooks/ so you know what you are installing.

2. Check for an existing install first. Look for ~/.claude/skills/mission-control/ and ~/.claude/skills/test-discipline/, and check whether ~/.claude/CLAUDE.md already has a Flight Deck activation block. If everything is already in place, tell me and stop there. Do not re-run steps or overwrite anything that is already installed.

3. Copy the skill folders. Copy skills/mission-control/ and skills/test-discipline/ from the clone into ~/.claude/skills/. If either folder already exists there, show me a diff against the incoming version before doing anything, and ask whether to overwrite, skip, or merge. Never overwrite silently.

4. Update ~/.claude/CLAUDE.md. Read CLAUDE-md-activation.md from the clone. If ~/.claude/CLAUDE.md does not exist yet, show me its full proposed contents and ask before creating it. If it exists and already contains this activation block (or an equivalent one covering the same triggers and opt-outs), tell me and make no change. Otherwise, show me the exact diff you intend to apply, including where it gets appended, and wait for my explicit confirmation before writing anything.

5. Offer the hooks, do not install them on your own. Read hooks/HOOKS.md from the clone. Show me what verify-reminder and fanout-guard each do, and the exact JSON that would be added to ~/.claude/settings.json to register them. Ask which ones, if any, I want.

Only once I confirm: copy the chosen hook script(s) into ~/.claude/hooks/ and make each one executable with chmod +x. If settings.json already has content in the relevant section, show me the diff before writing it, otherwise just apply the change. Before reporting a hook as registered, check that jq is installed and on PATH, and warn me if it is not, since both hooks need jq to run.

6. Finish with a plain summary: which files you copied, what, if anything, got appended to CLAUDE.md, and which hooks, if any, got registered. For anything I declined, say it was skipped and how to run it later. Then remove the temporary clone.

Do not write to CLAUDE.md or settings.json without showing me the change first and getting a yes. If the package is already installed, say so and stop instead of repeating the steps.