Six agents, one to each stage of the build.

Flightcrew runs spec-driven development for security controls. Forward deployed security engineers direct it and your team reviews what it proposes.

Flightcrew one control in flight

01running

atlas

spec.md · 6 scenarios

02running

flightplan

plan · 4 changes

03running

scout

scope · 2 of 4 first

04running

pilot

wt/egress-allowlist

05running

copilot

6 of 6 recorded

06running

debrief

ready for review

Review is the human gate, and it stays where it is. building

The crew.

01 AtlasStates what the control has to do Reads the environment and states what the control has to do.

02 FlightplanOrders the changes for review Orders the changes, each one small enough to read.

03 ScoutFinds the smallest version that works Cuts the plan to the smallest version that works end to end.

04 PilotFlies the Flightcrew protocol Flies the flight plan in smooth skies and through turbulence.

05 CopilotRuns the control against its scenarios Runs it against the scenarios Atlas named and records what each did.

06 DebriefRewrites what came back wrong Rewrites what came back wrong, before the change is proposed.

flightcrew-skills is the review crew as open source. Independent models from different families review the change and report. They never edit it.

Claude Code

$ /plugin marketplace add akasecurity/marketplace
$ /plugin install flightcrew@akasecurity