メニュー
Choose and wire a progressive-delivery strategy — blue-green, canary, rolling, or feature-flagged — by blast radius and reversibility, with a health-gated promotion and an automated, rehearsed rollback.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/mcorbett51090/RavenClaude --skill progressive-deliveryコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Route everyday, well-defined work (single-file edits, test-writing, summarization, mechanical refactors, boilerplate) to a cheaper coding agent (Grok or Copilot CLI) instead of doing it in the main Claude session, escalating multi-file/architecture/debugging/security work to Claude. Opt-in via the `cheap_lane:` comfort-posture knob.
Authors, validates and packages a claude.ai Organization Skill — the intake questions, the trigger and scope exercises, then lint, pack and verify against measured platform constraints. Reach for this when someone wants to publish a Skill to their organization, or when an upload was rejected and the reason is unclear.
Drafts a reply to an inbound customer email, grounded in the account record and the published help-centre articles rather than in recall. Use when a customer emails about billing, a renewal or an outage, when a reply must cite current policy, or when a teammate asks for a first draft to edit.
SOC 職業分類に基づく
SKILL.md を表示中
| name | progressive-delivery |
| description | Choose and wire a progressive-delivery strategy — blue-green, canary, rolling, or feature-flagged — by blast radius and reversibility, with a health-gated promotion and an automated, rehearsed rollback. |
Purpose: ship to production safely by matching the rollout to the risk.
| Situation | Strategy |
|---|---|
| Stateless, fast rollback | Canary (1% -> 10% -> 100% on signal) |
| Need instant cutover/rollback | Blue-green |
| Risky/irreversible behaviour change | Feature flag (deploy dark, release later) |
| Schema change | Expand/contract migration before the deploy |
A canary promotes on an SLO / error-budget burn-rate signal from observability-sre, not a timer. Define the abort condition and the rollback action before you ship, and rehearse the rollback.
Separate them: deploy the bytes dark, flip the flag to release. A bad release becomes a flag flip.