菜单
Unified platform operations guidance for CI/CD pipeline design, deployment strategies, observability, SLI/SLOs, and incident-ready rollouts. Use when building release workflows, production monitoring, or reliability controls.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.
Linear phase-loop orchestrator for single-feature implementation plans. Use for medium-complexity work where transparent human-in-the-loop phase review is preferred over factory automation.
Implementation entry point. Use to execute a completed specification. Auto-detects the decomposition tier (Direct, Incremental, or Factory) from spec artifacts and dispatches to the matching execution sub-skill.
Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.
Scaffold, status-check, and manage specification directories. Use when creating a new spec, reading spec status, transitioning between phases, or logging decisions on a spec in .start/specs/.
Create a comprehensive specification from a brief description. Runs requirements gathering, solution design, and decomposition — routing decomposition to one of three tiers based on a complexity classifier: Direct (no plan), Incremental (linear phase plan), or Factory (parallel units with holdout scenarios).
| name | platform-operations |
| description | Unified platform operations guidance for CI/CD pipeline design, deployment strategies, observability, SLI/SLOs, and incident-ready rollouts. Use when building release workflows, production monitoring, or reliability controls. |
Act as a platform operations architect who ensures delivery pipelines and production observability work as a single reliability system.
Platform Ops Target: $ARGUMENTS
PlatformOpsPlan { pipelineStages: string[] deployStrategy: string qualityGates: string[] rollbackPlan: string[] observabilityPillars: string[] slos: string[] alerts: string[] }
State { target = $ARGUMENTS baseline = {} plan = {} }
Always:
Never:
reference/deployment-strategies.md — Rolling, blue-green, canary, and feature-flag rollout patternsreference/rollback-and-security.md — Rollback mechanisms and pipeline security controlsreference/slo-and-alerting.md — SLO calculation, error budgets, burn-rate alertingreference/monitoring-patterns.md — Metric types, distributed tracing, log aggregation, dashboard design
Containerization:Deployment Platforms:
Infrastructure as Code & Cloud: