OPS — Next Action

What it does

This skill evaluates pre-gathered operational signals (infrastructure health, unread communications, CI/PR status, sprint issues, and GSD revenue phases) and produces a ranked next-action recommendation. It synthesises data to tell operators exactly what to do next: handle infra fires, triage urgent messages, review merge-ready PRs, or focus sprint/GSD work.

When to use it

Use when you want a concise operational priority: morning standups, on-call triage, release readiness checks, or whenever you need a one-line directive plus a short rationale. It is designed to run against collected telemetry and can be constrained to a project alias.

What's included

• Scripts: none bundled in this skill (uses environment pre-gathered data hooks)
• References: in-repo docs and runtime guidance for CLI/API usage (gh, custom ops helpers)
• Instructions: priority stack and output template; guidance to run subagents for parallel checks; explicit preflight commands for GH, CI, and project state checks.

Compatible agents

Best suited for agents with shell/CLI and WebFetch capabilities (Claude Code / OpenClaw style agents). It expects access to pre-gathered data endpoints and standard CLI tools (gh).