specweave 1.0.577 → 1.0.579

package/plugins/specweave/marketplace.json

@@ -0,0 +1,114 @@
+{
+  "$schema": "https://spec-weave.com/schemas/skill-marketplace.v1.json",
+  "plugin": "sw",
+  "version": "1.1.0",
+  "description": "Skill-level marketplace catalog for the specweave plugin. Lists deprecation state, replacement pointers, and alias routing for each skill.",
+  "skills": [
+    {
+      "name": "sw:github-sync",
+      "path": "skills/github-sync/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.1.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": "sw-github:sync-spec",
+      "migrationWarning": "sw:github-sync is deprecated. Use sw-github:sync-spec for push/pull operations. Scheduled for removal in v1.3.0."
+    },
+    {
+      "name": "sw:jira-sync",
+      "path": "skills/jira-sync/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.1.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": "sw-jira:push / sw-jira:pull",
+      "migrationWarning": "sw:jira-sync is deprecated. Use sw-jira:push (content) or sw-jira:pull (status) instead. Scheduled for removal in v1.3.0."
+    },
+    {
+      "name": "sw:ado-sync",
+      "path": "skills/ado-sync/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.1.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": "sw-ado:push / sw-ado:pull",
+      "migrationWarning": "sw:ado-sync is deprecated. Use sw-ado:push (content) or sw-ado:pull (status) instead. Scheduled for removal in v1.3.0."
+    },
+    {
+      "name": "sw:tdd-red",
+      "path": "skills/tdd-red/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.1.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": "sw:tdd-cycle --phase red",
+      "alias": {
+        "from": "/sw:tdd-red",
+        "to": "/sw:tdd-cycle --phase red",
+        "migrationWarning": "sw:tdd-red is deprecated. Use sw:tdd-cycle --phase red instead."
+      },
+      "migrationWarning": "sw:tdd-red is deprecated. Use sw:tdd-cycle --phase red instead. Scheduled for removal in v1.3.0."
+    },
+    {
+      "name": "sw:tdd-green",
+      "path": "skills/tdd-green/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.1.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": "sw:tdd-cycle --phase green",
+      "alias": {
+        "from": "/sw:tdd-green",
+        "to": "/sw:tdd-cycle --phase green",
+        "migrationWarning": "sw:tdd-green is deprecated. Use sw:tdd-cycle --phase green instead."
+      },
+      "migrationWarning": "sw:tdd-green is deprecated. Use sw:tdd-cycle --phase green instead. Scheduled for removal in v1.3.0."
+    },
+    {
+      "name": "sw:tdd-refactor",
+      "path": "skills/tdd-refactor/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.1.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": "sw:tdd-cycle --phase refactor",
+      "alias": {
+        "from": "/sw:tdd-refactor",
+        "to": "/sw:tdd-cycle --phase refactor",
+        "migrationWarning": "sw:tdd-refactor is deprecated. Use sw:tdd-cycle --phase refactor instead."
+      },
+      "migrationWarning": "sw:tdd-refactor is deprecated. Use sw:tdd-cycle --phase refactor instead. Scheduled for removal in v1.3.0."
+    },
+    {
+      "name": "sw:github-issue-standard",
+      "path": "skills/github-issue-standard/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.1.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": ".specweave/docs/internal/specs/github-issue-standard.md",
+      "migrationWarning": "sw:github-issue-standard was a documentation standard, not an executable skill. Content moved to .specweave/docs/internal/specs/github-issue-standard.md. For GitHub sync, use sw-github:push. Scheduled for removal in v1.3.0."
+    },
+    {
+      "name": "sw/github-multi-project",
+      "path": "skills/github-multi-project/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.2.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": "sw/multi-project --tool github",
+      "alias": {
+        "from": "sw/github-multi-project",
+        "to": "sw/multi-project --tool github",
+        "migrationWarning": "sw/github-multi-project is deprecated. Use sw/multi-project --tool github instead."
+      },
+      "migrationWarning": "sw/github-multi-project is deprecated. Use sw/multi-project --tool github instead. Scheduled for removal in v1.3.0."
+    },
+    {
+      "name": "sw/ado-multi-project",
+      "path": "skills/ado-multi-project/SKILL.md",
+      "deprecated": true,
+      "deprecatedIn": "1.2.0",
+      "removalScheduledIn": "1.3.0",
+      "replacement": "sw/multi-project --tool ado",
+      "alias": {
+        "from": "sw/ado-multi-project",
+        "to": "sw/multi-project --tool ado",
+        "migrationWarning": "sw/ado-multi-project is deprecated. Use sw/multi-project --tool ado instead."
+      },
+      "migrationWarning": "sw/ado-multi-project is deprecated. Use sw/multi-project --tool ado instead. Scheduled for removal in v1.3.0."
+    }
+  ]
+}

package/plugins/specweave/skills/ado-multi-project/SKILL.md

@@ -1,11 +1,19 @@
 ---
-description: Organize specs and tasks across multiple Azure DevOps projects with intelligent content-based mapping. Use when working with project-per-team, area-path-based, or team-based ADO architectures. Handles cross-project coordination and folder structure organization.
+description: "[DEPRECATED] Use `sw:multi-project --tool ado` instead. Organizes specs and tasks across multiple Azure DevOps projects. This skill will be removed in SpecWeave v1.3.0."
 user-invokable: false
 allowed-tools: Read, Write, Edit, Glob
 ---
 
 # Azure DevOps Multi-Project Skill
 
+## Migration
+
+> Deprecated. Use: `sw:multi-project --tool ado`
+
+This skill has been consolidated into the unified `sw:multi-project` skill. Replace any invocation of `sw:ado-multi-project` with `sw:multi-project --tool ado`. The flag-based skill supports GitHub, Azure DevOps, and Jira under a single interface. See `plugins/specweave/skills/multi-project/SKILL.md`.
+
+Scheduled for removal in SpecWeave v1.3.0.
+
 **Purpose**: Organize specs and increments across multiple Azure DevOps projects with intelligent mapping and folder organization.
 
 ## What This Skill Does

package/plugins/specweave/skills/ado-sync/SKILL.md

@@ -1,6 +1,21 @@
 ---
-description: Help and guidance for Azure DevOps synchronization with SpecWeave increments. Use when asking how to set up ADO sync, configure credentials, or troubleshoot integration issues. For actual syncing, use sw-ado:sync command.
+description: "[DEPRECATED] Help and guidance for Azure DevOps synchronization with SpecWeave increments. Use when asking how to set up ADO sync, configure credentials, or troubleshoot integration issues. For actual syncing, use sw-ado:push or sw-ado:pull command."
 user-invokable: false
+deprecated: true
+---
+
+> ⚠️ DEPRECATED: Use `sw-ado:push` / `sw-ado:pull` instead. This skill will be removed in v1.3.0.
+
+## Migration
+
+This skill has been deprecated as part of the Opus 4.7 framework alignment (increment 0669).
+
+- **Use instead**: `sw-ado:push` (content SpecWeave→ADO) and `sw-ado:pull` (status ADO→SpecWeave)
+- **Removal**: Scheduled for v1.3.0 (2 minor releases after v1.1.0)
+- **Why**: Consolidated sync logic moved to the `sw-ado:*` command family.
+
+For the migration policy, see `.specweave/docs/internal/specs/skill-deprecation-policy.md`.
+
 ---
 
 # Azure DevOps Sync Skill

package/plugins/specweave/skills/analytics/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: sw/analytics
+description: "Analytics and metrics for SpecWeave usage — token consumption, cache efficiency, agent spawn counts."
+allowed-tools: Read, Bash
+---
+
+## Tool-Use Rationale
+
+- **Read**: Load metrics snapshots, increment history, and config to compute analytics.
+- **Bash**: Run `specweave metrics` CLI commands to gather live telemetry data.
+
+## Usage
+
+```
+sw:analytics [--cache-stats] [--spawn-count] [--token-usage]
+```
+
+## --cache-stats
+
+Displays prompt cache hit rates per skill for the current session.
+
+**Output format**:
+```
+Cache Statistics (current session)
+───────────────────────────────────
+sw/grill         hit rate: 78% (1,240 tokens from cache)
+sw/judge-llm     hit rate: 65% (980 tokens from cache)
+sw/code-reviewer hit rate: 82% (1,560 tokens from cache)
+───────────────────────────────────
+Overall:         hit rate: 75%
+```
+
+**Requirements**:
+- Cache must be enabled (`cache.staticContextFiles` non-empty in config)
+- Minimum 2 invocations per skill for meaningful hit rate
+
+**Enable persistent metrics**: Set `analytics.cacheMetrics.enabled: true` in `.specweave/config.json`.
+
+## --spawn-count
+
+Reports agent spawn counts per team session. Use to verify that Opus 4.7 fan-out reduction is working (target: ≤ 50% of pre-1.1.0 baseline).
+
+## --token-usage
+
+Reports total token consumption per skill across the session.

package/plugins/specweave/skills/architect/SKILL.md

@@ -6,26 +6,12 @@ model: opus
 
 # Architect
 
-## STEP 0: Register Skill Chain Marker (MANDATORY - DO THIS FIRST)
+## Tool-Use Rationale
 
-**Before any other work**, register your invocation so the skill-chain-enforcement-guard allows plan.md writes.
-
-Extract the increment ID from your args (e.g., "Design architecture for increment 0323-feature-name ...").
-Then write the marker file:
-
-```bash
-mkdir -p .specweave/state
-STATE_FILE=".specweave/state/skill-chain-XXXX-name.json"
-if [ -f "$STATE_FILE" ]; then
-  jq '.architect_invoked=true | .architect_invoked_at="'$(date -Iseconds)'"' "$STATE_FILE" > "${STATE_FILE}.tmp" && mv "${STATE_FILE}.tmp" "$STATE_FILE"
-else
-  echo '{"architect_invoked":true,"architect_invoked_at":"'$(date -Iseconds)'"}' > "$STATE_FILE"
-fi
-```
-
-Replace `XXXX-name` with the actual increment ID. **This unblocks the guard for plan.md writes.**
-
-**If you skip this step, your Write to plan.md will be BLOCKED by the PreToolUse guard.**
+- **Read**: Load the increment's `spec.md`, existing ADRs under `.specweave/docs/internal/architecture/adr/`, and any living-docs referenced by the spec.
+- **Glob**: Discover repo layout, existing services, and interface files that inform component boundaries.
+- **Grep**: Locate existing types, APIs, and data models so the plan builds on reality instead of reinventing.
+- **Write**: Produce `plan.md` and new ADR files where design decisions warrant a record.
 
 ## Project Overrides
 

package/plugins/specweave/skills/auto/SKILL.md

@@ -28,7 +28,7 @@ sw:auto [INCREMENT_IDS...] [OPTIONS]
 | Option | Description | Default |
 |--------|-------------|---------|
 | `--max-turns N` | Max hook invocations before hard stop | 20 |
-| `--simple` | Minimal context mode | false |
+| `--simple-compat` | **Deprecated**. Equivalent to the legacy `--simple` flag. Emits a deprecation warning and will be removed in v1.3.0. | false |
 | `--dry-run` | Preview without starting | false |
 | `--all-backlog` | Process all backlog items | false |
 | `--skip-gates G1,G2` | Pre-approve specific gates | None |
@@ -43,17 +43,48 @@ sw:auto [INCREMENT_IDS...] [OPTIONS]
 | `--cov <n>` | Code coverage threshold (%) | 80 |
 | `--cmd "<command>"` | Custom command must pass | None |
 
-## Simple Mode (`--simple`)
+## Context-Adaptive Execution (default)
 
-When `simple: true` is set in the session marker, reduce context consumption per iteration:
+`sw:auto` no longer exposes `--simple` as a primary execution path. Every session uses context-adaptive execution:
 
-1. **Skip spec re-reads** — Do NOT re-read `spec.md` on each task iteration. Read it once at session start, then rely on `tasks.md` alone for task-by-task execution.
-2. **Minimal task context** — Read only the current task's section from `tasks.md`, not the entire file. Use line offsets if the file is long.
-3. **No sub-skill loading** — Do NOT invoke domain skills (frontend:architect, testing:qa, etc.) during auto execution. Execute tasks directly using code tools.
-4. **Shorter status output** — Skip banners and progress tables between tasks. Just implement, test, mark complete, move on.
-5. **No complexity re-check** — Skip Step 1.5a (team-lead routing check) since the caller already decided the execution mode.
+- On large specs (>40KB), `sw:auto` **automatically reduces context re-reads internally** — no manual `--simple` flag needed. Specs are read once at session start; subsequent iterations rely on `tasks.md` plus diffs.
+- On smaller specs, spec re-reads stay enabled for maximum coherence.
+- Sub-skill loading is decided per-task based on domain signals, not by a global flag.
 
-**When to use**: Primarily for sub-agents in team-lead mode where the team-lead has already loaded specs, assigned tasks, and the agent just needs to execute. Also useful for simple increments with <10 tasks.
+## Legacy `--simple-compat` (deprecated)
+
+The legacy `--simple` minimal-context mode is retained for one minor release as `--simple-compat`.
+
+- Emits a deprecation warning on invocation.
+- Will be removed in v1.3.0.
+- Equivalent behaviour (for compatibility with external runbooks):
+  1. Skip spec re-reads — read `spec.md` once at session start, rely on `tasks.md` alone afterward.
+  2. Minimal task context — read only the current task's section from `tasks.md`.
+  3. No sub-skill loading — execute tasks directly using code tools.
+  4. Shorter status output — skip banners and progress tables between tasks.
+  5. No complexity re-check — skip Step 1.5a (team-lead routing check).
+
+New callers should rely on the context-adaptive default above instead.
+
+## Tool-Use Rationale
+
+- **Read**: Load `.specweave/config.json`, `metadata.json`, `spec.md`, and `tasks.md` to drive the auto loop.
+- **Write/Edit**: Update `auto-mode.json` session marker and flip task/AC status as work completes.
+- **Glob**: Locate active/planned increments and test files during gate evaluation.
+- **Bash**: Run the configured quality gates (tests, build, lint, types, custom commands).
+
+## Native Auto Mode
+
+Claude Code ships with a built-in auto mode, toggled with **Shift+Tab**. That native mode runs the agent autonomously without any SpecWeave-specific orchestration.
+
+**When to use `sw:auto` vs native auto**:
+
+- Use **`sw:auto`** when you need increment-aware gates: spec validation, AC tracking, rubric evaluation, task-level test enforcement, or external sync to GitHub/Jira/ADO.
+- Use **Claude Code native auto (Shift+Tab)** for general-purpose autonomous execution without increment tracking — e.g. quick refactors, research loops, exploration.
+
+**One-time advisory**: When invoked in Claude Code, `sw:auto` prints a one-time advisory pointing to Shift+Tab for users who may not need increment gates. The advisory is suppressed after the first acknowledgement.
+
+**Opt-out for power users**: Pass `--force-sw-auto` to suppress the advisory permanently.
 
 ## Core Loop
 
@@ -103,7 +134,7 @@ If `pr-based`: create/checkout feature branch before starting work (same logic a
 ```
 
 Map flags to session marker fields:
-- `--simple` -> set `"simple": true`
+- `--simple-compat` -> set `"simple": true` (deprecated — emits warning, removed in v1.3.0)
 - `--tests` -> `{ "type": "tests_pass", "required": true }`
 - `--build` -> `{ "type": "build_succeeds", "required": true }`
 - `--e2e` -> `{ "type": "tests_pass", "description": "E2E tests", "required": true }`

package/plugins/specweave/skills/brainstorm/SKILL.md

@@ -141,7 +141,7 @@ Override defaults: `sw:brainstorm "topic" --criteria "perf,cost,complexity,risk"
 
 ## Phase 1: Frame
 
-**Token budget: 400 tokens max.**
+**Token budget: ~1200 tokens max** (raised 3× in SpecWeave 1.1.0; override via `quality.tokenBudgets.frame`).
 
 ### 1a. Restate the Problem
 
@@ -181,7 +181,7 @@ Update state: `"phase": "evaluate"`.
 
 ## Phase 2: Diverge
 
-**Token budget: 600 tokens per approach (max 3600 for 6 approaches).**
+**Token budget: ~1800 tokens per approach** (max ~10800 for 6 approaches; raised 3× in SpecWeave 1.1.0; override via `quality.tokenBudgets.diverge`).
 
 ### 2a. Lens Selection
 
@@ -247,7 +247,7 @@ Update state: `"phase": "evaluate"`, populate `"approaches"` array.
 
 ## Phase 3: Evaluate
 
-**Token budget: 500 tokens max.**
+**Token budget: ~1500 tokens max** (raised 3× in SpecWeave 1.1.0; override via `quality.tokenBudgets.evaluate`).
 
 ### 3a. Comparison Matrix
 
@@ -295,7 +295,7 @@ Update state: `"selectedApproach": { ... }`.
 
 ## Phase 4: Deepen (Deep Mode Only)
 
-**Token budget: 500 tokens max.**
+**Token budget: ~1500 tokens max** (raised 3× in SpecWeave 1.1.0; override via `quality.tokenBudgets.deepen`).
 
 This phase only runs when `--depth deep`.
 
@@ -335,7 +335,7 @@ Update state: `"phase": "output"`.
 
 ## Phase 5: Output
 
-**Token budget: 400 tokens max.**
+**Token budget: ~1200 tokens max** (raised 3× in SpecWeave 1.1.0; override via `quality.tokenBudgets.output`).
 
 ### 5a. Save Brainstorm Document
 
@@ -507,19 +507,19 @@ Save to `.specweave/docs/brainstorms/YYYY-MM-DD-{topic-slug}.md`. Structure:
 
 ## Token Budgets (Guidelines)
 
-These are targets, not hard limits. Prefer conciseness, but expand when the problem demands it.
+These are targets, not hard limits. Prefer conciseness, but expand when the problem demands it. Override via `quality.tokenBudgets` in `.specweave/config.json`. Budgets were raised 3× in SpecWeave 1.1.0 to take advantage of Opus 4.7's long-horizon coherence — smaller caps forced premature summarization and missed approach trade-offs.
 
 | Phase | Target | Hard Max | Notes |
 |-------|--------|----------|-------|
-| Frame | ~400 tokens | 800 | Problem + 5W1H + questions |
-| Diverge (per approach) | ~600 tokens | 1000 | Name + summary + steps + trade-offs |
-| Diverge (total) | ~3600 tokens | 6000 | 6 approaches max |
-| Evaluate | ~500 tokens | 800 | Matrix + recommendation |
-| Deepen | ~500 tokens | 1000 | Ladder + analogies + assumptions + pre-mortem |
-| Output | ~400 tokens | 600 | Summary + handoff |
-| **Quick total** | ~1300 | ~2600 | Frame + 3 approaches + Evaluate |
-| **Standard total** | ~3500 | ~5200 | Frame + Diverge + Evaluate + Output |
-| **Deep total** | ~5400 | ~9200 | All 5 phases |
+| Frame | ~1200 tokens | 2400 | Problem + 5W1H + questions |
+| Diverge (per approach) | ~1800 tokens | 3000 | Name + summary + steps + trade-offs |
+| Diverge (total) | ~10800 tokens | 18000 | 6 approaches max |
+| Evaluate | ~1500 tokens | 2400 | Matrix + recommendation |
+| Deepen | ~1500 tokens | 3000 | Ladder + analogies + assumptions + pre-mortem |
+| Output | ~1200 tokens | 1800 | Summary + handoff |
+| **Quick total** | ~3900 | ~7800 | Frame + 3 approaches + Evaluate |
+| **Standard total** | ~10500 | ~15600 | Frame + Diverge + Evaluate + Output |
+| **Deep total** | ~16200 | ~27600 | All 5 phases |
 
 **When to exceed targets**: Complex problems with many stakeholders, deeply technical domains requiring precise terminology, or when the user explicitly asks for more detail.
 

package/plugins/specweave/skills/close-all/SKILL.md

@@ -1,80 +1,50 @@
 ---
 name: close-all
-description: Batch-close all increments at 100% completion. Discovers "ready for review" and "active" increments with all tasks done, then closes each via sw-closer subagent (Claude Code) or sw:done (non-cloud). Use when saying "close all", "close stuck increments", "batch close".
+description: Batch-close all complete increments by delegating each one to `sw:done`. Discovers active/ready-for-review increments with zero pending tasks, then iterates and calls `sw:done` per increment. Use when saying "close all", "close stuck increments", or "batch close".
 argument-hint: "[--dry-run]"
 ---
 
 # Batch Close All Complete Increments
 
-Close all increments that are at 100% task completion but have not been formally closed via `sw:done`.
+Closes all active increments that have reached 100% task completion by delegating each one to `sw:done`. This skill is a thin batch-discovery loop; all actual closure logic (gates, reports, sync) lives in `sw:done`.
 
 ## Step 1: Discover Closeable Increments
 
 ```bash
-echo "=== Scanning for closeable increments ==="
-for meta in $(find .specweave/increments -maxdepth 2 -name "metadata.json" 2>/dev/null | sort); do
+for meta in $(find .specweave/increments -maxdepth 2 -name "metadata.json" | sort); do
   st=$(jq -r '.status' "$meta" 2>/dev/null)
-  # Only consider active/in-progress/ready_for_review
   [ "$st" != "active" ] && [ "$st" != "in-progress" ] && [ "$st" != "ready_for_review" ] && continue
-  d=$(dirname "$meta")
-  id=$(basename "$d")
-  # Check for pending tasks
-  tasks_file="$d/tasks.md"
-  [ ! -f "$tasks_file" ] && continue
-  pending=$(grep -c '\[ \]' "$tasks_file" 2>/dev/null || echo "0")
-  total=$(grep -c '\[x\]' "$tasks_file" 2>/dev/null || echo "0")
-  if [ "$pending" -eq 0 ] && [ "$total" -gt 0 ]; then
-    echo "CLOSEABLE: $id (status: $st, tasks: $total/$total)"
+  d=$(dirname "$meta"); id=$(basename "$d"); tasks="$d/tasks.md"
+  [ ! -f "$tasks" ] && continue
+  pending=$(grep -c '\[ \]' "$tasks" 2>/dev/null || echo 0)
+  done_count=$(grep -c '\[x\]' "$tasks" 2>/dev/null || echo 0)
+  if [ "$pending" -eq 0 ] && [ "$done_count" -gt 0 ]; then
+    echo "CLOSEABLE: $id"
   fi
 done
 ```
 
-If no closeable increments found, report "No increments ready for closure" and stop.
+If no closeable increments are found, report "No increments ready for closure" and stop.
 
-## Step 2: Check for --dry-run
+## Step 2: Dry-run
 
-If the user passed `--dry-run`, print the list of closeable increments and stop. Do not close anything.
+If the user passed `--dry-run`, print the discovered list and stop without closing anything.
 
-## Step 3: Close Each Increment
+## Step 3: Delegate each to `sw:done`
 
-### Step 3a: Claude Code (Agent tool available — preferred)
-
-For each closeable increment, spawn an `sw-closer` subagent in a fresh context:
-
-```typescript
-Agent({
-  subagent_type: "sw:sw-closer",
-  prompt: "Close increment <ID>. Increment path: .specweave/increments/<ID>/",
-  description: "Close increment <ID>"
-})
-```
-
-**Close sequentially** (one at a time) to respect dependency order and avoid race conditions.
-
-Wait for each sw-closer to return before spawning the next. If a closer fails, log the failure and continue to the next increment.
-
-### Step 3b: Non-cloud fallback (no Agent tool)
-
-For each closeable increment, invoke closure directly:
+Iterate the discovered list sequentially. For each `<ID>`:
 
 ```
-Skill({ skill: "sw:done", args: "<increment-id>" })
+Skill({ skill: "sw:done", args: "<ID>" })
 ```
 
-Non-cloud tools have fresh context per skill invocation, so inline closure works without overflow.
+`sw:done` owns the actual closure workflow: code-review, simplify, grill, judge-llm, PM validation, external sync, and final status transition. Close sequentially to respect dependency order; if `sw:done` fails for an increment, log the failure and continue with the next.
 
 ## Step 4: Summary
 
-Print a summary table of results:
+Print a final summary with CLOSED / FAILED counts per increment. Failures are not retried here — the user re-runs `sw:done <ID>` individually once blockers are resolved.
 
-```
-BATCH CLOSURE SUMMARY
-═══════════════════════════════════════════
-ID                              Status    Reason
-──────────────────────────────  ────────  ──────
-0593-fix-refresh-plugins        CLOSED    All gates passed
-0589-cli-complete-improvements  FAILED    Gate 1: grill BLOCKER found
-0587-fix-github-sync-dedup      CLOSED    All gates passed
-═══════════════════════════════════════════
-Closed: 2 | Failed: 1 | Total: 3
-```
+## Notes
+
+- All gate logic lives in `sw:done`. This skill MUST NOT duplicate closure behaviour.
+- Parallel closure is intentionally not supported — race conditions on shared living docs are a real hazard.