--- name: silver-devops description: This skill should be used for SB-orchestrated infrastructure/CI-CD workflow: intel → silver-blast-radius → devops-skill-router → devops-quality-gates (7 dims) → plan → execute (no TDD) → review → secure → ship argument-hint: "" version: 0.1.0 --- # /silver:devops — Infrastructure, CI/CD, IaC, Cloud Workflow SB orchestrator for infra, CI/CD, pipelines, Terraform, IaC, Kubernetes, containers, cloud, and ops work. **Key design principles:** - No brainstorming phase — infrastructure changes are driven by operational requirements established upstream (in silver:feature or silver:research). Blast-radius analysis replaces the product/engineering brainstorm. - Uses silver:devops-quality-gates (7 IaC-adapted dimensions) instead of the standard 9-dimension sweep at BOTH pre-plan and pre-ship gates. - TDD is not applicable for infra plans — explicitly skipped. **The 7 IaC quality dimensions:** reliability, security, scalability, modularity, testability, reusability, extensibility. (Usability omitted — no user-facing interface in IaC.) Never implements infra changes directly — orchestrates only. ## Pre-flight: Load Preferences Read the **User Workflow Preferences** section of `silver-bullet.md` to load user workflow preferences before any other step. ```bash grep -A 50 "^## [0-9]\+\. User Workflow Preferences" silver-bullet.md | head -60 ``` Display banner: ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SILVER BULLET ► DEVOPS WORKFLOW ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Change: {$ARGUMENTS or "(not specified)"} Mode: {interactive | autonomous — from §10e or session selection} ``` ## Composition Proposal Before beginning execution, read existing artifacts to determine context and propose which PATHs to include or skip. ### 1. Context Scan Check the following artifacts and set skip/include flags: | Artifact | Signal | Action | |----------|--------|--------| | `.planning/` directory exists | Project already bootstrapped | Skip FLOW 0 (BOOTSTRAP) | | `.planning/STATE.md` exists | GSD state present | Skip FLOW 0 (BOOTSTRAP) | ```bash # Check for existing planning artifacts [ -d ".planning" ] && echo "SKIP FLOW 0 — .planning/ exists" || echo "Include FLOW 0" ``` Note: FLOW 6 (DESIGN CONTRACT) and FLOW 8 (UI QUALITY) are never included in the devops workflow — infra has no user-facing interface. ### 2. Build Path Chain Construct the proposed flow chain for infrastructure/CI-CD work. Default chain: FLOW 0 (BOOTSTRAP) [skip if .planning/ exists] → FLOW 1 (ORIENT) → FLOW 5 (PLAN) → FLOW 7 (EXECUTE) → FLOW 10 (SECURE) [always included — infra work] → FLOW 11 (VERIFY) → FLOW 13 (SHIP) Note: FLOW 10 (SECURE) is always included for any infrastructure engagement. FLOW 6 (DESIGN CONTRACT) and FLOW 8 (UI QUALITY) are never included. ### 3. Display Proposal Display the composition proposal to the user: ``` ┌──────────────────────────────────────────────────────────────┐ │ SILVER BULLET ► FLOW COMPOSED │ ├──────────────────────────────────────────────────────────────┤ │ Flows: ORIENT → PLAN → EXECUTE → SECURE → VERIFY → SHIP │ │ Skipped: BOOTSTRAP — .planning/ exists; DESIGN/UI — infra │ └──────────────────────────────────────────────────────────────┘ Approve composition? [Y/n] ``` ### 4. Auto-Confirm in Autonomous Mode In autonomous mode (§10e), auto-confirm the composition proposal with a log message: ``` ⚡ Autonomous mode: auto-confirming composition — {path count} paths, {skipped count} skipped ``` ### 5. Create WORKFLOW.md If `.planning/WORKFLOW.md` does not exist, create it from `templates/workflow.md.base`: - Populate `Intent:` with the infrastructure change description ($ARGUMENTS) - Populate `Composed:` with the current ISO timestamp - Populate `Composer:` with `/silver:devops` - Populate `Mode:` with the current mode (interactive or autonomous) - Record the confirmed flow chain in the Flow Log section header After each path completes, write status to Flow Log table: ``` | {#} | FLOW {N} ({name}) | complete | {artifacts produced} | ✓ | ``` ## Step-Skip Protocol When the user requests skipping any step: 1. Explain why the step exists (one sentence) 2. Offer: A. Accept skip B. Lightweight alternative C. Show me what you have 3. If user chooses A permanently: record in silver-bullet.md §10b and templates/silver-bullet.md.base §10b, commit both. **Non-skippable gates:** `silver:security` (Step 3b), `silver:devops-quality-gates` pre-ship (Step 10), `gsd-verify-work` (Step 9). ## Step 0: Codebase Intel Invoke `silver:intel` (gsd-intel) via the Skill tool. Purpose: orient in the codebase — understand current infra topology before silver-blast-radius analysis. If no intel files exist: invoke `silver:scan` (gsd-scan) via the Skill tool for rapid structure assessment. ## Step 1: Blast Radius Analysis Invoke `silver:silver-blast-radius` via the Skill tool. Purpose: map change scope, downstream dependencies, failure modes, and rollback plan. This step replaces the product/engineering brainstorm for devops workflows. ## Step 2: DevOps Skill Router Invoke `silver:devops-skill-router` via the Skill tool. Purpose: route to the right IaC/cloud skill — Terraform, Pulumi, AWS CDK, k8s, or other tooling appropriate for the change. ## Step 3: Pre-Plan DevOps Quality Gates (7 IaC dimensions) Invoke `silver:devops-quality-gates` via the Skill tool. Purpose: 7 IaC-adapted quality dimensions (reliability, security, scalability, modularity, testability, reusability, extensibility) as the pre-plan gate. Note: this is NOT the standard 9-dimension silver:silver-quality-gates. The devops workflow uses silver:devops-quality-gates exclusively at both quality gate positions. ## Step 3b: Infrastructure Security (mandatory, non-skippable) Invoke `silver:security` via the Skill tool. Purpose: infrastructure security hard gate — mandatory independent of §10 preferences. Checks secrets, IAM permissions, network exposure, and data handling. ## Step 4: Discuss Phase Invoke `gsd-discuss-phase` via the Skill tool. Purpose: DevOps phase context → CONTEXT.md with locked decisions for the planner. ## Step 5: Plan Phase Invoke `gsd-plan-phase` via the Skill tool. Purpose: PLAN.md for the infrastructure change. ## Step 6: Execute Phase (TDD skipped) If mode is Interactive: invoke `gsd-execute-phase` via the Skill tool. If mode is Autonomous (§10e): invoke `gsd-autonomous` via the Skill tool. **TDD is explicitly skipped for infra plans — not applicable.** Infrastructure and configuration work is declarative; there is no red-green-refactor cycle that applies to IaC resources. No silver:tdd invocation. ## Step 7: Code Review (IaC review) Run review sequence in order: 1. Invoke `silver:request-review` (superpowers:requesting-code-review) via the Skill tool. 2. Invoke `gsd-code-review` via the Skill tool. If issues found: invoke `gsd-code-review-fix`. 3. For architecturally significant infra changes: invoke `gsd-review --all` via the Skill tool (fans out to all available external CLIs for cross-AI review). 4. Invoke `silver:receive-review` (superpowers:receiving-code-review) via the Skill tool. ## Step 8: IaC Security + Secrets Verification Invoke `gsd-secure-phase` via the Skill tool. Purpose: IaC security and secrets verification — confirm no credentials in code, correct IAM boundaries, secure defaults. ### Deferred-Item Capture (mandatory) During and after execution, any item that is skipped, descoped, out of scope, explicitly deferred, or identified for future work MUST be filed immediately via `/silver-add` — do not accumulate silently. ``` Skill(skill="silver-add", args="") ``` **Classification quick-reference:** - Bug, regression, broken behavior, blocking question, unfinished work → files as **issue** - Feature request, tech debt, advisory finding, informational question, housekeeping → files as **backlog** - When ambiguous → files as **backlog** (do not over-alarm with issues) **Minimum bar:** Only file items with distinct impact OR that block future work OR represent a conscious deferred decision. Do not file transient notes or items already addressed this session. ## Step 9: Deployment Verification Invoke `gsd-verify-work` via the Skill tool. Purpose: deployment verification and UAT. Non-skippable gate. ## Step 10: Pre-Ship DevOps Quality Gates (7 IaC dimensions) Invoke `silver:devops-quality-gates` via the Skill tool again. Purpose: final 7-dimension sweep before deploy — same gate as Step 3, applied post-implementation. Non-skippable. ## Step 10b: Doc-Scheme Compliance (conditional) **Only if `docs/doc-scheme.md` exists in the project:** ```bash [ -f "docs/doc-scheme.md" ] && echo "Doc-scheme gate required" || echo "No doc-scheme — skip" ``` Before deploying, verify documentation is up to date per the scheme: 1. **`docs/CHANGELOG.md`** — must have an entry for the infrastructure change (newest-first). If missing, write it now. 2. **`docs/ARCHITECTURE.md`** — update §Current State if the change altered infrastructure topology, pipeline stages, or deployment targets. 3. **`docs/knowledge/YYYY-MM.md`** (current month) — if IaC patterns, provider quirks, or config gotchas were encountered, append them. 4. **`docs/lessons/YYYY-MM.md`** (current month) — if portable DevOps lessons were learned, append them. **Gate:** Do NOT proceed to Step 11 until all applicable checks pass. If no `docs/doc-scheme.md` exists: skip this step entirely and proceed to Step 11. ## Step 11: Ship / Deploy Invoke `gsd-ship` via the Skill tool. Purpose: push branch, deploy, create PR.