Claude Ops

Features

• Prioritizes business tasks based on a defined stack (fires, comms, PRs, sprints, GSD work)
• Aggregates data from infrastructure, communication channels, PRs, and sprint boards
• Integrates with various services via CLI tools and MCP
• Provides clear output guiding the user to the next best action
• Includes robust setup, security, and fallback mechanisms

Use Cases

• Starting the day with a prioritized business briefing
• Identifying and addressing critical infrastructure issues or fires
• Managing communication overload by surfacing urgent messages
• Streamlining the PR review and merge process
• Focusing on the most impactful sprint tasks or revenue-generating work

Non-Goals

• Performing destructive actions directly; relies on other skills/tools for execution
• Collecting or transmitting telemetry, analytics, or crash reports
• Replacing individual service dashboards; acts as a consolidated overview

Workflow

1. Load runtime context (preferences, daemon health, memories)
2. Gather pre-gathered data from infrastructure, git, CI, comms, and sprint tools
3. Apply the priority stack (fires > comms > PRs > sprint > GSD work)
4. Determine the top priority action and rationale
5. Format and present the 'OPS ► NEXT ACTION' summary to the user
6. Allow user to select an action or describe their next step

Practices

• Business operations prioritization
• Data aggregation and analysis
• Actionable intelligence
• Security best practices
• Developer workflow automation

Prerequisites

• Claude Code 1.0+
• Dependencies installed automatically via Homebrew (macOS), apt (Linux), or winget (Windows)
• Optional: API keys/tokens for integrations (e.g., Stripe, RevenueCat, GitHub)