AI Agent Workflow Collection

Check mission status and progress via fresh subagent. Queries Beads for features, tasks, bugs, and recent work activity. Keeps HOUSTON context lean.

The flight plan — a decisions-first implementation plan, filed before launch. Leads with what you're most likely to tweak (data model, interfaces, anything user-facing); no code until you've reacted to the decisions.

The flight — execute the filed flight plan step by step. Creates the topic branch, dispatches a fresh TDD subagent per step, lands each step as its own commit, and tracks progress in flightlog.md so an interrupted flight resumes. Opt-in --flight-following adds a per-step drift review.

Heritage hardware — build a spec from a flight-proven reference. Use when you can point at code (a vendored crate, a file, a repo, a URL) that already behaves the way you want: it extracts the semantics worth porting.

The press kit — package the mission for stakeholder buy-in. Bundles the demo, the plan, and the deviations into one doc you can drop in Slack; anticipated concerns answered before they're raised.

The simulator — disposable HTML prototypes with fake data. Use when you'll only recognize what you want on sight: layouts, dashboards, flows, visual directions. Crash here, where it's free — nothing wires into the real app.

The tiger team — convene an independent adversary to attack the mission. Optional beat with two gates: after flightplan (attack the plan while it's cheap to change) or after the flight (attack the diff before merge). Uses Codex when installed; otherwise a three-lens Claude panel.