@windyroad/itil 0.14.0 → 0.15.0

package/skills/list-incidents/SKILL.md

@@ -0,0 +1,81 @@
+---
+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.
+allowed-tools: Read, Bash, Grep, Glob
+---
+
+# List Incidents
+
+Display the active incident backlog — investigating, mitigating, and restored incidents — sorted by severity (highest first). This skill is a pure read-only view of `docs/incidents/`; it does not edit, transition, close, or create incidents. For those operations, use the dedicated skills (`/wr-itil:manage-incident` to declare / update / mitigate / restore / close / link).
+
+This skill is the P071 phased-landing split of `/wr-itil:manage-incident list` per ADR-010 amended Skill Granularity rule: one skill per distinct user intent. The original `/wr-itil:manage-incident list` subcommand route remains as a thin-router forwarder during the deprecation window but is scheduled for removal in `@windyroad/itil`'s next major version.
+
+## Scope
+
+Included in the ranking table:
+- `docs/incidents/*.investigating.md` — symptoms reported, scope being established
+- `docs/incidents/*.mitigating.md` — mitigation(s) in flight
+- `docs/incidents/*.restored.md` — service verified restored, awaiting close gate
+
+`docs/incidents/*.closed.md` is omitted entirely (the view is of active incidents, not the closed archive). Closed incidents remain readable by filename convention; this skill does not index them.
+
+**Severity, not WSJF** — per ADR-011: incidents are time-bound events where the WSJF "effort" divisor is meaningless during a live event. Severity uses Impact × Likelihood from `RISK-POLICY.md`, interpreted as "right now, what's the live business impact?". The skill surfaces the severity score from each incident file's frontmatter directly — no re-scoring, no auto-transitioning.
+
+## Steps
+
+### 1. Live scan
+
+Enumerate the active incident files via glob:
+
+```bash
+ls docs/incidents/*.investigating.md docs/incidents/*.mitigating.md docs/incidents/*.restored.md 2>/dev/null
+```
+
+If the `docs/incidents/` directory does not exist or no active incidents are present, report "No active incidents." and exit.
+
+For each matched file, read the `**Status**`, `**Severity**`, and the first-line `# Incident <I###>: <Title>` header. The severity line shape is:
+
+```
+**Severity**: <score> (<label>) — Impact: <label> (<n>) x Likelihood: <label> (<n>)
+```
+
+Extract the numeric `<score>` for sorting. If severity is missing, treat the incident as severity 0 and flag it so the user knows the incident file is incomplete.
+
+### 2. Display
+
+Render one section:
+
+**Active Incidents** — sorted by severity descending:
+
+```
+| Severity | ID | Title | Status |
+|----------|------|-------|--------|
+| <score> | I<NNN> | <title> | <status> |
+```
+
+If the section is empty (no active incidents), omit the table and print "No active incidents." instead.
+
+### 3. Trailing suggestions
+
+After the table, print one short pointer depending on what the output showed:
+
+- When the table is non-empty: `Run /wr-itil:manage-incident <I###> to update a specific incident, or /wr-itil:manage-incident <I###> mitigate / restored / close to advance its lifecycle.`
+- When the table is empty: (no pointer needed).
+
+## Ownership boundary
+
+`list-incidents` is read-only — it does not modify, rename, or commit any files. There is no README cache for incidents (unlike `docs/problems/README.md` which the `review-problems` skill maintains). Every invocation runs a live scan. If the output seems wrong, check the incident file frontmatter directly; there is no cache to refresh.
+
+## Related
+
+- **P071** (`docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md`) — originating ticket. This skill is slice 5 of the P071 phased-landing plan.
+- **ADR-010 amended** (`docs/decisions/010-rename-wr-problem-to-wr-itil.proposed.md` — Skill Granularity section) — canonical skill-split naming + forwarder contract + `deprecated-arguments: true` frontmatter flag.
+- **ADR-011** (`docs/decisions/011-manage-incident-skill-wrapping.proposed.md`) — incident lifecycle file-suffix conventions (`.investigating.md` / `.mitigating.md` / `.restored.md` / `.closed.md`) + "Severity, not WSJF" rule.
+- **ADR-037** (`docs/decisions/037-skill-testing-strategy.proposed.md`) — contract-assertion bats pattern applied to this skill.
+- **JTBD-001** (`docs/jtbd/solo-developer/JTBD-001-enforce-governance.proposed.md`) — discoverable surface via `/wr-itil:` autocomplete.
+- **JTBD-101** (`docs/jtbd/plugin-developer/JTBD-101-extend-suite.proposed.md`) — one skill per distinct user intent.
+- **JTBD-201** (`docs/jtbd/tech-lead/JTBD-201-restore-service-fast.proposed.md`) — incident status visibility for audit trail.
+- `packages/itil/skills/manage-incident/SKILL.md` — hosts the thin-router forwarder for the deprecated `manage-incident list` form.
+- `packages/itil/skills/list-problems/SKILL.md` — slice 1 precedent; this skill mirrors its read-only display shape.
+
+$ARGUMENTS

package/skills/list-incidents/test/list-incidents-contract.bats

@@ -0,0 +1,115 @@
+#!/usr/bin/env bats
+# Contract assertions for /wr-itil:list-incidents (P071 split slice 5).
+#
+# This skill hosts the "list active incidents" user intent previously
+# hidden behind /wr-itil:manage-incident list. It is a pure read-only
+# display skill — no branching, no interaction, no file edits.
+#
+# Structural assertion — Permitted Exception to the source-grep ban
+# (ADR-005 / P011 / ADR-037 contract-assertion pattern).
+#
+# @problem P071
+# @jtbd JTBD-001 (enforce governance without slowing down — discoverable surface)
+# @jtbd JTBD-101 (extend the suite with clear patterns — one skill per distinct user intent)
+# @jtbd JTBD-201 (restore service fast with an audit trail — incident status visibility)
+#
+# Cross-reference:
+#   P071: docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md
+#   ADR-010 amended (Skill Granularity section) — split naming + forwarder contract
+#   ADR-011 — manage-incident skill-wrapping precedent (list-incidents mirrors its file conventions)
+#   ADR-037 — contract-assertion bats pattern
+
+setup() {
+  SKILL_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
+  SKILL_FILE="${SKILL_DIR}/SKILL.md"
+}
+
+@test "SKILL.md exists and has frontmatter" {
+  [ -f "$SKILL_FILE" ]
+  run head -1 "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+  [ "$output" = "---" ]
+}
+
+@test "SKILL.md frontmatter name is wr-itil:list-incidents (P071 + ADR-010 amended)" {
+  # Split naming convention per ADR-010 amendment: <verb>-<object> pair.
+  # The new skill's name must match the phased-landing plan pinned in P071.
+  run grep -n "^name: wr-itil:list-incidents$" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md frontmatter description names the list intent (P071)" {
+  # Description must name "list" and "incident" so Claude Code autocomplete
+  # surfaces the user intent rather than a generic name.
+  run grep -inE "^description:.*list.*incident|^description:.*incident.*list" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md frontmatter allowed-tools is read-only (P071 — read-only list display)" {
+  # Pure read-only list display (mirrors list-problems slice 1). No Write,
+  # no Edit, no AskUserQuestion. This assertion is the enforceable contract —
+  # future maintainers cannot accidentally grow the tool surface past the
+  # intent.
+  run grep -nE "^allowed-tools:" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+  run grep -E "^allowed-tools:.*(Write|Edit|AskUserQuestion)" "$SKILL_FILE"
+  [ "$status" -ne 0 ]
+}
+
+@test "SKILL.md documents the read-only scan scope (P071 + ADR-011)" {
+  # The skill reads the three active incident statuses per ADR-011:
+  # .investigating.md, .mitigating.md, and .restored.md. Closed incidents
+  # are omitted (the view is active backlog, not archive). The SKILL.md
+  # must name all three glob patterns explicitly so the contract is
+  # legible.
+  run grep -inE "\.investigating\.md" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+  run grep -inE "\.mitigating\.md" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+  run grep -inE "\.restored\.md" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md documents severity-sorted output (P071 + ADR-011)" {
+  # Unlike list-problems (WSJF-sorted), list-incidents is severity-sorted
+  # per ADR-011 "Severity, not WSJF" — incidents are time-bound events
+  # where effort divisor is meaningless. The SKILL.md must name severity
+  # as the sort key.
+  run grep -inE "severity" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md cites P071 and ADR-010 amended (P071 + ADR-025)" {
+  # ADR-025 inheritance per ADR-037: contract-assertion bats should reflect
+  # traceability cites on the skill spec document.
+  run grep -inE "P071|ADR-010" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md does not carry a deprecated-arguments frontmatter flag (clean-split skill)" {
+  # list-incidents is a clean-split skill with no argument-subcommands
+  # itself. ADR-010 amendment's `deprecated-arguments: true` flag is only
+  # valid on host skills with forwarder routes — list-incidents is the
+  # forwarder TARGET, not the host. It must NOT carry the flag.
+  run grep -E "^deprecated-arguments:" "$SKILL_FILE"
+  [ "$status" -ne 0 ]
+}
+
+@test "SKILL.md does not use word-argument subcommand branching (P071 regression guard)" {
+  # The whole point of P071: Claude Code autocomplete does not surface
+  # arguments. A clean-split skill must not reintroduce word-arg subcommand
+  # routing. The SKILL.md must not contain `If arguments start with "list"`
+  # / `If arguments contain "mitigate"` / etc. patterns.
+  run grep -inE "If arguments start with|If arguments contain" "$SKILL_FILE"
+  [ "$status" -ne 0 ]
+}
+
+@test "SKILL.md documents the ownership boundary — no README rewrite (P071)" {
+  # list-incidents displays active incidents but does NOT maintain a README
+  # cache (unlike list-problems which reads a README written by review-problems).
+  # For incidents, there is no README cache — the skill always runs a live
+  # scan. The SKILL.md must explicitly name the "read-only / no-edit" stance
+  # so the ownership boundary is legible to future maintainers.
+  run grep -inE "read-only|does not (edit|modify|rewrite|commit)" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}

package/skills/manage-incident/SKILL.md

@@ -2,6 +2,7 @@
 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.
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
+deprecated-arguments: true
 ---
 
 # Incident Management Skill
@@ -71,10 +72,58 @@ Severity uses the Impact × Likelihood matrix from `RISK-POLICY.md`, interpreted
 
 Determine the operation from `$ARGUMENTS`:
 
-- If arguments start with "list" → show active incidents summary
-- If arguments start with `I<NNN>` or a bare number → this is an update, mitigate, restore, close, or link
+- If arguments start with "list" → **delegate to `/wr-itil:list-incidents`** via the Skill tool. See "Deprecated-argument forwarders" below.
+- If arguments match `<I###> mitigate <action>` → **delegate to `/wr-itil:mitigate-incident <I###> <action>`** via the Skill tool. See "Deprecated-argument forwarders" below.
+- If arguments match `<I###> restored` → **delegate to `/wr-itil:restore-incident <I###>`** via the Skill tool. See "Deprecated-argument forwarders" below.
+- If arguments match `<I###> close` → **delegate to `/wr-itil:close-incident <I###>`** via the Skill tool. See "Deprecated-argument forwarders" below.
+- If arguments match `<I###> link P<MMM>` → **delegate to `/wr-itil:link-incident <I###> P<MMM>`** via the Skill tool. See "Deprecated-argument forwarders" below.
+- If arguments start with `I<NNN>` or a bare number → this is an update
 - Otherwise → declare a new incident
 
+#### Deprecated-argument forwarders (ADR-010 amended + P071)
+
+Per ADR-010's amended Skill Granularity section, word-argument subcommands that name distinct user intents are being split into their own named skills. During the deprecation window, this skill's Step 1 parser retains the legacy argument routes as **thin-router forwarders** that re-invoke the new named skill via the Skill tool AND emit a one-line systemMessage with the canonical deprecation notice so the user learns the new invocation shape.
+
+**Forwarder for `list`** (P071 split slice 5 — new skill `/wr-itil:list-incidents`):
+
+When `$ARGUMENTS` contains the word `list` as a top-level argument (not inside an incident body edit), delegate to `/wr-itil:list-incidents` via the Skill tool and emit this systemMessage verbatim:
+
+> `/wr-itil:manage-incident list is deprecated; use /wr-itil:list-incidents directly. This forwarder will be removed in @windyroad/itil's next major version.`
+
+The forwarder does NOT re-implement the list logic locally — it invokes the Skill tool with `wr-itil:list-incidents` and returns the new skill's output verbatim. Duplicating the scan logic would harden the deprecation window into a permanent fork.
+
+**Forwarder for `<I###> mitigate <action>`** (P071 split slice 6a — new skill `/wr-itil:mitigate-incident`):
+
+When `$ARGUMENTS` matches the shape `<I###> mitigate <action>` (an incident ID followed by the literal word `mitigate` followed by a free-text action), delegate to `/wr-itil:mitigate-incident <I###> <action>` via the Skill tool and emit this systemMessage verbatim:
+
+> `/wr-itil:manage-incident <I###> mitigate <action> is deprecated; use /wr-itil:mitigate-incident <I###> <action> directly. This forwarder will be removed in @windyroad/itil's next major version.`
+
+The forwarder does NOT re-implement the mitigation logic locally — it invokes the Skill tool with `wr-itil:mitigate-incident`, passes `<I###> <action>` through as the data parameters, and returns the new skill's output verbatim. Duplicating the rename + evidence-gate + timeline-append logic would harden the deprecation window into a permanent fork. The data-parameter shape `<I###> <action>` is permitted under ADR-010 amended — only the verb word `mitigate` is being split out.
+
+**Forwarder for `<I###> restored`** (P071 split slice 6b — new skill `/wr-itil:restore-incident`):
+
+When `$ARGUMENTS` matches the shape `<I###> restored` (an incident ID followed by the literal word `restored`), delegate to `/wr-itil:restore-incident <I###>` via the Skill tool and emit this systemMessage verbatim:
+
+> `/wr-itil:manage-incident <I###> restored is deprecated; use /wr-itil:restore-incident <I###> directly. This forwarder will be removed in @windyroad/itil's next major version.`
+
+The forwarder does NOT re-implement the restore logic locally — it invokes the Skill tool with `wr-itil:restore-incident`, passes `<I###>` through as the data parameter, and returns the new skill's output verbatim. Duplicating the rename + verification-signal prompt + manage-problem handoff logic would harden the deprecation window into a permanent fork.
+
+**Forwarder for `<I###> close`** (P071 split slice 6c — new skill `/wr-itil:close-incident`):
+
+When `$ARGUMENTS` matches the shape `<I###> close` (an incident ID followed by the literal word `close`), delegate to `/wr-itil:close-incident <I###>` via the Skill tool and emit this systemMessage verbatim:
+
+> `/wr-itil:manage-incident <I###> close is deprecated; use /wr-itil:close-incident <I###> directly. This forwarder will be removed in @windyroad/itil's next major version.`
+
+The forwarder does NOT re-implement the close logic locally — it invokes the Skill tool with `wr-itil:close-incident`, passes `<I###>` through as the data parameter, and returns the new skill's output verbatim. Duplicating the linked-problem gate + rename logic would harden the deprecation window into a permanent fork.
+
+**Forwarder for `<I###> link P<MMM>`** (P071 split slice 6d — new skill `/wr-itil:link-incident`):
+
+When `$ARGUMENTS` matches the shape `<I###> link P<MMM>` (an incident ID followed by the literal word `link` followed by a problem ID), delegate to `/wr-itil:link-incident <I###> P<MMM>` via the Skill tool and emit this systemMessage verbatim:
+
+> `/wr-itil:manage-incident <I###> link P<MMM> is deprecated; use /wr-itil:link-incident <I###> P<MMM> directly. This forwarder will be removed in @windyroad/itil's next major version.`
+
+The forwarder does NOT re-implement the link logic locally — it invokes the Skill tool with `wr-itil:link-incident`, passes `<I###> P<MMM>` through as the data parameters, and returns the new skill's output verbatim. Duplicating the problem-file-lookup + Linked Problem section write logic would harden the deprecation window into a permanent fork. The data-parameter shape `<I###> P<MMM>` is permitted under ADR-010 amended — only the verb word `link` is being split out.
+
 ### 2. For new incidents: Check for duplicates FIRST
 
 Before creating, search `docs/incidents/` for active (non-closed) incidents with overlapping symptoms or scope. The user may already have an incident open for this outage.
@@ -158,79 +207,33 @@ ls docs/incidents/<I###>-*.md 2>/dev/null
 
 Append new observations, hypotheses, or timeline entries. **Every hypothesis must cite evidence.** If the user proposes a hypothesis without evidence, ask via `AskUserQuestion` what evidence supports it before writing.
 
-### 7. For mitigate: Record and transition to mitigating
-
-When the first mitigation attempt is made:
-
-1. `git mv docs/incidents/<I###>-<title>.investigating.md docs/incidents/<I###>-<title>.mitigating.md`
-2. Update the **Status** field to "Mitigating"
-3. Append to **Mitigation attempts**: `[<timestamp> UTC] <action> → <outcome>` (outcome may be "pending verification" initially; update once the verification signal is known)
+### 7. For mitigate: delegate to `/wr-itil:mitigate-incident` (P071 split slice 6a)
 
-Pre-flight check before first mitigation: the file must contain at least one hypothesis with cited evidence. If not, block the transition and ask the user what evidence supports the chosen action.
+The `mitigate` subcommand is now hosted by the `/wr-itil:mitigate-incident` skill. This step exists as a thin-router forwarder — the Step 1 parser recognises the `<I###> mitigate <action>` shape and delegates via the Skill tool. This body is intentionally empty of implementation logic; the canonical documentation of the rename, Status update, evidence-gate pre-flight, and Mitigation attempts append lives in `/wr-itil:mitigate-incident`.
 
-### 8. For restore: Transition and hand off to manage-problem
+Do not re-implement the rename or the evidence gate here — delegate. See "Deprecated-argument forwarders" under Step 1 for the canonical systemMessage.
 
-Pre-flight checks before restore:
+### 8. For restore: delegate to `/wr-itil:restore-incident` (P071 split slice 6b)
 
-- [ ] At least one mitigation attempt is recorded with outcome
-- [ ] A verification signal is captured (e.g., "error rate back to baseline per Datadog", "user reports normal", "synthetic probe passing")
+The `restored` subcommand is now hosted by the `/wr-itil:restore-incident` skill. This step exists as a thin-router forwarder — the Step 1 parser recognises the `<I###> restored` shape and delegates via the Skill tool. This body is intentionally empty of implementation logic; the canonical documentation of the pre-flight checks, rename, Status update, Timeline append, and manage-problem handoff lives in `/wr-itil:restore-incident`.
 
-If checks pass:
-
-1. `git mv docs/incidents/<I###>-<title>.mitigating.md docs/incidents/<I###>-<title>.restored.md`
-2. Update the **Status** field to "Restored"
-3. Append to **Timeline**: `[<timestamp> UTC] Service restored — <verification signal>`
-
-Then perform the **handoff to problem management**:
-
-1. Ask via `AskUserQuestion`: "Service restored. Should I create or update a problem record for the root cause? (a) yes — recommended, (b) no — document why (trivial/one-off)"
-2. If yes, construct a handoff payload:
-   - Incident ID and title
-   - Timeline summary
-   - Top-ranked hypothesis + cited evidence
-   - Mitigation applied + verification signal
-3. Invoke `wr-itil:manage-problem` via the `Skill` tool with the payload as arguments. The problem skill's existing dedupe flow handles new-vs-update.
-4. Capture the returned `P<NNN>` and write a **Linked Problem** section into the incident file:
-   ```markdown
-   ## Linked Problem
-   P<NNN> (<title>) — <status>
-   ```
-5. If the user chose "no", write a **No Problem** section with the justification and skip the handoff:
-   ```markdown
-   ## No Problem
-   <reason — e.g. "one-off cosmic-bit-flip; not reproducible">
-   ```
-
-### 9. For close: Gate on linked problem status
-
-The close operation checks the linked problem's file suffix:
-
-```bash
-linked_id=<extracted from Linked Problem section>
-linked_file=$(ls docs/problems/${linked_id}-*.md 2>/dev/null | head -1)
-```
+Do not re-implement the rename or the problem handoff here — delegate. See "Deprecated-argument forwarders" under Step 1 for the canonical systemMessage.
 
-- If `linked_file` ends with `.known-error.md`, `.verifying.md`, or `.closed.md` → close is allowed (per ADR-022: `.verifying.md` means root cause is confirmed AND fix has been released, which satisfies the "Restored → Closed" handoff at least as well as Known Error did under the old contract)
-- If `linked_file` ends with `.open.md` → close is blocked; report "Linked problem ${linked_id} is still Open. Transition it to Known Error first, or update the Linked Problem reference."
-- If no linked problem and the file has a **No Problem** section → close is allowed
+### 9. For close: delegate to `/wr-itil:close-incident` (P071 split slice 6c)
 
-On close:
+The `close` subcommand is now hosted by the `/wr-itil:close-incident` skill. This step exists as a thin-router forwarder — the Step 1 parser recognises the `<I###> close` shape and delegates via the Skill tool. This body is intentionally empty of implementation logic; the canonical documentation of the Linked-Problem gate (accepting `.known-error.md`, `.verifying.md`, and `.closed.md`), the No Problem bypass, and the rename lives in `/wr-itil:close-incident`.
 
-1. `git mv docs/incidents/<I###>-<title>.restored.md docs/incidents/<I###>-<title>.closed.md`
-2. Update the **Status** field to "Closed"
-3. Append to **Timeline**: `[<timestamp> UTC] Incident closed`
+Do not re-implement the close gate or the rename here — delegate. See "Deprecated-argument forwarders" under Step 1 for the canonical systemMessage.
 
 ### 10. For list: Show active incidents
 
 Read all `.investigating.md`, `.mitigating.md`, and `.restored.md` files in `docs/incidents/`. Extract ID, title, severity, and status. Sort by severity (highest first). Display as a markdown table.
 
-### 11. For link: Attach a problem
+### 11. For link: delegate to `/wr-itil:link-incident` (P071 split slice 6d)
 
-When the user runs `incident <I###> link P<MMM>`:
+The `link` subcommand is now hosted by the `/wr-itil:link-incident` skill. This step exists as a thin-router forwarder — the Step 1 parser recognises the `<I###> link P<MMM>` shape and delegates via the Skill tool. This body is intentionally empty of implementation logic; the canonical documentation of the problem-file lookup and the `## Linked Problem` section write (including the retroactive-link-from-No-Problem case) lives in `/wr-itil:link-incident`.
 
-1. Verify `docs/problems/P<MMM>-*.md` exists
-2. Read or add the **Linked Problem** section with `P<MMM> (<title>) — <status>`
-3. Report the link
+Do not re-implement the link logic here — delegate. See "Deprecated-argument forwarders" under Step 1 for the canonical systemMessage.
 
 ### 12. Edge cases
 

package/skills/manage-incident/test/manage-incident-close-forwarder.bats

@@ -0,0 +1,67 @@
+#!/usr/bin/env bats
+# Contract assertions for manage-incident's `close` subcommand forwarder (P071 split slice 6c).
+#
+# Per ADR-010 amended (Skill Granularity section) + P071 phased plan:
+# `/wr-itil:manage-incident <I> close` delegates to the new
+# `/wr-itil:close-incident <I>` skill via a thin-router forwarder.
+# Original skill already carries `deprecated-arguments: true` frontmatter
+# (slice 5); forwarder emits a canonical one-line systemMessage
+# deprecation notice.
+#
+# Structural assertion — Permitted Exception to the source-grep ban
+# (ADR-005 / P011 / ADR-037 contract-assertion pattern).
+#
+# @problem P071
+# @jtbd JTBD-001 (enforce governance without slowing down)
+# @jtbd JTBD-101 (extend the suite with clear patterns)
+# @jtbd JTBD-201 (restore service fast with an audit trail)
+#
+# Cross-reference:
+#   P071: docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md
+#   ADR-010 amended — split naming + forwarder contract + deprecated-arguments flag
+#   ADR-011 — manage-incident skill-wrapping precedent (close gate on linked problem)
+#   ADR-022 — problem lifecycle verification-pending status (.verifying.md allowance)
+#   ADR-013 Rule 1 — structured user interaction (forwarder emits systemMessage, not AskUserQuestion)
+#   ADR-037 — contract-assertion bats pattern
+
+setup() {
+  SKILL_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
+  SKILL_FILE="${SKILL_DIR}/SKILL.md"
+}
+
+@test "manage-incident SKILL.md frontmatter has deprecated-arguments: true (ADR-010 amended)" {
+  # Already pinned by slice 5; slice 6c inherits. Guard against regression.
+  run grep -nE "^deprecated-arguments:[[:space:]]*true[[:space:]]*$" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 forwards 'close' argument to /wr-itil:close-incident (P071)" {
+  # The forwarder names the target skill explicitly so the router is legible
+  # at the contract level. ADR-010's canonical shape: "invokes the new
+  # named skill via the Skill tool, not via re-prompting the user".
+  run grep -inE "/wr-itil:close-incident" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 emits the canonical close deprecation notice (ADR-010 amended)" {
+  # ADR-010's canonical deprecation-notice template:
+  # "/wr-<plugin>:<old> <arg> is deprecated; use /wr-<plugin>:<new>
+  #  directly. This forwarder will be removed in <plugin>'s next major
+  #  version."
+  # The notice MUST be emitted as a systemMessage (not AskUserQuestion)
+  # because deprecation is informational, not decisional (ADR-013 Rule 1
+  # structured-interaction scope).
+  run grep -inE "is deprecated.*use /wr-itil:close-incident|deprecated.*close-incident|close.*removed in .* next major version" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 close forwarder delegates via Skill tool (P071 regression guard)" {
+  # The forwarder must not duplicate the close logic — it must delegate.
+  # Per ADR-010: "thin-router forwarder re-invokes the new named skill
+  # via the Skill tool". If the forwarder grows its own gate + rename
+  # logic, the deprecation window will harden into a permanent fork.
+  # Guard against this by asserting the forwarder block mentions "delegate"
+  # or "Skill tool" language near the close-incident reference.
+  run grep -inE "delegate.*close-incident|Skill tool.*close-incident|close-incident.*Skill tool" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}

package/skills/manage-incident/test/manage-incident-link-forwarder.bats

@@ -0,0 +1,67 @@
+#!/usr/bin/env bats
+# Contract assertions for manage-incident's `link` subcommand forwarder (P071 split slice 6d).
+#
+# Per ADR-010 amended (Skill Granularity section) + P071 phased plan:
+# `/wr-itil:manage-incident <I> link P<M>` delegates to the new
+# `/wr-itil:link-incident <I> P<M>` skill via a thin-router forwarder.
+# Original skill already carries `deprecated-arguments: true` frontmatter
+# (slice 5); forwarder emits a canonical one-line systemMessage
+# deprecation notice.
+#
+# Structural assertion — Permitted Exception to the source-grep ban
+# (ADR-005 / P011 / ADR-037 contract-assertion pattern).
+#
+# @problem P071
+# @jtbd JTBD-001 (enforce governance without slowing down)
+# @jtbd JTBD-101 (extend the suite with clear patterns)
+# @jtbd JTBD-201 (restore service fast with an audit trail)
+#
+# Cross-reference:
+#   P071: docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md
+#   ADR-010 amended — split naming + forwarder contract + deprecated-arguments flag
+#   ADR-011 — manage-incident skill-wrapping precedent (Linked Problem section)
+#   ADR-013 Rule 1 — structured user interaction (forwarder emits systemMessage, not AskUserQuestion)
+#   ADR-037 — contract-assertion bats pattern
+
+setup() {
+  SKILL_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
+  SKILL_FILE="${SKILL_DIR}/SKILL.md"
+}
+
+@test "manage-incident SKILL.md frontmatter has deprecated-arguments: true (ADR-010 amended)" {
+  # Already pinned by slice 5; slice 6d inherits. Guard against regression.
+  run grep -nE "^deprecated-arguments:[[:space:]]*true[[:space:]]*$" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 forwards 'link' argument to /wr-itil:link-incident (P071)" {
+  # The forwarder names the target skill explicitly so the router is legible
+  # at the contract level. ADR-010's canonical shape: "invokes the new
+  # named skill via the Skill tool, not via re-prompting the user".
+  run grep -inE "/wr-itil:link-incident" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 emits the canonical link deprecation notice (ADR-010 amended)" {
+  # ADR-010's canonical deprecation-notice template:
+  # "/wr-<plugin>:<old> <arg> is deprecated; use /wr-<plugin>:<new>
+  #  directly. This forwarder will be removed in <plugin>'s next major
+  #  version."
+  # The notice MUST be emitted as a systemMessage (not AskUserQuestion)
+  # because deprecation is informational, not decisional (ADR-013 Rule 1
+  # structured-interaction scope).
+  run grep -inE "is deprecated.*use /wr-itil:link-incident|deprecated.*link-incident|link.*removed in .* next major version" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 link forwarder delegates via Skill tool (P071 regression guard)" {
+  # The forwarder must not duplicate the link logic — it must delegate.
+  # Per ADR-010: "thin-router forwarder re-invokes the new named skill
+  # via the Skill tool". If the forwarder grows its own problem-file-lookup
+  # + Linked Problem write logic, the deprecation window will harden into
+  # a permanent fork. Guard against this by asserting the forwarder block
+  # mentions "delegate" or "Skill tool" language near the link-incident
+  # reference.
+  run grep -inE "delegate.*link-incident|Skill tool.*link-incident|link-incident.*Skill tool" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}

package/skills/manage-incident/test/manage-incident-list-forwarder.bats

@@ -0,0 +1,68 @@
+#!/usr/bin/env bats
+# Contract assertions for manage-incident's `list` subcommand forwarder (P071 split slice 5).
+#
+# Per ADR-010 amended (Skill Granularity section) + P071 phased plan:
+# `/wr-itil:manage-incident list` delegates to the new `/wr-itil:list-incidents`
+# skill via a thin-router forwarder. Original skill carries
+# `deprecated-arguments: true` frontmatter; forwarder emits a
+# canonical one-line systemMessage deprecation notice.
+#
+# Structural assertion — Permitted Exception to the source-grep ban
+# (ADR-005 / P011 / ADR-037 contract-assertion pattern).
+#
+# @problem P071
+# @jtbd JTBD-001 (enforce governance without slowing down)
+# @jtbd JTBD-101 (extend the suite with clear patterns)
+# @jtbd JTBD-201 (restore service fast with an audit trail)
+#
+# Cross-reference:
+#   P071: docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md
+#   ADR-010 amended — split naming + forwarder contract + deprecated-arguments flag
+#   ADR-011 — manage-incident skill-wrapping precedent
+#   ADR-013 Rule 1 — structured user interaction (forwarder emits systemMessage, not AskUserQuestion)
+#   ADR-037 — contract-assertion bats pattern
+
+setup() {
+  SKILL_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
+  SKILL_FILE="${SKILL_DIR}/SKILL.md"
+}
+
+@test "manage-incident SKILL.md frontmatter has deprecated-arguments: true (ADR-010 amended)" {
+  # ADR-010 amendment pins the frontmatter flag name as `deprecated-arguments`.
+  # The host skill of any forwarder route must carry this flag so ADR-037
+  # cross-plugin contract assertions can find the opt-in during the
+  # deprecation window.
+  run grep -nE "^deprecated-arguments:[[:space:]]*true[[:space:]]*$" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 forwards 'list' argument to /wr-itil:list-incidents (P071)" {
+  # The forwarder names the target skill explicitly so the router is legible
+  # at the contract level. ADR-010's canonical shape: "invokes the new
+  # named skill via the Skill tool, not via re-prompting the user".
+  run grep -inE "/wr-itil:list-incidents" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 emits the canonical deprecation notice (ADR-010 amended)" {
+  # ADR-010's canonical deprecation-notice template:
+  # "/wr-<plugin>:<old> <arg> is deprecated; use /wr-<plugin>:<new>
+  #  directly. This forwarder will be removed in <plugin>'s next major
+  #  version."
+  # The notice MUST be emitted as a systemMessage (not AskUserQuestion)
+  # because deprecation is informational, not decisional (ADR-013 Rule 1
+  # structured-interaction scope).
+  run grep -inE "is deprecated.*use /wr-itil:list-incidents|deprecated.*list-incidents|removed in .* next major version" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 forwarder does not re-implement the list logic (P071 regression guard)" {
+  # The forwarder must not duplicate the list logic — it must delegate.
+  # Per ADR-010: "thin-router forwarder re-invokes the new named skill
+  # via the Skill tool". If the forwarder grows its own scan logic, the
+  # deprecation window will harden into a permanent fork. Guard against
+  # this by asserting the forwarder block mentions "delegate" or
+  # "Skill tool" language near the list-incidents reference.
+  run grep -inE "delegate.*list-incidents|Skill tool.*list-incidents|list-incidents.*Skill tool" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}

package/skills/manage-incident/test/manage-incident-mitigate-forwarder.bats

@@ -0,0 +1,66 @@
+#!/usr/bin/env bats
+# Contract assertions for manage-incident's `mitigate` subcommand forwarder (P071 split slice 6a).
+#
+# Per ADR-010 amended (Skill Granularity section) + P071 phased plan:
+# `/wr-itil:manage-incident <I> mitigate <action>` delegates to the new
+# `/wr-itil:mitigate-incident <I> <action>` skill via a thin-router
+# forwarder. Original skill already carries `deprecated-arguments: true`
+# frontmatter (slice 5); forwarder emits a canonical one-line systemMessage
+# deprecation notice.
+#
+# Structural assertion — Permitted Exception to the source-grep ban
+# (ADR-005 / P011 / ADR-037 contract-assertion pattern).
+#
+# @problem P071
+# @jtbd JTBD-001 (enforce governance without slowing down)
+# @jtbd JTBD-101 (extend the suite with clear patterns)
+# @jtbd JTBD-201 (restore service fast with an audit trail)
+#
+# Cross-reference:
+#   P071: docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md
+#   ADR-010 amended — split naming + forwarder contract + deprecated-arguments flag
+#   ADR-011 — manage-incident skill-wrapping precedent
+#   ADR-013 Rule 1 — structured user interaction (forwarder emits systemMessage, not AskUserQuestion)
+#   ADR-037 — contract-assertion bats pattern
+
+setup() {
+  SKILL_DIR="$(cd "$(dirname "$BATS_TEST_FILENAME")/.." && pwd)"
+  SKILL_FILE="${SKILL_DIR}/SKILL.md"
+}
+
+@test "manage-incident SKILL.md frontmatter has deprecated-arguments: true (ADR-010 amended)" {
+  # Already pinned by slice 5; slice 6a inherits. Guard against regression.
+  run grep -nE "^deprecated-arguments:[[:space:]]*true[[:space:]]*$" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 forwards 'mitigate' argument to /wr-itil:mitigate-incident (P071)" {
+  # The forwarder names the target skill explicitly so the router is legible
+  # at the contract level. ADR-010's canonical shape: "invokes the new
+  # named skill via the Skill tool, not via re-prompting the user".
+  run grep -inE "/wr-itil:mitigate-incident" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 emits the canonical mitigate deprecation notice (ADR-010 amended)" {
+  # ADR-010's canonical deprecation-notice template:
+  # "/wr-<plugin>:<old> <arg> is deprecated; use /wr-<plugin>:<new>
+  #  directly. This forwarder will be removed in <plugin>'s next major
+  #  version."
+  # The notice MUST be emitted as a systemMessage (not AskUserQuestion)
+  # because deprecation is informational, not decisional (ADR-013 Rule 1
+  # structured-interaction scope).
+  run grep -inE "is deprecated.*use /wr-itil:mitigate-incident|deprecated.*mitigate-incident|mitigate.*removed in .* next major version" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-incident Step 1 mitigate forwarder delegates via Skill tool (P071 regression guard)" {
+  # The forwarder must not duplicate the mitigate logic — it must delegate.
+  # Per ADR-010: "thin-router forwarder re-invokes the new named skill
+  # via the Skill tool". If the forwarder grows its own rename + evidence-gate
+  # logic, the deprecation window will harden into a permanent fork.
+  # Guard against this by asserting the forwarder block mentions "delegate"
+  # or "Skill tool" language near the mitigate-incident reference.
+  run grep -inE "delegate.*mitigate-incident|Skill tool.*mitigate-incident|mitigate-incident.*Skill tool" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}