mission-control-blueprintlisted

Turn a business into a deployable Mission Control build that runs in Claude Cowork with a live dashboard served on a local server. Input can be a discovery/scoping/kickoff transcript, ops notes, an ops-ai-advisor report, an existing conductor-blueprint, or just a description of the next system you want. Use whenever you want to map, scope, blueprint, or "spin up" a Mission Control — for your own use OR a client prototype — with triggers like "blueprint a mission control", "build a mission control for [business]", "scope a mission control", "turn this into a mission control", "mission control for this client", "repurpose mission control for X", or "what would a mission control do for them". Produces a BUILD PACKET (PRD, folder tree + data-schema contract, scheduled-task prompts, the local-server dashboard + serve script, a Cowork kickoff prompt, and a wiring checklist) plus a plain-language CLIENT-FACING PLAN. Use this even if they don't say "skill" or "blueprint" explicitly.
mikeleewoodai/mission-control · ★ 0 · AI & Automation · score 70

Install: claude install-skill mikeleewoodai/mission-control

# Mission Control Blueprint Translate a business into a deployable **Mission Control** — a single Claude Cowork workspace that unifies recurring work into scheduled workflows, on-demand skills, and a **live dashboard served on a local server**. This skill maps what a business needs onto Mission Control's primitives so you can drop the packet into Cowork and stand the system up. Always produce two deliverables: a **Build packet** (internal) and a **Client-facing plan** (or, when the target is you's own use, a short scope confirmation in its place). **Mission Control vs. Conductor OS — pick the right tool.** Conductor (see `conductor-blueprint`) is skills-only, runs unattended on the client's own monthly plan, no servers — best for lightweight always-on automation the client owns. Mission Control is heavier and visual: a Cowork project with a local data layer and a dashboard you open in a browser. Choose it when the value is a **command center** — seeing brief + gauges + pipeline + inbox in one place — when there's a richer data layer to maintain, or when it's a **prototype you build here and may later promote** (the am-conductor pattern). If the ask is purely "automate these recurring tasks on their plan," route to `conductor-blueprint` instead. --- ## The architecture you are mapping onto Mission Control = a **Cowork project on a local folder** + the **Productivity plugin** foundation + **N domains** + a **data layer** + **interaction patterns**. - **Foundation:** the