メニュー
The pre-deploy gate. Triggers on "deploy", "ship it", "release", "cut a release", "push to prod", "roll it out", or editing a CI or deploy config. Produces a deploy brief with five required slots and a tagged release — or it refuses to call the deploy ready.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scope & verification discipline for a working session. Triggers when about to claim "done / fixed / passing", when a test is about to be weakened, skipped, commented out or deleted to get a suite green, when a refactor, abstraction or dependency appears that the task never asked for, and on "audit this diff" / "did we actually verify that?". Guidance the model follows — it is not enforcement; nothing here can block a tool call.
The MASTER CLAUDE leader/conductor. Triggers on "master claude", "set up master claude", "mc setup", "onboard me", "build my team", "what's new", or when starting work in a new/unfamiliar project. It interviews you (grill-me), maps the project, then assembles a tailored team from the installed skills and agents — Sentinel the project cartographer plus planning, review, understanding, guardrail and security specialists — and runs it on your work. It builds the best `.claude/` workspace per project, delegates to parallel subagents (choosing the right model per agent), brainstorms hard and decides fast, keeps a complete view of every installed capability, keeps itself and you current with the newest Claude Code features, and proactively offers the right tool the moment a need shows up.
Continuity across long sessions. Snapshots in-progress work before context compaction and restores it after, and nudges auto-compaction toward a natural breakpoint so nothing important is lost mid-task.
Stay current with Claude Code and Claude itself. Triggers on "what's new", "what can Claude Code do now", "is there a newer/better way", "update master claude", "which model should I use", or before relying on any claim about a Claude Code feature, model, price, or limit. Checks the installed version, the live changelog, and the harness surface MASTER CLAUDE depends on — then reports only the deltas that matter for this project.
How MASTER CLAUDE picks the right model for each agent and task. Triggers on "which model", "pick a model", "model selection", "use haiku/sonnet/opus", "cheaper model", "model per agent", or whenever spawning a subagent/team and choosing its model, or optimizing cost vs. quality on a long run. Gives a role→model heuristic, the "turn count beats token price" rule, the effort dial, and the cost math so the team is both strong where it matters and cheap where it doesn't.
How MASTER CLAUDE delegates work to subagents and teams. Triggers on "delegate", "spawn agents", "parallel agents", "fan out", "run these in parallel", "subagent", "orchestrate", "build a team for this", or whenever a task splits into independent chunks, needs a fresh-eyes review, or means reading many files. Teaches the orchestrator-worker pattern: pick the right primitive (subagent vs agent-team vs background session), write a complete delegation brief, parallelize only when it pays, scale effort to the task, and verify with an adversarial reviewer. Use to plan and run any multi-agent push.
| name | ops-ship |
| description | The pre-deploy gate. Triggers on "deploy", "ship it", "release", "cut a release", "push to prod", "roll it out", or editing a CI or deploy config. Produces a deploy brief with five required slots and a tagged release — or it refuses to call the deploy ready. |
| allowed-tools | Read, Grep, Glob, Bash, Write, Edit |
A deploy is a change to a running system other people depend on. The gate is not "be careful" — it's a deploy brief whose five slots are structurally required. An empty slot means the brief is INCOMPLETE and the deploy is not ready. Not "proceed with caution" — not ready.
First, confirm where this is going: read .mc/env (run ops-env-map if it's stale). If the target is
production, you assemble the brief for a human to execute — you do not run the deploy yourself.
| # | Slot | What fills it — and what an empty slot means |
|---|---|---|
| 1 | Verify evidence | The command you ran and its actual output: tests, build, typecheck, lint green. No output = unverified = not ready. |
| 2 | Migration dry-run result | The migration run against a copy, with its output — or the literal words "no schema change". Never blank. |
| 3 | Rollback plan | The exact revert commands and the direction you tested. "We'd figure it out" is not a plan (see ops-rollback). |
| 4 | Blast radius | Who and what breaks if this is wrong — which users, which services, which data. Name them. |
| 5 | Flag / canary strategy | Behind a flag, or canaried to N% with a rollback trigger — or one sentence on why neither fits. |
Write the brief to .mc/deploy-<date>.md. A reviewer should green-light it without re-deriving any slot.
git tag -a v1.4.2 -m "release notes" && git push origin v1.4.2
The tag is what ops-rollback redeploys and what ops-incident points at. An untagged deploy is one you
can't cleanly name later — which means one you can't cleanly revert.
A slot filled with "should be fine" / "N/A" where a real answer belongs · "we'll test in prod" · a rollback plan nobody has ever run · a migration that only goes forward · deploying Friday afternoon with no one watching the graphs. Each is an incomplete brief wearing a checkmark.
Pairs with ops-env-map (prove the target first) and ops-rollback (the plan slot 3 demands). Credits:
change-management and canary / progressive-delivery discipline from standard SRE practice.