chinmaireddy09·chinmaireddy09/fleet-command/skills/mission-control/SKILL.md

mission-control

Skill0 starsChanged 50 days agoLicence not identifiedView on GitHub

Fleet Command for any number of Claude Code sessions working one repo. The session that initiates it comes on watch as Control — the user's XO in the command post, owning the plan with them rather than relaying messages — and Control is whoever ran the command, not a post somebody has to deploy first. Gives each session a call-sign and its own git worktree, keeps a live board of who holds what and what is next, and spots when one station's work depends on another's so nobody guesses, waits or duplicates. Call-signs are initiated per job and retired when it lands — there is no fixed roster and no ceiling. Deploys a station in the background by default — no terminal opened, nothing typed, nothing taking your focus — or in a new tab or its own window if you ask for one, then verifies it really registered rather than trusting that something appeared. Works the same in every IDE and CLI, and /mc-config changes how stations appear in one keystroke. Control comes up already carrying its call-sign, so the name on the messages it sends is its own from the first one rather than a handle the shell generated. Coordinates changes that cross every area at once, and emails a human collaborator when a job needs them. Every wait has an expiry and silence is never taken as evidence. Runs only when explicitly invoked, as /mission-control or /mc.

• Commits and pushes