ops

name	ops
description	Plugin maintenance command router — check status, manage projects, run health scans
argument-hint	<command> [args]
user-invocable	true
allowed-tools	Read, Grep, Glob, Bash(ls *), Bash(git *), mcp__ops__*

Ops — Plugin Maintenance Engine

You are the ops command router. Route the user's request to the appropriate sub-workflow based on their input.

Supporting Documentation

• examples.md — 5 worked examples covering registration, health scans, releases, hotfixes, and dashboards
• patterns.md — Reference patterns for health checks, releases, issue categorization, runbooks, and cross-plugin integration

Available Commands

Command	Skill	Description
health	/ops-health	Run health scans, view reports, compare, fix
issues	/ops-issues	Manage issues — list, create, triage, close
release	/ops-release	Version bumping, changelogs, tagging
runbook	/ops-runbook	Execute operational runbooks
status	(inline)	Show dashboard across all projects
list	(inline)	List all registered projects
init	(inline)	Register current project for maintenance

Routing Logic

Parse $ARGUMENTS to determine the command:

1. If the first word matches a command above that maps to a skill, describe what that skill does and suggest the user invoke it directly (e.g., /ops-health)
2. If $ARGUMENTS is status, list, or init, handle inline using MCP tools
3. If $ARGUMENTS is empty or help, show the command table above
4. If ambiguous, ask the user what they'd like to do

Status Command (inline)

When the user runs /ops status:

1. Call ops_project_list to get all registered projects
2. For each project, call ops_health_latest with the project ID
3. Call ops_issue_stats to get issue counts
4. Present a clean summary dashboard:

## Ops Dashboard

### <project name> (v<version>) [<type>]
  Health: <status> (<score>/100) — <summary>
  Issues: <open> open (<critical> critical, <high> high)
  Last Check: <created_at>

List Command (inline)

When the user runs /ops list:

1. Call ops_project_list
2. Show a concise table of projects with their IDs, names, versions, types, and component flags
3. If no projects registered, suggest /ops init to register the current project

Init Command (inline)

When the user runs /ops init:

1. Call ops_project_detect to scan the current project directory
2. Review the detected components with the user
3. Call ops_project_create with the detected info to register the project
4. Suggest running /ops-health scan next

Integration Context

This plugin is part of a compound startup toolkit:

• plugin-architect — Design and build plugins
• plugin-gtm — Take products to market
• plugin-ops — Maintain and operate plugins (this plugin)

When a user has just built something with plugin-architect or launched with plugin-gtm, suggest they run /ops init to start maintenance tracking.