@windyroad/itil 2.1.3 → 2.1.4

package/.claude-plugin/plugin.json

@@ -497,5 +497,5 @@
     }
   },
   "name": "wr-itil",
-  "version": "2.1.3"
+  "version": "2.1.4"
 }

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "wr-itil",
-  "version": "2.1.3",
+  "version": "2.1.4",
   "description": "ITIL problem-management workflows for AI coding agents",
   "author": {
     "name": "Windy Road Technology",

package/agents/hang-off-check.md

@@ -1,13 +1,13 @@
 ---
 name: hang-off-check
-description: Capture-time inflow-discipline arbiter for problem tickets. Given a
+description: "Capture-time inflow-discipline arbiter for problem tickets. Given a"
   new capture's description plus a filtered candidate ticket list, returns a
   structured verdict — HANG_OFF P<NNN> when the new scope belongs as an
   Investigation Tasks expansion / Phase N section on an existing parent ticket,
   or PROCEED_NEW when no candidate absorbs the new scope. Spawned fresh from
   inside /wr-itil:capture-problem and /wr-itil:manage-problem Step 2 to avoid
-  the calling agent's session-context bias. Read-only. Codified as the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule's
-  5th invocation pattern under the "`/wr-itil:review-problems` has no path to close tickets that are no longer relevant (evidence-based, NOT age-based) — structural outflow gap drives monotonic backlog growth" problem amendment.
+  the calling agent's session-context bias. Read-only. Codified as ADR-032's
+  5th invocation pattern under the P346 amendment.
 tools:
   - Read
   - Glob

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/itil",
-  "version": "2.1.3",
+  "version": "2.1.4",
   "description": "ITIL-aligned IT service management for Claude Code and Codex",
   "bin": {
     "windyroad-itil": "./bin/install.mjs"

package/skills/capture-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:capture-problem
-description: Lightweight problem-capture skill for aside-invocation during foreground work — minimal duplicate-check, skeleton ticket file, single commit per capture (covers new ticket + inline README refresh per the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem per the "capture-problem → manage-problem same-session halts at Step 0 reconcile (HALT_ROUTE_RECONCILE on deferred-refresh seam)" problem Option 2 amendment 2026-06-05). Defers full duplicate analysis to /wr-itil:review-problems. Use this when the user (or agent mid-iter) wants to capture an observation quickly without disrupting current task flow. For full-intake new-problem creation, use /wr-itil:manage-problem.
+description: "Lightweight problem-capture skill for aside-invocation during foreground work — minimal duplicate-check, skeleton ticket file, single commit per capture (covers new ticket + inline README refresh per the \"Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation\" problem per the \"capture-problem → manage-problem same-session halts at Step 0 reconcile (HALT_ROUTE_RECONCILE on deferred-refresh seam)\" problem Option 2 amendment 2026-06-05). Defers full duplicate analysis to /wr-itil:review-problems. Use this when the user (or agent mid-iter) wants to capture an observation quickly without disrupting current task flow. For full-intake new-problem creation, use /wr-itil:manage-problem."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion
 ---
 

package/skills/capture-rfc/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:capture-rfc
-description: Draw a problem-traced RFC release row on a story map and attach at least one delivery story. Uses the existing delivery-planning vehicle instead of creating an RFC document.
+description: "Draw a problem-traced RFC release row on a story map and attach at least one delivery story. Uses the existing delivery-planning vehicle instead of creating an RFC document."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Skill, AskUserQuestion
 ---
 

package/skills/capture-story/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:capture-story
-description: Lightweight story-capture skill for aside-invocation during foreground work — mandatory leading problem-trace AND JTBD-trace per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule I6 + I9 invariants, mandatory `--story-map` trace (I8 enforced AT CAPTURE per the "Story-map membership and story-content completeness are enforced at capture" architecture rule, refuse-and-route if absent) + optional `--rfc` (I7 at accepted) + real user-value + >=1 acceptance criterion at capture (I10 content subset / the "Story-map membership and story-content completeness are enforced at capture" architecture rule), skeleton story file at `docs/stories/draft/STORY-NNN-<slug>.md`, single commit per capture, no inline README refresh. Defers full INVEST shape + acceptance transition to /wr-itil:manage-story. Use when the user (or agent) wants to capture a story quickly with clear problem + JTBD anchoring. For full lifecycle management, use /wr-itil:manage-story.
+description: "Lightweight story-capture skill for aside-invocation during foreground work — mandatory leading problem-trace AND JTBD-trace per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule I6 + I9 invariants, mandatory `--story-map` trace (I8 enforced AT CAPTURE per the \"Story-map membership and story-content completeness are enforced at capture\" architecture rule, refuse-and-route if absent) + optional `--rfc` (I7 at accepted) + real user-value + >=1 acceptance criterion at capture (I10 content subset / the \"Story-map membership and story-content completeness are enforced at capture\" architecture rule), skeleton story file at `docs/stories/draft/STORY-NNN-<slug>.md`, single commit per capture, no inline README refresh. Defers full INVEST shape + acceptance transition to /wr-itil:manage-story. Use when the user (or agent) wants to capture a story quickly with clear problem + JTBD anchoring. For full lifecycle management, use /wr-itil:manage-story."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills/capture-story-map/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:capture-story-map
-description: Lightweight story-map-capture skill for aside-invocation during foreground work — mandatory leading problem-trace AND JTBD-trace per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule I3 + I4 invariants, skeleton HTML file at `docs/story-maps/draft/STORY-MAP-NNN-<slug>.html` per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule § Phase 2 encoding amendment 2026-05-12, single commit per capture, no inline README refresh. Defers full backbone/ribs/slices authoring + lifecycle transitions to /wr-itil:manage-story-map. Use when the user (or agent) wants to capture a new story-map quickly with clear problem + JTBD anchoring.
+description: "Lightweight story-map-capture skill for aside-invocation during foreground work — mandatory leading problem-trace AND JTBD-trace per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule I3 + I4 invariants, skeleton HTML file at `docs/story-maps/draft/STORY-MAP-NNN-<slug>.html` per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule § Phase 2 encoding amendment 2026-05-12, single commit per capture, no inline README refresh. Defers full backbone/ribs/slices authoring + lifecycle transitions to /wr-itil:manage-story-map. Use when the user (or agent) wants to capture a new story-map quickly with clear problem + JTBD anchoring."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills/check-upstream-responses/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:check-upstream-responses
-description: Poll upstream issues and pull requests we've filed via `/wr-itil:report-upstream` and surface new comments or reviews, state changes, or label changes since last check. Reads `## Reported Upstream` back-link sections in local problem tickets, queries GitHub read-only, diffs against `docs/problems/.outbound-responses-cache.json`, and appends an audit-log entry to `docs/audits/outbound-responses-log.md`. Outbound symmetric counterpart to the "Inbound upstream-report discovery + assessment pipeline (peer of )" architecture rule's inbound discovery pipeline (the "No process for issue reporters to check for responses — symmetric gap to inbound discovery" problem Phase 1).
+description: "Poll upstream issues and pull requests we've filed via `/wr-itil:report-upstream` and surface new comments or reviews, state changes, or label changes since last check. Reads `## Reported Upstream` back-link sections in local problem tickets, queries GitHub read-only, diffs against `docs/problems/.outbound-responses-cache.json`, and appends an audit-log entry to `docs/audits/outbound-responses-log.md`. Outbound symmetric counterpart to the \"Inbound upstream-report discovery + assessment pipeline (peer of )\" architecture rule's inbound discovery pipeline (the \"No process for issue reporters to check for responses — symmetric gap to inbound discovery\" problem Phase 1)."
 allowed-tools: Read, Edit, Write, Bash, Glob, Grep
 ---
 

package/skills/close-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:close-incident
-description: Close a restored incident — gated on the Linked Problem reaching Known Error, Verifying, or Closed (or a ## No Problem justification). Renames .restored.md to .closed.md.
+description: "Close a restored incident — gated on the Linked Problem reaching Known Error, Verifying, or Closed (or a ## No Problem justification). Renames .restored.md to .closed.md."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/skills/link-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:link-incident
-description: Link an incident to an existing problem — writes or updates the ## Linked Problem section on the incident file with the problem's ID, title, and current status.
+description: "Link an incident to an existing problem — writes or updates the ## Linked Problem section on the incident file with the problem's ID, title, and current status."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/skills/list-incidents/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:list-incidents
-description: List active incidents from docs/incidents/ sorted by severity. Read-only display of the incident backlog — no edits, no interaction. Shown as a markdown table with ID, title, severity, and status columns.
+description: "List active incidents from docs/incidents/ sorted by severity. Read-only display of the incident backlog — no edits, no interaction. Shown as a markdown table with ID, title, severity, and status columns."
 allowed-tools: Read, Bash, Grep, Glob
 ---
 

package/skills/list-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:list-problems
-description: List open and known-error problem tickets from docs/problems/ sorted by WSJF priority. Read-only display of the current backlog — no edits, no interaction. Shown as a markdown table with ID, title, severity, status, and effort columns.
+description: "List open and known-error problem tickets from docs/problems/ sorted by WSJF priority. Read-only display of the current backlog — no edits, no interaction. Shown as a markdown table with ID, title, severity, status, and effort columns."
 allowed-tools: Read, Bash, Grep, Glob
 ---
 

package/skills/list-stories/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:list-stories
-description: List INVEST-shaped story tickets from docs/stories/ as a markdown table. Read-only display — no edits, no interaction. Optional `--rfc RFC-<NNN>` filter to surface a specific RFC's ordered story list per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Phase 2.
+description: "List INVEST-shaped story tickets from docs/stories/ as a markdown table. Read-only display — no edits, no interaction. Optional `--rfc RFC-<NNN>` filter to surface a specific RFC's ordered story list per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule Phase 2."
 allowed-tools: Read, Bash, Grep, Glob
 ---
 

package/skills/list-story-maps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:list-story-maps
-description: List story-map artefacts from docs/story-maps/ as a markdown table. Read-only display — no edits, no interaction. Renders <meta> block data (problems / rfcs / jtbd / status) from each HTML map per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule § Phase 2 encoding amendment 2026-05-12.
+description: "List story-map artefacts from docs/story-maps/ as a markdown table. Read-only display — no edits, no interaction. Renders <meta> block data (problems / rfcs / jtbd / status) from each HTML map per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule § Phase 2 encoding amendment 2026-05-12."
 allowed-tools: Read, Bash, Grep, Glob
 ---
 

package/skills/manage-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:manage-incident
-description: Declare, triage, mitigate, and close an incident using an evidence-first workflow. Restores service first, then hands off to manage-problem for root-cause work.
+description: "Declare, triage, mitigate, and close an incident using an evidence-first workflow. Restores service first, then hands off to manage-problem for root-cause work."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
 deprecated-arguments: true
 ---

package/skills/manage-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:manage-problem
-description: Create, update, or transition a problem ticket using an ITIL-aligned problem management workflow with WSJF prioritisation. Supports creating new problems, updating root cause analysis, transitioning status, and closing problems.
+description: "Create, update, or transition a problem ticket using an ITIL-aligned problem management workflow with WSJF prioritisation. Supports creating new problems, updating root cause analysis, transitioning status, and closing problems."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
 deprecated-arguments: true
 ---

package/skills/manage-rfc/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:manage-rfc
-description: Heavyweight RFC intake + lifecycle management following the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Problem-RFC-Story framework. Creates new RFCs (delegates to /wr-itil:capture-rfc for the lightweight path), updates existing RFCs, transitions through proposed → accepted → in-progress → verifying → closed lifecycle, runs WSJF re-rank reviews, and refreshes docs/rfcs/README.md per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem / the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem contract pattern.
+description: "Heavyweight RFC intake + lifecycle management following the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule Problem-RFC-Story framework. Creates new RFCs (delegates to /wr-itil:capture-rfc for the lightweight path), updates existing RFCs, transitions through proposed → accepted → in-progress → verifying → closed lifecycle, runs WSJF re-rank reviews, and refreshes docs/rfcs/README.md per the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem / the \"Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation\" problem contract pattern."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task
 ---
 

package/skills/manage-story/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:manage-story
-description: Heavyweight story intake + lifecycle management following the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Phase 2. Creates and updates story tickets, transitions through draft → accepted → in-progress → done → archived lifecycle, enforces I7 + I8 trace-gate at the accepted transition, runs INVEST checks per I10 at acceptance, auto-detects accepted→in-progress on the first implementing commit and in-progress→done on all-criteria-ticked + linked RFC closes (per the "A story cannot be implemented while in draft — implementation requires accepted" architecture rule a draft story is NEVER implementable — draft→in-progress is removed; the itil-no-implement-draft-gate blocks implementing a draft story), and refreshes docs/stories/README.md per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem / the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem contract pattern. Companion to /wr-itil:capture-story (lightweight aside surface).
+description: "Heavyweight story intake + lifecycle management following the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule Phase 2. Creates and updates story tickets, transitions through draft → accepted → in-progress → done → archived lifecycle, enforces I7 + I8 trace-gate at the accepted transition, runs INVEST checks per I10 at acceptance, auto-detects accepted→in-progress on the first implementing commit and in-progress→done on all-criteria-ticked + linked RFC closes (per the \"A story cannot be implemented while in draft — implementation requires accepted\" architecture rule a draft story is NEVER implementable — draft→in-progress is removed; the itil-no-implement-draft-gate blocks implementing a draft story), and refreshes docs/stories/README.md per the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem / the \"Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation\" problem contract pattern. Companion to /wr-itil:capture-story (lightweight aside surface)."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills/manage-story-map/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:manage-story-map
-description: Heavyweight story-map intake + lifecycle management following the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Phase 2. Authors backbone × ribs × slices structure on draft maps, transitions through draft → accepted → in-progress → completed → archived, re-validates I3 + I4 invariants at every transition, and refreshes docs/story-maps/README.md per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem / the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem contract pattern. Companion to /wr-itil:capture-story-map (lightweight aside surface).
+description: "Heavyweight story-map intake + lifecycle management following the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule Phase 2. Authors backbone × ribs × slices structure on draft maps, transitions through draft → accepted → in-progress → completed → archived, re-validates I3 + I4 invariants at every transition, and refreshes docs/story-maps/README.md per the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem / the \"Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation\" problem contract pattern. Companion to /wr-itil:capture-story-map (lightweight aside surface)."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills/mitigate-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:mitigate-incident
-description: Record a mitigation attempt against an incident — transitions an investigating incident to mitigating on the first attempt, appends subsequent attempts to the Mitigation attempts timeline. Evidence-first gate enforced per the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule.
+description: "Record a mitigation attempt against an incident — transitions an investigating incident to mitigating on the first attempt, appends subsequent attempts to the Mitigation attempts timeline. Evidence-first gate enforced per the \"Add `manage-incident` Skill to `wr-itil` Plugin\" architecture rule."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
 ---
 

package/skills/reconcile-readme/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:reconcile-readme
-description: Detect and correct drift between docs/problems/README.md and the on-disk ticket inventory. Wraps the diagnose-only `packages/itil/scripts/reconcile-readme.sh` script with an agent-applied-edits pattern that preserves narrative content (the "Last reviewed" prose paragraph and Closed-section closure-via free text). Use when README WSJF Rankings, Verification Queue, or Closed sections drift from filesystem state — typically detected by manage-problem Step 0 preflight or work-problems Step 0 preflight.
+description: "Detect and correct drift between docs/problems/README.md and the on-disk ticket inventory. Wraps the diagnose-only `packages/itil/scripts/reconcile-readme.sh` script with an agent-applied-edits pattern that preserves narrative content (the \"Last reviewed\" prose paragraph and Closed-section closure-via free text). Use when README WSJF Rankings, Verification Queue, or Closed sections drift from filesystem state — typically detected by manage-problem Step 0 preflight or work-problems Step 0 preflight."
 allowed-tools: Read, Edit, Write, Bash, Grep, Glob
 ---
 

package/skills/reconcile-stories/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:reconcile-stories
-description: Detect and correct drift between docs/stories/README.md and the on-disk story inventory. Wraps the diagnose-only packages/itil/scripts/reconcile-stories.sh script with an agent-applied-edits pattern that preserves narrative content (the "Last reviewed" prose paragraph). Use when docs/stories/README.md Story Rankings or Done sections drift from filesystem state — typically detected by manage-story Step 0 preflight or work-problems preflight on RFC iters with story-tier traces.
+description: "Detect and correct drift between docs/stories/README.md and the on-disk story inventory. Wraps the diagnose-only packages/itil/scripts/reconcile-stories.sh script with an agent-applied-edits pattern that preserves narrative content (the \"Last reviewed\" prose paragraph). Use when docs/stories/README.md Story Rankings or Done sections drift from filesystem state — typically detected by manage-story Step 0 preflight or work-problems preflight on RFC iters with story-tier traces."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills/reconcile-story-maps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:reconcile-story-maps
-description: Detect and correct drift between docs/story-maps/README.md and the on-disk story-map HTML inventory. Wraps the diagnose-only packages/itil/scripts/reconcile-story-maps.sh script with an agent-applied-edits pattern preserving narrative content.
+description: "Detect and correct drift between docs/story-maps/README.md and the on-disk story-map HTML inventory. Wraps the diagnose-only packages/itil/scripts/reconcile-story-maps.sh script with an agent-applied-edits pattern preserving narrative content."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills/report-upstream/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:report-upstream
-description: Report a local problem ticket as a structured issue against an upstream repository, with bidirectional cross-references and SECURITY.md-aware routing for security-classified tickets. Implements the contract in the "Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`" architecture rule, with the "Report-upstream classifier is problem-first — supersedes Decision Outcome Steps 3 + 5" architecture rule governing problem-first classifier + default body shape.
+description: "Report a local problem ticket as a structured issue against an upstream repository, with bidirectional cross-references and SECURITY.md-aware routing for security-classified tickets. Implements the contract in the \"Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`\" architecture rule, with the \"Report-upstream classifier is problem-first — supersedes Decision Outcome Steps 3 + 5\" architecture rule governing problem-first classifier + default body shape."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill, Agent
 ---
 

package/skills/restore-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:restore-incident
-description: Mark an incident as service-restored — transitions a mitigating incident to restored, appends a Timeline entry, and hands off to /wr-itil:manage-problem for linked-problem creation or update per the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule.
+description: "Mark an incident as service-restored — transitions a mitigating incident to restored, appends a Timeline entry, and hands off to /wr-itil:manage-problem for linked-problem creation or update per the \"Add `manage-incident` Skill to `wr-itil` Plugin\" architecture rule."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
 ---
 

package/skills/review-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:review-problems
-description: Re-assess every open and known-error problem ticket in docs/problems/ — re-read RISK-POLICY.md, re-rate Impact × Likelihood, re-estimate Effort, recalculate WSJF, surface pending verifications, auto-transition Open → Known Error where warranted, and rewrite docs/problems/README.md with the refreshed ranking. Writes to problem files and the README cache; commits the refresh per the "Governance Skills Commit Their Own Completed Work" architecture rule.
+description: "Re-assess every open and known-error problem ticket in docs/problems/ — re-read RISK-POLICY.md, re-rate Impact × Likelihood, re-estimate Effort, recalculate WSJF, surface pending verifications, auto-transition Open → Known Error where warranted, and rewrite docs/problems/README.md with the refreshed ranking. Writes to problem files and the README cache; commits the refresh per the \"Governance Skills Commit Their Own Completed Work\" architecture rule."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
 ---
 

package/skills/scaffold-intake/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:scaffold-intake
-description: Scaffold the four OSS intake surfaces (.github/ISSUE_TEMPLATE/, SECURITY.md, SUPPORT.md, CONTRIBUTING.md) for a downstream project that adopts @windyroad/itil. Idempotent, foreground-synchronous, and respects the "Gate Marker Lifecycle: TTL + Drift, Not Stop-Hook Reset" architecture rule marker semantics. Implements the contract in the "Scaffold downstream OSS intake — skill + layered triggers" architecture rule.
+description: "Scaffold the four OSS intake surfaces (.github/ISSUE_TEMPLATE/, SECURITY.md, SUPPORT.md, CONTRIBUTING.md) for a downstream project that adopts @windyroad/itil. Idempotent, foreground-synchronous, and respects the \"Gate Marker Lifecycle: TTL + Drift, Not Stop-Hook Reset\" architecture rule marker semantics. Implements the contract in the \"Scaffold downstream OSS intake — skill + layered triggers\" architecture rule."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
 

package/skills/transition-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:transition-problem
-description: Advance a problem ticket's lifecycle status — Open → Known Error, Known Error → Verification Pending (verifying), Verification Pending → Closed. Renames the ticket file, updates the Status field, and refreshes docs/problems/README.md in the same commit. Hosts the transition execution inline (pre-flight checks, the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem staging-trap handling, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection, the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem README refresh, the "Governance Skills Commit Their Own Completed Work" architecture rule commit) per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended "Split-skill execution ownership". Use when the user asks to "transition", "close", "mark known-error", or "release" a specific ticket.
+description: "Advance a problem ticket's lifecycle status — Open → Known Error, Known Error → Verification Pending (verifying), Verification Pending → Closed. Renames the ticket file, updates the Status field, and refreshes docs/problems/README.md in the same commit. Hosts the transition execution inline (pre-flight checks, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem staging-trap handling, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh, the \"Governance Skills Commit Their Own Completed Work\" architecture rule commit) per the \"Rename `wr-problem` Plugin to `wr-itil`\" architecture rule amended \"Split-skill execution ownership\". Use when the user asks to \"transition\", \"close\", \"mark known-error\", or \"release\" a specific ticket."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
 ---
 

package/skills/transition-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:transition-problems
-description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem re-stage, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection, the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the "Governance Skills Commit Their Own Completed Work" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
+description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem re-stage, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the \"Governance Skills Commit Their Own Completed Work\" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill, Agent
 ---
 

package/skills/update-upstream/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:update-upstream
-description: Post a lifecycle-update comment to an upstream issue when a local problem ticket transitions. Drafts a transition-specific update (root-cause confirmed / fix released / closed), composes the prose through the external-comms risk gate + voice-tone gate, auto-posts within appetite, queues above-appetite. Reciprocal sibling to /wr-itil:report-upstream — initial-filing vs lifecycle-update split per the "Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`" architecture rule amendment (the "Problem 080: No bidirectional update of upstream-reported problems — local lifecycle transitions never propagate back to the reporter" problem).
+description: "Post a lifecycle-update comment to an upstream issue when a local problem ticket transitions. Drafts a transition-specific update (root-cause confirmed / fix released / closed), composes the prose through the external-comms risk gate + voice-tone gate, auto-posts within appetite, queues above-appetite. Reciprocal sibling to /wr-itil:report-upstream — initial-filing vs lifecycle-update split per the \"Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`\" architecture rule amendment (the \"Problem 080: No bidirectional update of upstream-reported problems — local lifecycle transitions never propagate back to the reporter\" problem)."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill, Agent
 ---
 

package/skills/work-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:work-problem
-description: Pick the highest-WSJF open or known-error problem ticket and work it — investigate, implement, commit, and release per the standard manage-problem workflow. Selection is framework-mediated (WSJF + documented tie-break ladder per the "— Decision-Delegation Contract: when agents act on the framework vs ask the user" architecture rule); singular variant; distinct from /wr-itil:work-problems (plural AFK orchestrator). Use this when the user asks to "work the next problem", "work the top of the queue", or "grind through one ticket".
+description: "Pick the highest-WSJF open or known-error problem ticket and work it — investigate, implement, commit, and release per the standard manage-problem workflow. Selection is framework-mediated (WSJF + documented tie-break ladder per the \"— Decision-Delegation Contract: when agents act on the framework vs ask the user\" architecture rule); singular variant; distinct from /wr-itil:work-problems (plural AFK orchestrator). Use this when the user asks to \"work the next problem\", \"work the top of the queue\", or \"grind through one ticket\"."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill, Agent
 ---
 

package/skills/work-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wr-itil:work-problems
-description: Batch-work ITIL problem tickets while the user is AFK. Loops through the problem backlog by WSJF priority, delegating each problem to wr-itil:manage-problem, and stops when nothing is left to progress. Use this skill whenever the user says things like "work through my problems", "grind problems", "work the backlog", "work problems while I'm away", "process problems AFK", or any request to autonomously work through multiple problem tickets without interactive input. Also trigger when the user asks to "loop" or "batch" problem work, or says they'll be away and wants problems handled.
+description: "Batch-work ITIL problem tickets while the user is AFK. Loops through the problem backlog by WSJF priority, delegating each problem to wr-itil:manage-problem, and stops when nothing is left to progress. Use this skill whenever the user says things like \"work through my problems\", \"grind problems\", \"work the backlog\", \"work problems while I'm away\", \"process problems AFK\", or any request to autonomously work through multiple problem tickets without interactive input. Also trigger when the user asks to \"loop\" or \"batch\" problem work, or says they'll be away and wants problems handled."
 allowed-tools: Agent, Skill, Bash, Glob, Grep, Read
 ---
 

package/skills-codex/capture-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: capture-problem
-description: Lightweight problem-capture skill for aside-invocation during foreground work — minimal duplicate-check, skeleton ticket file, single commit per capture (covers new ticket + inline README refresh per the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem per the "capture-problem → manage-problem same-session halts at Step 0 reconcile (HALT_ROUTE_RECONCILE on deferred-refresh seam)" problem Option 2 amendment 2026-06-05). Defers full duplicate analysis to /wr-itil:review-problems. Use this when the user (or agent mid-iter) wants to capture an observation quickly without disrupting current task flow. For full-intake new-problem creation, use /wr-itil:manage-problem.
+description: "Lightweight problem-capture skill for aside-invocation during foreground work — minimal duplicate-check, skeleton ticket file, single commit per capture (covers new ticket + inline README refresh per the \"Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation\" problem per the \"capture-problem → manage-problem same-session halts at Step 0 reconcile (HALT_ROUTE_RECONCILE on deferred-refresh seam)\" problem Option 2 amendment 2026-06-05). Defers full duplicate analysis to /wr-itil:review-problems. Use this when the user (or agent mid-iter) wants to capture an observation quickly without disrupting current task flow. For full-intake new-problem creation, use /wr-itil:manage-problem."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob, request_user_input
 ---
 

package/skills-codex/capture-rfc/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: capture-rfc
-description: Draw a problem-traced RFC release row on a story map and attach at least one delivery story. Uses the existing delivery-planning vehicle instead of creating an RFC document.
+description: "Draw a problem-traced RFC release row on a story map and attach at least one delivery story. Uses the existing delivery-planning vehicle instead of creating an RFC document."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Skill, request_user_input
 ---
 

package/skills-codex/capture-story/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: capture-story
-description: Lightweight story-capture skill for aside-invocation during foreground work — mandatory leading problem-trace AND JTBD-trace per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule I6 + I9 invariants, mandatory `--story-map` trace (I8 enforced AT CAPTURE per the "Story-map membership and story-content completeness are enforced at capture" architecture rule, refuse-and-route if absent) + optional `--rfc` (I7 at accepted) + real user-value + >=1 acceptance criterion at capture (I10 content subset / the "Story-map membership and story-content completeness are enforced at capture" architecture rule), skeleton story file at `docs/stories/draft/STORY-NNN-<slug>.md`, single commit per capture, no inline README refresh. Defers full INVEST shape + acceptance transition to /wr-itil:manage-story. Use when the user (or agent) wants to capture a story quickly with clear problem + JTBD anchoring. For full lifecycle management, use /wr-itil:manage-story.
+description: "Lightweight story-capture skill for aside-invocation during foreground work — mandatory leading problem-trace AND JTBD-trace per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule I6 + I9 invariants, mandatory `--story-map` trace (I8 enforced AT CAPTURE per the \"Story-map membership and story-content completeness are enforced at capture\" architecture rule, refuse-and-route if absent) + optional `--rfc` (I7 at accepted) + real user-value + >=1 acceptance criterion at capture (I10 content subset / the \"Story-map membership and story-content completeness are enforced at capture\" architecture rule), skeleton story file at `docs/stories/draft/STORY-NNN-<slug>.md`, single commit per capture, no inline README refresh. Defers full INVEST shape + acceptance transition to /wr-itil:manage-story. Use when the user (or agent) wants to capture a story quickly with clear problem + JTBD anchoring. For full lifecycle management, use /wr-itil:manage-story."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills-codex/capture-story-map/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: capture-story-map
-description: Lightweight story-map-capture skill for aside-invocation during foreground work — mandatory leading problem-trace AND JTBD-trace per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule I3 + I4 invariants, skeleton HTML file at `docs/story-maps/draft/STORY-MAP-NNN-<slug>.html` per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule § Phase 2 encoding amendment 2026-05-12, single commit per capture, no inline README refresh. Defers full backbone/ribs/slices authoring + lifecycle transitions to /wr-itil:manage-story-map. Use when the user (or agent) wants to capture a new story-map quickly with clear problem + JTBD anchoring.
+description: "Lightweight story-map-capture skill for aside-invocation during foreground work — mandatory leading problem-trace AND JTBD-trace per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule I3 + I4 invariants, skeleton HTML file at `docs/story-maps/draft/STORY-MAP-NNN-<slug>.html` per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule § Phase 2 encoding amendment 2026-05-12, single commit per capture, no inline README refresh. Defers full backbone/ribs/slices authoring + lifecycle transitions to /wr-itil:manage-story-map. Use when the user (or agent) wants to capture a new story-map quickly with clear problem + JTBD anchoring."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills-codex/check-upstream-responses/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: check-upstream-responses
-description: Poll upstream issues and pull requests we've filed via `/wr-itil:report-upstream` and surface new comments or reviews, state changes, or label changes since last check. Reads `## Reported Upstream` back-link sections in local problem tickets, queries GitHub read-only, diffs against `docs/problems/.outbound-responses-cache.json`, and appends an audit-log entry to `docs/audits/outbound-responses-log.md`. Outbound symmetric counterpart to the "Inbound upstream-report discovery + assessment pipeline (peer of )" architecture rule's inbound discovery pipeline (the "No process for issue reporters to check for responses — symmetric gap to inbound discovery" problem Phase 1).
+description: "Poll upstream issues and pull requests we've filed via `/wr-itil:report-upstream` and surface new comments or reviews, state changes, or label changes since last check. Reads `## Reported Upstream` back-link sections in local problem tickets, queries GitHub read-only, diffs against `docs/problems/.outbound-responses-cache.json`, and appends an audit-log entry to `docs/audits/outbound-responses-log.md`. Outbound symmetric counterpart to the \"Inbound upstream-report discovery + assessment pipeline (peer of )\" architecture rule's inbound discovery pipeline (the \"No process for issue reporters to check for responses — symmetric gap to inbound discovery\" problem Phase 1)."
 allowed-tools: Read, Edit, Write, Bash, Glob, Grep
 ---
 

package/skills-codex/close-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: close-incident
-description: Close a restored incident — gated on the Linked Problem reaching Known Error, Verifying, or Closed (or a ## No Problem justification). Renames .restored.md to .closed.md.
+description: "Close a restored incident — gated on the Linked Problem reaching Known Error, Verifying, or Closed (or a ## No Problem justification). Renames .restored.md to .closed.md."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/skills-codex/link-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: link-incident
-description: Link an incident to an existing problem — writes or updates the ## Linked Problem section on the incident file with the problem's ID, title, and current status.
+description: "Link an incident to an existing problem — writes or updates the ## Linked Problem section on the incident file with the problem's ID, title, and current status."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 

package/skills-codex/list-incidents/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: list-incidents
-description: List active incidents from docs/incidents/ sorted by severity. Read-only display of the incident backlog — no edits, no interaction. Shown as a markdown table with ID, title, severity, and status columns.
+description: "List active incidents from docs/incidents/ sorted by severity. Read-only display of the incident backlog — no edits, no interaction. Shown as a markdown table with ID, title, severity, and status columns."
 allowed-tools: Read, Bash, Grep, Glob
 ---
 

package/skills-codex/list-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: list-problems
-description: List open and known-error problem tickets from docs/problems/ sorted by WSJF priority. Read-only display of the current backlog — no edits, no interaction. Shown as a markdown table with ID, title, severity, status, and effort columns.
+description: "List open and known-error problem tickets from docs/problems/ sorted by WSJF priority. Read-only display of the current backlog — no edits, no interaction. Shown as a markdown table with ID, title, severity, status, and effort columns."
 allowed-tools: Read, Bash, Grep, Glob
 ---
 

package/skills-codex/list-stories/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: list-stories
-description: List INVEST-shaped story tickets from docs/stories/ as a markdown table. Read-only display — no edits, no interaction. Optional `--rfc RFC-<NNN>` filter to surface a specific RFC's ordered story list per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Phase 2.
+description: "List INVEST-shaped story tickets from docs/stories/ as a markdown table. Read-only display — no edits, no interaction. Optional `--rfc RFC-<NNN>` filter to surface a specific RFC's ordered story list per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule Phase 2."
 allowed-tools: Read, Bash, Grep, Glob
 ---
 

package/skills-codex/list-story-maps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: list-story-maps
-description: List story-map artefacts from docs/story-maps/ as a markdown table. Read-only display — no edits, no interaction. Renders <meta> block data (problems / rfcs / jtbd / status) from each HTML map per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule § Phase 2 encoding amendment 2026-05-12.
+description: "List story-map artefacts from docs/story-maps/ as a markdown table. Read-only display — no edits, no interaction. Renders <meta> block data (problems / rfcs / jtbd / status) from each HTML map per the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule § Phase 2 encoding amendment 2026-05-12."
 allowed-tools: Read, Bash, Grep, Glob
 ---
 

package/skills-codex/manage-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: manage-incident
-description: Declare, triage, mitigate, and close an incident using an evidence-first workflow. Restores service first, then hands off to manage-problem for root-cause work.
+description: "Declare, triage, mitigate, and close an incident using an evidence-first workflow. Restores service first, then hands off to manage-problem for root-cause work."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill
 deprecated-arguments: true
 ---

package/skills-codex/manage-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: manage-problem
-description: Create, update, or transition a problem ticket using an ITIL-aligned problem management workflow with WSJF prioritisation. Supports creating new problems, updating root cause analysis, transitioning status, and closing problems.
+description: "Create, update, or transition a problem ticket using an ITIL-aligned problem management workflow with WSJF prioritisation. Supports creating new problems, updating root cause analysis, transitioning status, and closing problems."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill
 deprecated-arguments: true
 ---

package/skills-codex/manage-rfc/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: manage-rfc
-description: Heavyweight RFC intake + lifecycle management following the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Problem-RFC-Story framework. Creates new RFCs (delegates to /wr-itil:capture-rfc for the lightweight path), updates existing RFCs, transitions through proposed → accepted → in-progress → verifying → closed lifecycle, runs WSJF re-rank reviews, and refreshes docs/rfcs/README.md per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem / the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem contract pattern.
+description: "Heavyweight RFC intake + lifecycle management following the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule Problem-RFC-Story framework. Creates new RFCs (delegates to /wr-itil:capture-rfc for the lightweight path), updates existing RFCs, transitions through proposed → accepted → in-progress → verifying → closed lifecycle, runs WSJF re-rank reviews, and refreshes docs/rfcs/README.md per the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem / the \"Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation\" problem contract pattern."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task
 ---
 

package/skills-codex/manage-story/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: manage-story
-description: Heavyweight story intake + lifecycle management following the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Phase 2. Creates and updates story tickets, transitions through draft → accepted → in-progress → done → archived lifecycle, enforces I7 + I8 trace-gate at the accepted transition, runs INVEST checks per I10 at acceptance, auto-detects accepted→in-progress on the first implementing commit and in-progress→done on all-criteria-ticked + linked RFC closes (per the "A story cannot be implemented while in draft — implementation requires accepted" architecture rule a draft story is NEVER implementable — draft→in-progress is removed; the itil-no-implement-draft-gate blocks implementing a draft story), and refreshes docs/stories/README.md per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem / the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem contract pattern. Companion to /wr-itil:capture-story (lightweight aside surface).
+description: "Heavyweight story intake + lifecycle management following the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule Phase 2. Creates and updates story tickets, transitions through draft → accepted → in-progress → done → archived lifecycle, enforces I7 + I8 trace-gate at the accepted transition, runs INVEST checks per I10 at acceptance, auto-detects accepted→in-progress on the first implementing commit and in-progress→done on all-criteria-ticked + linked RFC closes (per the \"A story cannot be implemented while in draft — implementation requires accepted\" architecture rule a draft story is NEVER implementable — draft→in-progress is removed; the itil-no-implement-draft-gate blocks implementing a draft story), and refreshes docs/stories/README.md per the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem / the \"Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation\" problem contract pattern. Companion to /wr-itil:capture-story (lightweight aside surface)."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills-codex/manage-story-map/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: manage-story-map
-description: Heavyweight story-map intake + lifecycle management following the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Phase 2. Authors backbone × ribs × slices structure on draft maps, transitions through draft → accepted → in-progress → completed → archived, re-validates I3 + I4 invariants at every transition, and refreshes docs/story-maps/README.md per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem / the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem contract pattern. Companion to /wr-itil:capture-story-map (lightweight aside surface).
+description: "Heavyweight story-map intake + lifecycle management following the \"Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology\" architecture rule Phase 2. Authors backbone × ribs × slices structure on draft maps, transitions through draft → accepted → in-progress → completed → archived, re-validates I3 + I4 invariants at every transition, and refreshes docs/story-maps/README.md per the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem / the \"Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation\" problem contract pattern. Companion to /wr-itil:capture-story-map (lightweight aside surface)."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills-codex/mitigate-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mitigate-incident
-description: Record a mitigation attempt against an incident — transitions an investigating incident to mitigating on the first attempt, appends subsequent attempts to the Mitigation attempts timeline. Evidence-first gate enforced per the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule.
+description: "Record a mitigation attempt against an incident — transitions an investigating incident to mitigating on the first attempt, appends subsequent attempts to the Mitigation attempts timeline. Evidence-first gate enforced per the \"Add `manage-incident` Skill to `wr-itil` Plugin\" architecture rule."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill
 ---
 

package/skills-codex/reconcile-readme/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: reconcile-readme
-description: Detect and correct drift between docs/problems/README.md and the on-disk ticket inventory. Wraps the diagnose-only `<itil-plugin-root>/scripts/reconcile-readme.sh` script with an agent-applied-edits pattern that preserves narrative content (the "Last reviewed" prose paragraph and Closed-section closure-via free text). Use when README WSJF Rankings, Verification Queue, or Closed sections drift from filesystem state — typically detected by manage-problem Step 0 preflight or work-problems Step 0 preflight.
+description: "Detect and correct drift between docs/problems/README.md and the on-disk ticket inventory. Wraps the diagnose-only `<itil-plugin-root>/scripts/reconcile-readme.sh` script with an agent-applied-edits pattern that preserves narrative content (the \"Last reviewed\" prose paragraph and Closed-section closure-via free text). Use when README WSJF Rankings, Verification Queue, or Closed sections drift from filesystem state — typically detected by manage-problem Step 0 preflight or work-problems Step 0 preflight."
 allowed-tools: Read, Edit, Write, Bash, Grep, Glob
 ---
 

package/skills-codex/reconcile-stories/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: reconcile-stories
-description: Detect and correct drift between docs/stories/README.md and the on-disk story inventory. Wraps the diagnose-only <itil-plugin-root>/scripts/reconcile-stories.sh script with an agent-applied-edits pattern that preserves narrative content (the "Last reviewed" prose paragraph). Use when docs/stories/README.md Story Rankings or Done sections drift from filesystem state — typically detected by manage-story Step 0 preflight or work-problems preflight on RFC iters with story-tier traces.
+description: "Detect and correct drift between docs/stories/README.md and the on-disk story inventory. Wraps the diagnose-only <itil-plugin-root>/scripts/reconcile-stories.sh script with an agent-applied-edits pattern that preserves narrative content (the \"Last reviewed\" prose paragraph). Use when docs/stories/README.md Story Rankings or Done sections drift from filesystem state — typically detected by manage-story Step 0 preflight or work-problems preflight on RFC iters with story-tier traces."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills-codex/reconcile-story-maps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: reconcile-story-maps
-description: Detect and correct drift between docs/story-maps/README.md and the on-disk story-map HTML inventory. Wraps the diagnose-only <itil-plugin-root>/scripts/reconcile-story-maps.sh script with an agent-applied-edits pattern preserving narrative content.
+description: "Detect and correct drift between docs/story-maps/README.md and the on-disk story-map HTML inventory. Wraps the diagnose-only <itil-plugin-root>/scripts/reconcile-story-maps.sh script with an agent-applied-edits pattern preserving narrative content."
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob
 ---
 

package/skills-codex/report-upstream/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: report-upstream
-description: Report a local problem ticket as a structured issue against an upstream repository, with bidirectional cross-references and SECURITY.md-aware routing for security-classified tickets. Implements the contract in the "Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`" architecture rule, with the "Report-upstream classifier is problem-first — supersedes Decision Outcome Steps 3 + 5" architecture rule governing problem-first classifier + default body shape.
+description: "Report a local problem ticket as a structured issue against an upstream repository, with bidirectional cross-references and SECURITY.md-aware routing for security-classified tickets. Implements the contract in the \"Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`\" architecture rule, with the \"Report-upstream classifier is problem-first — supersedes Decision Outcome Steps 3 + 5\" architecture rule governing problem-first classifier + default body shape."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill, Agent
 ---
 

package/skills-codex/restore-incident/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: restore-incident
-description: Mark an incident as service-restored — transitions a mitigating incident to restored, appends a Timeline entry, and hands off to /wr-itil:manage-problem for linked-problem creation or update per the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule.
+description: "Mark an incident as service-restored — transitions a mitigating incident to restored, appends a Timeline entry, and hands off to /wr-itil:manage-problem for linked-problem creation or update per the \"Add `manage-incident` Skill to `wr-itil` Plugin\" architecture rule."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill
 ---
 

package/skills-codex/review-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: review-problems
-description: Re-assess every open and known-error problem ticket in docs/problems/ — re-read RISK-POLICY.md, re-rate Impact × Likelihood, re-estimate Effort, recalculate WSJF, surface pending verifications, auto-transition Open → Known Error where warranted, and rewrite docs/problems/README.md with the refreshed ranking. Writes to problem files and the README cache; commits the refresh per the "Governance Skills Commit Their Own Completed Work" architecture rule.
+description: "Re-assess every open and known-error problem ticket in docs/problems/ — re-read RISK-POLICY.md, re-rate Impact × Likelihood, re-estimate Effort, recalculate WSJF, surface pending verifications, auto-transition Open → Known Error where warranted, and rewrite docs/problems/README.md with the refreshed ranking. Writes to problem files and the README cache; commits the refresh per the \"Governance Skills Commit Their Own Completed Work\" architecture rule."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill
 ---
 

package/skills-codex/scaffold-intake/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: scaffold-intake
-description: Scaffold the four OSS intake surfaces (.github/ISSUE_TEMPLATE/, SECURITY.md, SUPPORT.md, CONTRIBUTING.md) for a downstream project that adopts @windyroad/itil. Idempotent, foreground-synchronous, and respects the "Gate Marker Lifecycle: TTL + Drift, Not Stop-Hook Reset" architecture rule marker semantics. Implements the contract in the "Scaffold downstream OSS intake — skill + layered triggers" architecture rule.
+description: "Scaffold the four OSS intake surfaces (.github/ISSUE_TEMPLATE/, SECURITY.md, SUPPORT.md, CONTRIBUTING.md) for a downstream project that adopts @windyroad/itil. Idempotent, foreground-synchronous, and respects the \"Gate Marker Lifecycle: TTL + Drift, Not Stop-Hook Reset\" architecture rule marker semantics. Implements the contract in the \"Scaffold downstream OSS intake — skill + layered triggers\" architecture rule."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
 ---
 

package/skills-codex/transition-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: transition-problem
-description: Advance a problem ticket's lifecycle status — Open → Known Error, Known Error → Verification Pending (verifying), Verification Pending → Closed. Renames the ticket file, updates the Status field, and refreshes docs/problems/README.md in the same commit. Hosts the transition execution inline (pre-flight checks, the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem staging-trap handling, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection, the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem README refresh, the "Governance Skills Commit Their Own Completed Work" architecture rule commit) per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended "Split-skill execution ownership". Use when the user asks to "transition", "close", "mark known-error", or "release" a specific ticket.
+description: "Advance a problem ticket's lifecycle status — Open → Known Error, Known Error → Verification Pending (verifying), Verification Pending → Closed. Renames the ticket file, updates the Status field, and refreshes docs/problems/README.md in the same commit. Hosts the transition execution inline (pre-flight checks, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem staging-trap handling, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh, the \"Governance Skills Commit Their Own Completed Work\" architecture rule commit) per the \"Rename `wr-problem` Plugin to `wr-itil`\" architecture rule amended \"Split-skill execution ownership\". Use when the user asks to \"transition\", \"close\", \"mark known-error\", or \"release\" a specific ticket."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill
 ---
 

package/skills-codex/transition-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: transition-problems
-description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem re-stage, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection, the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the "Governance Skills Commit Their Own Completed Work" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
+description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the \"Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit\" problem re-stage, the \"Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external\" problem external-root-cause detection, the \"Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently\" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the \"Governance Skills Commit Their Own Completed Work\" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill, Agent
 ---
 

package/skills-codex/update-upstream/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: update-upstream
-description: Post a lifecycle-update comment to an upstream issue when a local problem ticket transitions. Drafts a transition-specific update (root-cause confirmed / fix released / closed), composes the prose through the external-comms risk gate + voice-tone gate, auto-posts within appetite, queues above-appetite. Reciprocal sibling to /wr-itil:report-upstream — initial-filing vs lifecycle-update split per the "Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`" architecture rule amendment (the "Problem 080: No bidirectional update of upstream-reported problems — local lifecycle transitions never propagate back to the reporter" problem).
+description: "Post a lifecycle-update comment to an upstream issue when a local problem ticket transitions. Drafts a transition-specific update (root-cause confirmed / fix released / closed), composes the prose through the external-comms risk gate + voice-tone gate, auto-posts within appetite, queues above-appetite. Reciprocal sibling to /wr-itil:report-upstream — initial-filing vs lifecycle-update split per the \"Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`\" architecture rule amendment (the \"Problem 080: No bidirectional update of upstream-reported problems — local lifecycle transitions never propagate back to the reporter\" problem)."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill, Agent
 ---
 

package/skills-codex/work-problem/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: work-problem
-description: Pick the highest-WSJF open or known-error problem ticket and work it — investigate, implement, commit, and release per the standard manage-problem workflow. Selection is framework-mediated (WSJF + documented tie-break ladder per the "— Decision-Delegation Contract: when agents act on the framework vs ask the user" architecture rule); singular variant; distinct from /wr-itil:work-problems (plural AFK orchestrator). Use this when the user asks to "work the next problem", "work the top of the queue", or "grind through one ticket".
+description: "Pick the highest-WSJF open or known-error problem ticket and work it — investigate, implement, commit, and release per the standard manage-problem workflow. Selection is framework-mediated (WSJF + documented tie-break ladder per the \"— Decision-Delegation Contract: when agents act on the framework vs ask the user\" architecture rule); singular variant; distinct from /wr-itil:work-problems (plural AFK orchestrator). Use this when the user asks to \"work the next problem\", \"work the top of the queue\", or \"grind through one ticket\"."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input, Skill, Agent
 ---
 

package/skills-codex/work-problems/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: work-problems
-description: Drain the ITIL problem backlog in WSJF order using isolated Codex CLI iterations, governed commits, pushes, and releases.
+description: "Drain the ITIL problem backlog in WSJF order using isolated Codex CLI iterations, governed commits, pushes, and releases."
 ---
 
 <!-- Generated from the runtime-neutral skill source. Do not edit. -->