RUN A CAMPAIGN
Ship Track — Step 2
A campaign is not a single build — it's a war. I read the PRD, break it into missions, and execute them one at a time. Kira runs recon, Dax analyzes the battlefield, and I call /assemble for each mission. When every mission is complete, the Victory Gauntlet runs automatically. That's how you ship.
SiskoWHAT IS A CAMPAIGN
A campaign takes your entire PRD and builds it mission by mission. Each mission maps to a feature or flow from the PRD. Sisko picks the next mission based on dependency order, runs the full /assemble pipeline for it — architect, build, review, UX, security, QA, tests — and only moves on when the mission passes all gates.
This is not a monolithic build. It's iterative, resumable, and tracks state across sessions. If context gets heavy or you need to stop, Sisko writes a checkpoint and picks up exactly where you left off.
KEY FLAGS
Launch Claude Code in your project directory, then start a campaign:
claude
> /campaignBy default, campaigns run autonomously with the full agent roster — no confirmation prompts between missions, auto-commits, auto-debriefs. Full review quality is preserved. Walk away and come back to a built project.
--interactive pauses for human confirmation between missions — useful when you want to inspect each one before proceeding. --fast trims review rounds (skips Crossfire + Council per mission) but is still comprehensive. --light uses standard agents only — no cross-domain spot-checks. --solo runs lead agent only, zero sub-agents — good for quick checks. --resume picks up from the last checkpoint — essential for multi-session campaigns. --plan updates the PRD without building. --mission "Name" jumps to a specific mission. --focus "topic" biases the Silver Surfer's agent selection toward a domain — e.g., --focus "api" loads more backend specialists.
THE CAMPAIGN LOOP
Every campaign follows the same loop: Kira runs recon on the current mission scope, Dax analyzes dependencies and risk, Sisko calls /assemble to execute the build pipeline, and the mission is verified against its gates. Repeat until the PRD is fully built.
Every 4th mission triggers a checkpoint gauntlet — a quick 3-round review of the combined system. Individual missions only review their own scope; checkpoints catch cross-module issues like missing imports, inconsistent auth, or API contract drift between features built in different missions.
Campaigns also extract learned rules — when the same root cause appears across multiple checkpoints, it becomes a persistent pre-flight check saved in campaign-state.md. Rules persist across sessions because they live in the file, not in context.
When the last mission completes, Sisko triggers the Victory Gauntlet — a full /gauntlet pass across the entire project. If it survives, you're ready to ship. If issues surface, they get logged as new missions and the campaign continues until everything is clean.