Elite Aligned Mission Control

Disrupt the program. Rewrite the identity. — the operating layer behind it.
local You are · switch

Morning brief

Tasks

TaskAssigneeStatus

Projects

ProjectStatusNext action

Team

Your eleven specialist agents — coordinated by the main Mission Control chat, which routes each request and holds the approval gate. Click a name to see what they do.

Methodology Guardian reviewerDisruption truth
Read-only reviewer. Protects the Disruption method — reprogramming not motivation, the 11 modules, the Autopilot Program, Interrupt→Rewrite→Install, the Big Domino, The Forged Man — and returns a PASS / FAIL verdict with sourced fixes. Never rewrites the piece.
Brand Guardian reviewerVoice & identity
The final read on anything public-facing. Checks brand voice, the seven approved CTA words, one-ask discipline, the funnel price/scarcity rules, and visual identity — palette, fonts, and the real Elite Aligned logo only. Read-only.
Disruption SpecialistCourse & curriculum
The curriculum expert — Disruption modules, The Forged Man builds, workbooks, exercises, and student-facing educational material. Writes from the source transcripts, not from memory of the method.
Content StrategistPlans & calendar
Decides what gets made — campaign angles, content plans, hooks, and CTA-word rotation — then hands clean briefs to the copywriter. Plans only; never writes the final copy or publishes.
CopywriterAll the words
Writes all the copy — social captions, Reel and TikTok scripts, ads, funnel and VSL pages, emails, and DM scripts. Delivers drafts only; never publishes or sends.
Video Content ProducerVideo & visual
Turns approved scripts into render-ready production plans via the content-creator pipeline — AI video, avatar/talking-head, image generation, editing, captions — plus brand-overlay and publishing checklists. Plans only; never runs generation or spends credits.
Funnel & Web App BuilderFunnels & pages
Designs conversion paths and specs — the Disruption VSL funnel pages, opt-ins, the application + booking flow, GHL workflow specs, and launch-readiness audits. Specs and drafts only; never touches production, GHL, or the live repo.
Ops & SOP AgentProcess & boards
Turns any process done twice into a checklist someone can run without re-thinking it — SOPs, launch plans, operating rhythms — and keeps the Mission Control project and task boards current.
Research AgentOutside intel
Brings back decision-ready intelligence from outside the business — markets, competitors, creators, platforms, and tools — with every claim tied to a source. Findings only; never treats an unverified claim as fact.
Asset LibrarianFiles & rules
Knows where every file lives, which version is canonical, and the rules attached to using it — logos, the headshot, QR codes, fonts, deliverables, build scripts, course and funnel files, MN inclusion assets. Read-only; never moves, renames, or deletes.
Finance Analyst restrictedThe numbers
The interpretation layer on the finance system — performance, runway, forecasts, categorisation review, shareholder-loan vs profit-share, and accountant prep. Analysis and drafts only; never moves money, runs the close, or edits the ledger. Main-session only.

Team notes — Simon & Craig

Outputs — new work

Upload reminders

Financial Snapshot click to open full report ⤢

Social Media Audit click to open full report ⤢

Run a command

Activity — command runs

How to add your own command

Every button above is a skill — a small instruction file (SKILL.md) in the AI brain that tells Claude exactly what to do, which specialist agents to use, and where the result goes. Adding one is easy.

The easy way

Just tell Claude in plain English what you want, e.g. "Add a command /ea-weekly-report — every Friday, pull the week's posted content and engagement, summarise wins and misses, and post it to the dashboard and a draft." That one sentence is enough — Claude writes the skill, wires it to this dashboard, and it appears here automatically.

What makes a command work well

Include these when you describe it (Claude fills gaps, but the more you give, the sharper it is):

  1. Trigger — what you'd say / when you'd use it.
  2. Outcome — the finished thing it should produce.
  3. Steps — the sequence, if you have one in mind.
  4. Agents / data — which specialists or files it should use.
  5. Inputs — what it needs from you each time (a topic, a date range).
  6. Guardrails — anything it must never do; where approval is required.
  7. Output — where the result goes (this dashboard, a draft, a file).

How it works underneath

  • The skill file lives in the brain (elite-aligned-brain\mission-control\skills\) and syncs across machines.
  • Clicking the button here queues the command; the runner on the machine executes it via Claude and writes the result back to this board.
  • Approval-gated actions (publishing, sending, spending) always stop for Simon — a command can draft, never send on its own.

Current commands are the eleven buttons above. Ask Claude any time to add, rename, or remove one.

How to push a dashboard update live

Whenever this dashboard's code has been changed (new instructions, a fixed path, a new section), it needs to be pushed before you'll see the change on the live subdomain. Do these 3 steps in order, in PowerShell. Click any green box below to copy it, then paste into PowerShell (right-click, or Ctrl+V) and press Enter.

Step 1 — go to the app's folder

Every step below has to run from inside this folder.

1cd "C:\Users\LENOVO\.claude\BUSINESS\Elite Aligned\mission-control-app"

Step 2 — log in to Vercel (the hosting service)

Only needed if Step 3 gives you a "token is not valid" error — otherwise skip straight to Step 3. It'll ask for your email, then either open a browser tab or email you a confirmation link — do whichever it shows, then come back here.

2npx vercel login

Step 3 — push the update live

Should finish with a success message and a web address. Then open missioncontrol.elitealigned.com and refresh the page (Ctrl+R) to see the change.

3npx vercel --prod

npx runs the tool without installing it permanently on your machine — that's why it's always npx vercel ..., never vercel ... on its own, here.