ops-yolo

OPS ► YOLO MODE

Phase 1 — Pre-gather ALL data

Run all of these simultaneously:

${CLAUDE_PLUGIN_ROOT}/bin/ops-infra 2>/dev/null || echo '{}'

${CLAUDE_PLUGIN_ROOT}/bin/ops-git 2>/dev/null || echo '[]'

${CLAUDE_PLUGIN_ROOT}/bin/ops-prs 2>/dev/null || echo '[]'

${CLAUDE_PLUGIN_ROOT}/bin/ops-ci 2>/dev/null || echo '[]'

${CLAUDE_PLUGIN_ROOT}/bin/ops-unread 2>/dev/null || echo '{}'

aws ce get-cost-and-usage --time-period "Start=$(date +%Y-%m-01),End=$(date +%Y-%m-%d)" --granularity MONTHLY --metrics "UnblendedCost" --output json 2>/dev/null || echo '{}'

cat "${CLAUDE_PLUGIN_ROOT}/scripts/registry.json" 2>/dev/null || echo '{}'

for d in $(jq -r '.projects[] | select(.gsd == true) | .paths[]' "${CLAUDE_PLUGIN_ROOT}/scripts/registry.json" 2>/dev/null); do
  expanded="${d/#\~/$HOME}"
  [ -f "$expanded/.planning/STATE.md" ] && echo "=== $(basename $expanded) ===" && cat "$expanded/.planning/STATE.md" && echo "---"
done

---

Phase 2 — Spawn 4 C-suite agents in parallel

Spawn these 4 agents simultaneously using all pre-gathered data as context. Each writes their analysis to a file in /tmp/yolo-[session]/:

Agent 1 — CEO (Strategic)

Uses agents/yolo-ceo.md. Writes /tmp/yolo-[session]/ceo-analysis.md.

• What's the #1 thing blocking growth right now?
• Are we building the right things?
• Where are we wasting time vs. creating value?
• What would you tell an investor today, unfiltered?

Agent 2 — CTO (Technical)

Uses agents/yolo-cto.md. Writes /tmp/yolo-[session]/cto-analysis.md.

• What's the worst technical debt that will bite us?
• Which services are time-bombs?
• Is the team/architecture set up to scale?
• What corners were cut that need fixing now?

Agent 3 — CFO (Financial)

Uses agents/yolo-cfo.md. Writes /tmp/yolo-[session]/cfo-analysis.md.

• Actual burn rate vs. runway
• Which AWS services are waste?
• When do we hit zero if nothing changes?
• What's the ROI on current work?

Agent 4 — COO (Operations)

Uses agents/yolo-coo.md. Writes /tmp/yolo-[session]/coo-analysis.md.

• What's falling through the cracks right now?
• Which processes are broken?
• What's the top execution risk this week?
• What should be automated that isn't?

---

Phase 3 — Hard Truths Report

After all 4 agents complete, synthesize into a unified report:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 YOLO ► HARD TRUTHS REPORT — [date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

 CEO: [1-2 brutal strategic truths]

 CTO: [1-2 brutal technical truths]

 CFO: [1-2 brutal financial truths]

 COO: [1-2 brutal operational truths]

──────────────────────────────────────────────────────
 CONSENSUS: The #1 thing that matters today is:
 [single most important action, no sugar-coating]
──────────────────────────────────────────────────────

 Full analysis files saved to:
 /tmp/yolo-[session]/ceo-analysis.md
 /tmp/yolo-[session]/cto-analysis.md
 /tmp/yolo-[session]/cfo-analysis.md
 /tmp/yolo-[session]/coo-analysis.md

──────────────────────────────────────────────────────
 Type YOLO to hand over the controls.
 I'll run your business autonomously for the next day.
 This means: closing inbox, merging ready PRs,
 fixing fires, advancing GSD phases, triaging issues.

 Or:
 a) Read CEO analysis
 b) Read CTO analysis
 c) Read CFO analysis
 d) Read COO analysis
 e) Execute top recommendation now
──────────────────────────────────────────────────────

---

Phase 4 — YOLO Autonomous Mode

If user types YOLO (all caps), enter autonomous mode via /loop:

Run the following in sequence, reporting after each step:

1. Inbox — Process all unread messages. Reply to humans, archive automated.
2. Fires — Fix any CRITICAL or HIGH production issues (dispatch agents).
3. PRs — Merge all ready-to-merge PRs (CI green, no unresolved comments).
4. Triage — Auto-resolve confirmed-fixed issues across Sentry/Linear/GitHub.
5. GSD — Advance the highest-priority active phase across all projects.
6. Linear — Update sprint board to reflect actual state.
7. Deploy — Trigger any pending deploys that are ready.
8. Report — Summary of everything done, what's left, and blockers.

After each step, check if new fires have appeared before proceeding. Report final summary when done.

If $ARGUMENTS is analyze or empty, go straight to Phase 1. If $ARGUMENTS is YOLO, skip to Phase 4. If $ARGUMENTS is report, skip to Phase 3 (reads existing analysis files if present).