@windyroad/itil 1.2.0 → 2.0.0-preview.1111

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

@@ -0,0 +1,192 @@
+---
+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.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+<!-- Generated from the runtime-neutral skill source. Do not edit. -->
+
+> Codex runtime note: use `request_user_input` only where this contract
+> explicitly requires a human decision. Resolve `<itil-plugin-root>` from
+> this installed `SKILL.md`: it is two directories above the skill
+> directory. Run bundled commands from `<itil-plugin-root>/bin/`; do not
+> search the adopter repository or rely on those commands being on `PATH`.
+> Spawn `wr-itil:hang-off-check` with the native Codex subagent tool, wait
+> for it, and close that same agent.
+
+
+# Close Incident
+
+Close a restored incident. Closing is the final lifecycle transition — once closed, the incident file is archival and does not appear in active incident views. The close operation is gated on the Linked Problem reaching an acceptable terminal state, or on the incident carrying a documented "No Problem" justification. The gate exists so the problem-handoff invariant (the "Restore Service Fast with an Audit Trail" user outcome) is preserved: every incident either tracks to a root cause or carries an explicit note that none is required.
+
+This skill is the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem phased-landing split of `/wr-itil:manage-incident <I> close` per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended Skill Granularity rule: one skill per distinct user intent. The argument `<I>` is a data parameter, permitted under the amendment. The original `/wr-itil:manage-incident <I> close` subcommand route remains as a thin-router forwarder during the deprecation window but is scheduled for removal in `@windyroad/itil`'s next major version.
+
+## Arguments
+
+`/wr-itil:close-incident <I###>` — one positional data parameter:
+
+- `<I###>` — the incident ID (e.g. `I007` or bare `007`). Resolves to `docs/incidents/<I###>-*.restored.md` (primary path) or `docs/incidents/<I###>-*.closed.md` (idempotent — already-closed short-circuits).
+
+If `$ARGUMENTS` is empty or malformed, read the message from the arguments and report the expected shape. No request_user_input — the gate itself is a hard check with a message, and an empty-arguments case is a user misinvocation, not a decisional branch.
+
+## Close gate (the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule + the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule)
+
+The close operation checks the Linked Problem's file suffix:
+
+| Linked problem state | File suffix | Close allowed? | Rationale |
+|----------------------|-------------|----------------|-----------|
+| Open | `.open.md` | **Blocked** | Root cause work not yet converged. The problem may still reclassify, re-scope, or need a fix before the incident can be safely archived. |
+| Known Error | `.known-error.md` | Allowed | Root cause is identified and understood; a workaround exists or the risk is accepted. Incident may close. |
+| Verifying | `.verifying.md` | Allowed (the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule) | Fix released, root cause confirmed, post-release verification pending. Per the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule, verifying satisfies the "Restored → Closed" handoff at least as well as Known Error did under the old contract. |
+| Closed | `.closed.md` | Allowed | Problem fully resolved. Incident may close. |
+
+If the incident carries a `## No Problem` section (instead of a Linked Problem), the gate is bypassed — the user has documented why no problem record is required.
+
+## Steps
+
+### 1. Parse arguments
+
+Extract `<I###>` from `$ARGUMENTS`. Normalise:
+
+- Accept `I007`, `i007`, `007`, `7` → canonicalise to `I007` (uppercase I + zero-padded 3 digits).
+- If missing, report "Usage: `/wr-itil:close-incident <I###>`" and exit.
+
+### 2. Locate the incident file
+
+```bash
+ls docs/incidents/<I###>-*.restored.md docs/incidents/<I###>-*.closed.md 2>/dev/null
+```
+
+- If no file matches, report "No restored incident `<I###>` found. If the incident is still mitigating, run `/wr-itil:restore-incident <I###>` first. If no incident with this ID exists, check `/wr-itil:list-incidents`." and exit.
+- If a `.closed.md` file matches, this is an idempotent re-invocation — report "Incident `<I###>` is already closed." and exit without further action.
+- If a `.restored.md` file matches, proceed to Step 3.
+- If both suffixes somehow match (should not happen under the naming convention), report the ambiguity and exit.
+
+### 3. Read the Linked Problem (or No Problem) section
+
+Read the incident file and locate either:
+
+- A `## Linked Problem` section with a line like `P<NNN> (<title>) — <status>`, OR
+- A `## No Problem` section with a justification.
+
+Branch on which section is present:
+
+**Case A — `## Linked Problem` present**:
+
+1. Extract the problem ID `P<NNN>` from the section.
+2. Locate the problem file. Dual-tolerant lookup spans flat layout AND per-state subdir layout (the ": docs/problems/ flat layout migration — per-state subdirs + adopter auto-migration" release design migration window):
+
+   ```bash
+   ls docs/problems/<NNN>-*.md docs/problems/*/<NNN>-*.md 2>/dev/null | head -1
+   ```
+
+   Accept both `P<NNN>-*.md` and `<NNN>-*.md` naming conventions for robustness.
+
+3. Read the problem file's suffix:
+   - `.open.md` → close is **blocked**. Report: "Linked problem `P<NNN>` is still Open. Transition it to Known Error (via `/wr-itil:transition-problem P<NNN> known-error`), or let the release verification pipeline take it to `.verifying.md` before closing this incident. If the problem is genuinely not required, update the Linked Problem section to a No Problem justification instead." and exit.
+   - `.known-error.md`, `.verifying.md`, or `.closed.md` → close is **allowed**. Proceed to Step 4.
+
+**Case B — `## No Problem` present**:
+
+Close is **allowed**. Proceed to Step 4.
+
+**Case C — neither section present**:
+
+Report: "Incident `<I###>` has no Linked Problem or No Problem section. Run `/wr-itil:restore-incident <I###>` to complete the restore handoff first (which writes one of those sections), or run `/wr-itil:link-incident <I###> P<MMM>` to attach an existing problem, or edit the file manually to add a No Problem section." and exit.
+
+### 4. Transition to closed
+
+Compute a UTC timestamp (e.g. `2026-04-21T14:37Z`). Then:
+
+1. `git mv docs/incidents/<I###>-<title>.restored.md docs/incidents/<I###>-<title>.closed.md`
+2. Update the `**Status**:` field from `Restored` to `Closed` via `Edit`.
+3. Append to the `## Timeline` section:
+
+   ```markdown
+   - [<timestamp> UTC] Incident closed
+   ```
+
+### 5. Quality checks
+
+After the close, verify:
+
+- **Status consistency**: `**Status**:` field matches the filename suffix (`Closed` + `.closed.md`).
+- **Timeline monotonicity**: the "Incident closed" entry's timestamp is ≥ the last existing timeline entry's timestamp.
+- **Post-close sections present**: either `## Linked Problem` with an acceptable terminal-state problem, or `## No Problem` with a justification.
+
+### 6. Report
+
+Report:
+
+- The file path closed.
+- The incident ID and title.
+- The transition (Restored → Closed).
+- The linked problem ID (if any) and its state at close-time, OR the No Problem justification.
+- Any quality-check warnings.
+
+### 7. Commit the completed work (the "Governance Skills Commit Their Own Completed Work" architecture rule)
+
+Per the "Governance Skills Commit Their Own Completed Work" architecture rule, governance skills commit their own work.
+
+1. `git add` the renamed incident file.
+2. Delegate to `wr-risk-scorer:pipeline` (subagent_type: `wr-risk-scorer:pipeline`) to assess the staged changes and create a bypass marker. If the subagent type is not available (spawned subagent surface), invoke `/wr-risk-scorer:assess-release` via the installed skill invocation instead — per the "On-Demand Assessment Skills for Governance Plugins" architecture rule it wraps the same pipeline subagent.
+3. `git commit -m "docs(incidents): close I<NNN>"`.
+4. If risk is above appetite: report the above-appetite state clearly and exit without committing (close-incident does not carry `request_user_input` in its allowed-tools — the gate is a hard check). The user can re-run with `--force` semantics by invoking the commit manually if they choose.
+
+### 8. Auto-release when changesets are queued (the "Governance skills auto-release when changesets are queued" architecture rule)
+
+**Skip this step if the skill is running inside an AFK orchestrator.** Orchestrators handle release cadence themselves per the "Inter-iteration release cadence for AFK loops" architecture rule (Step 6.5). When in doubt, defer to the orchestrator by skipping this step.
+
+Otherwise, after the commit in step 7 lands, drain the release queue so the close lands on npm without requiring manual user action.
+
+**Mechanism — delegate, do not re-implement scoring (per the "On-Demand Assessment Skills for Governance Plugins" architecture rule):**
+
+1. Invoke the release scorer. Two paths are valid:
+   - **Primary**: delegate to subagent type `wr-risk-scorer:pipeline` via the native Codex subagent tool.
+   - **Fallback**: if that subagent type is not available, invoke skill `/wr-risk-scorer:assess-release` via the installed skill invocation.
+2. Read the returned `RISK_SCORES: commit=X push=Y release=Z` line.
+3. **Drain condition**: if `push` and `release` are both within appetite (≤ 4/25, "Low" band per `RISK-POLICY.md`), AND `.changeset/` is non-empty, proceed to the drain action. Otherwise, skip the drain and report the unreleased state.
+
+**Drain action (non-interactive, policy-authorised per the "Structured User Interaction for Governance-Skill Decisions" architecture rule Rule 6):**
+
+1. Run `npm run push:watch` (push + wait for CI to pass).
+2. If `.changeset/` remains non-empty after push (i.e. a release PR is pending), run `npm run release:watch` (merge the release PR + wait for npm publish).
+3. Report the release: "Released <package>@<version>. Close record is now live on npm."
+
+**Failure handling**: if `release:watch` fails (CI failure, publish failure), stop and report the failure clearly. Do not retry non-interactively — the user must intervene.
+
+**Above-appetite branch**: if push/release risk is above appetite, skip the drain and report: "Release skipped — risk above appetite. Run `npm run push:watch` and `npm run release:watch` manually when ready."
+
+## Ownership boundary
+
+`close-incident` writes the `## Timeline` close entry, the Status field, and the `.restored.md → .closed.md` rename. It does NOT:
+
+- Restore the incident (that is `/wr-itil:restore-incident <I###>` — slice 6b).
+- Link a problem to the incident (that is `/wr-itil:link-incident <I###> P<MMM>` — slice 6d).
+- Record a mitigation attempt (that is `/wr-itil:mitigate-incident <I###> <action>` — slice 6a).
+- Transition the linked problem's status (that is `/wr-itil:transition-problem P<NNN> <status>`).
+- Rename a `.investigating.md` or `.mitigating.md` file — the incident must already be `.restored.md`.
+- Prompt the user for decisions — the gate is a hard check with a message, never a prompt. If a decisional branch is needed (e.g. "close anyway without a linked problem"), the user edits the incident file to add a No Problem section and re-runs.
+
+If the user wants any of the above, the skill reports the appropriate sibling and exits.
+
+## Related
+
+- **the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem** (`docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md`) — originating ticket. This skill is slice 6c of the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem phased-landing plan.
+- **the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule 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.
+- **the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule** (`docs/decisions/011-manage-incident-skill.proposed.md`) — incident lifecycle file-suffix conventions (`.investigating.md` / `.mitigating.md` / `.restored.md` / `.closed.md`) + close-gate-on-linked-problem rule.
+- **the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule** (`docs/decisions/022-problem-lifecycle-verification-pending-status.proposed.md`) — `.verifying.md` status; extends the close gate to accept `.verifying.md` alongside `.known-error.md` and `.closed.md`.
+- **the "Structured User Interaction for Governance-Skill Decisions" architecture rule** Rule 1 — structured user interaction (forwarder emits systemMessage for deprecation notice; gate-blocks are hard-fail messages, not prompts).
+- **the "Structured User Interaction for Governance-Skill Decisions" architecture rule** Rule 6 — policy-within-appetite non-interactive actions (release drain).
+- **the "Governance Skills Commit Their Own Completed Work" architecture rule** — governance skills commit their own work.
+- **the "On-Demand Assessment Skills for Governance Plugins" architecture rule** — release scorer delegation pattern.
+- **the "Governance skills auto-release when changesets are queued" architecture rule** — auto-release when changesets are queued.
+- **the "Skill testing strategy — contract-assertion bats companion to" architecture rule** (`docs/decisions/037-skill-testing-strategy.proposed.md`) — contract-assertion bats pattern applied to this skill.
+- **the ": Enforce Governance Without Slowing Down" user outcome** (`docs/jtbd/developer/the ": Enforce Governance Without Slowing Down" user outcome-enforce-governance.proposed.md`) — discoverable surface via `/wr-itil:` autocomplete.
+- **the "Extend the Suite with New Plugins" user outcome** (`docs/jtbd/plugin-developer/the "Extend the Suite with New Plugins" user outcome-extend-suite.proposed.md`) — one skill per distinct user intent.
+- **the "Restore Service Fast with an Audit Trail" user outcome** (`docs/jtbd/tech-lead/the "Restore Service Fast with an Audit Trail" user outcome-restore-service-fast.proposed.md`) — close gate preserves the problem-handoff audit trail.
+- `<itil-plugin-root>/skills/manage-incident/SKILL.md` — hosts the thin-router forwarder for the deprecated `manage-incident <I###> close` form.
+- `<itil-plugin-root>/skills/restore-incident/SKILL.md` — slice 6b precedent; close-incident is the next transition after restore.
+- `<itil-plugin-root>/skills/transition-problem/SKILL.md` — the skill used to advance a linked problem from `.open.md` to `.known-error.md` so the incident close gate can pass.
+
+$ARGUMENTS

package/skills-codex/close-incident/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "WR ITIL: Close Incident"
+  short_description: "Close a restored incident after its problem gate passes."

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

@@ -0,0 +1,173 @@
+---
+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.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+<!-- Generated from the runtime-neutral skill source. Do not edit. -->
+
+> Codex runtime note: use `request_user_input` only where this contract
+> explicitly requires a human decision. Resolve `<itil-plugin-root>` from
+> this installed `SKILL.md`: it is two directories above the skill
+> directory. Run bundled commands from `<itil-plugin-root>/bin/`; do not
+> search the adopter repository or rely on those commands being on `PATH`.
+> Spawn `wr-itil:hang-off-check` with the native Codex subagent tool, wait
+> for it, and close that same agent.
+
+
+# Link Incident
+
+Attach an existing problem record to an incident. This is the standalone link operation — the `/wr-itil:restore-incident` skill already handles the link-at-restore flow (writing the `## Linked Problem` section as part of problem-handoff). The `link-incident` skill is for after-the-fact links: when an incident was closed with a `## No Problem` note that later turned out to be wrong, when multiple incidents share a newly-created problem and need to be linked, or when a problem existed in parallel but was not attached during restore.
+
+This skill is the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem phased-landing split of `/wr-itil:manage-incident <I> link P<M>` per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended Skill Granularity rule: one skill per distinct user intent. The arguments `<I>` (incident ID) and `<P>` (problem ID) are data parameters, permitted under the amendment. The original `/wr-itil:manage-incident <I> link P<M>` subcommand route remains as a thin-router forwarder during the deprecation window but is scheduled for removal in `@windyroad/itil`'s next major version.
+
+## Arguments
+
+`/wr-itil:link-incident <I###> P<MMM>` — two positional data parameters:
+
+- `<I###>` — the incident ID (e.g. `I007` or bare `007`). Resolves to `docs/incidents/<I###>-*.{investigating,mitigating,restored,closed}.md`.
+- `P<MMM>` — the problem ID (e.g. `the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem` or bare `071`). Resolves to `docs/problems/<MMM>-*.md` (any lifecycle suffix).
+
+If either argument is missing or malformed, report the expected shape and exit. No request_user_input — both are data parameters, not decisional branches.
+
+## Steps
+
+### 1. Parse arguments
+
+Extract `<I###>` and `P<MMM>` from `$ARGUMENTS`. Normalise:
+
+- Accept `I007`, `i007`, `007`, `7` → canonicalise the incident ID to `I007`.
+- Accept `the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem`, `p071`, `071`, `71` → canonicalise the problem ID to `the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem`.
+- If either is missing, report "Usage: `/wr-itil:link-incident <I###> P<MMM>`" and exit.
+
+### 2. Locate the incident file
+
+```bash
+ls docs/incidents/<I###>-*.md 2>/dev/null | head -1
+```
+
+The link operation works on any incident status — investigating, mitigating, restored, or closed. (Closed incidents are rare to link retroactively but not impossible — the audit-trail requirement is preserved either way.)
+
+- If no file matches, report "No incident `<I###>` found. Check `/wr-itil:list-incidents` for active incidents or search `docs/incidents/` for closed incidents." and exit.
+- If multiple files match (should not happen under the naming convention), report the ambiguity and exit.
+
+### 3. Locate the problem file
+
+Dual-tolerant lookup spans flat layout AND per-state subdir layout (the ": docs/problems/ flat layout migration — per-state subdirs + adopter auto-migration" release design migration window):
+
+```bash
+ls docs/problems/<MMM>-*.md docs/problems/*/<MMM>-*.md 2>/dev/null | head -1
+```
+
+Accept any lifecycle suffix: `.open.md`, `.known-error.md`, `.verifying.md`, `.closed.md` in flat layout; bare `<MMM>-<title>.md` under `docs/problems/<state>/` in per-state layout.
+
+- If no file matches, report "No problem `P<MMM>` found. Check `/wr-itil:list-problems` for the current backlog." and exit.
+- Read the problem file's title from the `# Problem <MMM>: <Title>` header line.
+- Read the problem file's status from the filename suffix (Open / Known Error / Verifying / Closed).
+
+### 4. Write or update the Linked Problem section
+
+Construct the link entry:
+
+```markdown
+## Linked Problem
+P<MMM> (<title>) — <status>
+```
+
+where `<status>` is the human-readable label derived from the file suffix (`Open`, `Known Error`, `Verifying`, `Closed`).
+
+Branch on whether the incident already has a link:
+
+**Case A — no `## Linked Problem` or `## No Problem` section present**:
+
+Append the `## Linked Problem` section at the end of the incident file.
+
+**Case B — `## Linked Problem` section already present**:
+
+Replace the existing section's body with the new link entry. Keep the `## Linked Problem` heading. If the existing link matches exactly (same `P<MMM>`, same title, same status), report "Incident `<I###>` is already linked to `P<MMM>` with the same status — no change." and exit without modifying the file.
+
+**Case C — `## No Problem` section present**:
+
+This is a retroactive-link-after-no-problem case. Replace the `## No Problem` section with a `## Linked Problem` section carrying the new link entry. Also append a `[<timestamp> UTC] Retroactive link to P<MMM>` entry to the `## Timeline` section so the audit trail records the revision.
+
+### 5. Quality checks
+
+After the link, verify:
+
+- Exactly one of `## Linked Problem` or `## No Problem` exists on the incident file (never both, never neither).
+- The `## Linked Problem` body matches the canonical shape `P<MMM> (<title>) — <status>`.
+- The problem file referenced actually exists in `docs/problems/`.
+
+### 6. Report
+
+Report:
+
+- The incident ID and file path modified.
+- The problem ID, title, and status linked.
+- Whether the link was a new attach (Case A), an update (Case B), or a retroactive conversion from No Problem (Case C).
+- Any quality-check warnings.
+
+### 7. Commit the completed work (the "Governance Skills Commit Their Own Completed Work" architecture rule)
+
+Per the "Governance Skills Commit Their Own Completed Work" architecture rule, governance skills commit their own work.
+
+1. `git add` the modified incident file.
+2. Delegate to `wr-risk-scorer:pipeline` (subagent_type: `wr-risk-scorer:pipeline`) to assess the staged changes and create a bypass marker. If the subagent type is not available (spawned subagent surface), invoke `/wr-risk-scorer:assess-release` via the installed skill invocation instead — per the "On-Demand Assessment Skills for Governance Plugins" architecture rule it wraps the same pipeline subagent.
+3. `git commit -m "docs(incidents): link I<NNN> to P<MMM>"`.
+4. If risk is above appetite: report the above-appetite state clearly and exit without committing. The user can re-run the commit manually if they choose.
+
+### 8. Auto-release when changesets are queued (the "Governance skills auto-release when changesets are queued" architecture rule)
+
+**Skip this step if the skill is running inside an AFK orchestrator.** Orchestrators handle release cadence themselves per the "Inter-iteration release cadence for AFK loops" architecture rule (Step 6.5). When in doubt, defer to the orchestrator by skipping this step.
+
+Otherwise, after the commit in step 7 lands, drain the release queue so the link lands on npm without requiring manual user action.
+
+**Mechanism — delegate, do not re-implement scoring (per the "On-Demand Assessment Skills for Governance Plugins" architecture rule):**
+
+1. Invoke the release scorer. Two paths are valid:
+   - **Primary**: delegate to subagent type `wr-risk-scorer:pipeline` via the native Codex subagent tool.
+   - **Fallback**: if that subagent type is not available, invoke skill `/wr-risk-scorer:assess-release` via the installed skill invocation.
+2. Read the returned `RISK_SCORES: commit=X push=Y release=Z` line.
+3. **Drain condition**: if `push` and `release` are both within appetite (≤ 4/25, "Low" band per `RISK-POLICY.md`), AND `.changeset/` is non-empty, proceed to the drain action. Otherwise, skip the drain and report the unreleased state.
+
+**Drain action (non-interactive, policy-authorised per the "Structured User Interaction for Governance-Skill Decisions" architecture rule Rule 6):**
+
+1. Run `npm run push:watch` (push + wait for CI to pass).
+2. If `.changeset/` remains non-empty after push (i.e. a release PR is pending), run `npm run release:watch` (merge the release PR + wait for npm publish).
+3. Report the release: "Released <package>@<version>. Link record is now live on npm."
+
+**Failure handling**: if `release:watch` fails (CI failure, publish failure), stop and report the failure clearly. Do not retry non-interactively — the user must intervene.
+
+**Above-appetite branch**: if push/release risk is above appetite, skip the drain and report: "Release skipped — risk above appetite. Run `npm run push:watch` and `npm run release:watch` manually when ready."
+
+## Ownership boundary
+
+`link-incident` writes (or updates) the `## Linked Problem` section on an incident file and, in Case C only, appends a retroactive-link Timeline entry. It does NOT:
+
+- Create a new problem (that is `/wr-itil:manage-problem` with no args).
+- Update the problem's body (that is `/wr-itil:manage-problem P<MMM>`).
+- Transition the problem's status (that is `/wr-itil:transition-problem P<MMM> <status>`).
+- Transition the incident's status (that is `/wr-itil:restore-incident` or `/wr-itil:close-incident`).
+- Record a mitigation (that is `/wr-itil:mitigate-incident`).
+- Prompt the user for decisions — both arguments are data parameters; any missing-argument case is a hard-fail message, not a decisional branch.
+
+If the user wants any of the above, the skill reports the appropriate sibling and exits.
+
+## Related
+
+- **the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem** (`docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md`) — originating ticket. This skill is slice 6d of the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem phased-landing plan.
+- **the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule 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.
+- **the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule** (`docs/decisions/011-manage-incident-skill.proposed.md`) — incident lifecycle file-suffix conventions + Linked Problem section convention.
+- **the "Structured User Interaction for Governance-Skill Decisions" architecture rule** Rule 1 — structured user interaction (forwarder emits systemMessage for deprecation; missing-argument is a hard-fail message, not a prompt).
+- **the "Governance Skills Commit Their Own Completed Work" architecture rule** — governance skills commit their own work.
+- **the "On-Demand Assessment Skills for Governance Plugins" architecture rule** — release scorer delegation pattern.
+- **the "Governance skills auto-release when changesets are queued" architecture rule** — auto-release when changesets are queued.
+- **the "Skill testing strategy — contract-assertion bats companion to" architecture rule** (`docs/decisions/037-skill-testing-strategy.proposed.md`) — contract-assertion bats pattern applied to this skill.
+- **the ": Enforce Governance Without Slowing Down" user outcome** (`docs/jtbd/developer/the ": Enforce Governance Without Slowing Down" user outcome-enforce-governance.proposed.md`) — discoverable surface via `/wr-itil:` autocomplete.
+- **the "Extend the Suite with New Plugins" user outcome** (`docs/jtbd/plugin-developer/the "Extend the Suite with New Plugins" user outcome-extend-suite.proposed.md`) — one skill per distinct user intent.
+- **the "Restore Service Fast with an Audit Trail" user outcome** (`docs/jtbd/tech-lead/the "Restore Service Fast with an Audit Trail" user outcome-restore-service-fast.proposed.md`) — Linked Problem traceability preserved post-split.
+- `<itil-plugin-root>/skills/manage-incident/SKILL.md` — hosts the thin-router forwarder for the deprecated `manage-incident <I###> link P<MMM>` form.
+- `<itil-plugin-root>/skills/restore-incident/SKILL.md` — slice 6b precedent; writes the `## Linked Problem` section as part of problem-handoff. `link-incident` is the standalone-after-the-fact equivalent.
+- `<itil-plugin-root>/skills/manage-problem/SKILL.md` — the source of truth for problem titles / statuses read during link.
+
+$ARGUMENTS

package/skills-codex/link-incident/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "WR ITIL: Link Incident"
+  short_description: "Link an incident to an existing problem."

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

@@ -0,0 +1,92 @@
+---
+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
+---
+
+<!-- Generated from the runtime-neutral skill source. Do not edit. -->
+
+> Codex runtime note: use `request_user_input` only where this contract
+> explicitly requires a human decision. Resolve `<itil-plugin-root>` from
+> this installed `SKILL.md`: it is two directories above the skill
+> directory. Run bundled commands from `<itil-plugin-root>/bin/`; do not
+> search the adopter repository or rely on those commands being on `PATH`.
+> Spawn `wr-itil:hang-off-check` with the native Codex subagent tool, wait
+> for it, and close that same agent.
+
+
+# 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 "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem phased-landing split of `/wr-itil:manage-incident list` per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule 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 the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule: 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
+
+- **the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem** (`docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md`) — originating ticket. This skill is slice 5 of the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem phased-landing plan.
+- **the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule 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.
+- **the "Add `manage-incident` Skill to `wr-itil` Plugin" architecture rule** (`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.
+- **the "Skill testing strategy — contract-assertion bats companion to" architecture rule** (`docs/decisions/037-skill-testing-strategy.proposed.md`) — contract-assertion bats pattern applied to this skill.
+- **the ": Enforce Governance Without Slowing Down" user outcome** (`docs/jtbd/developer/the ": Enforce Governance Without Slowing Down" user outcome-enforce-governance.proposed.md`) — discoverable surface via `/wr-itil:` autocomplete.
+- **the "Extend the Suite with New Plugins" user outcome** (`docs/jtbd/plugin-developer/the "Extend the Suite with New Plugins" user outcome-extend-suite.proposed.md`) — one skill per distinct user intent.
+- **the "Restore Service Fast with an Audit Trail" user outcome** (`docs/jtbd/tech-lead/the "Restore Service Fast with an Audit Trail" user outcome-restore-service-fast.proposed.md`) — incident status visibility for audit trail.
+- `<itil-plugin-root>/skills/manage-incident/SKILL.md` — hosts the thin-router forwarder for the deprecated `manage-incident list` form.
+- `<itil-plugin-root>/skills/list-problems/SKILL.md` — slice 1 precedent; this skill mirrors its read-only display shape.
+
+$ARGUMENTS

package/skills-codex/list-incidents/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "WR ITIL: List Incidents"
+  short_description: "List active incidents in lifecycle order."

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

@@ -0,0 +1,126 @@
+---
+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.
+allowed-tools: Read, Bash, Grep, Glob
+---
+
+<!-- Generated from the runtime-neutral skill source. Do not edit. -->
+
+> Codex runtime note: use `request_user_input` only where this contract
+> explicitly requires a human decision. Resolve `<itil-plugin-root>` from
+> this installed `SKILL.md`: it is two directories above the skill
+> directory. Run bundled commands from `<itil-plugin-root>/bin/`; do not
+> search the adopter repository or rely on those commands being on `PATH`.
+> Spawn `wr-itil:hang-off-check` with the native Codex subagent tool, wait
+> for it, and close that same agent.
+
+
+# List Problems
+
+Display the current problem backlog — open and known-error tickets — sorted by Weighted Shortest Job First (WSJF) priority. This skill is a pure read-only view of `docs/problems/`; it does not edit, transition, close, or create tickets. For those operations, use the dedicated skills (`/wr-itil:manage-problem`, `/wr-itil:transition-problem`, etc.).
+
+This skill is the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem phased-landing split of `/wr-itil:manage-problem list` per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended Skill Granularity rule: one skill per distinct user intent. The original `/wr-itil:manage-problem 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 (the ": docs/problems/ flat layout migration — per-state subdirs + adopter auto-migration" release design migration window — each glob is dual-tolerant, covering BOTH the flat `docs/problems/<NNN>-<title>.<state>.md` filename-suffix layout AND the per-state subdir `docs/problems/<state>/<NNN>-<title>.md` layout):
+
+- `docs/problems/*.open.md` + `docs/problems/open/*.md` — open tickets (under investigation)
+- `docs/problems/*.known-error.md` + `docs/problems/known-error/*.md` — known errors (root cause confirmed, fix NOT yet released)
+
+Shown in separate sections, excluded from the dev-work WSJF ranking per the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule:
+- `docs/problems/*.verifying.md` + `docs/problems/verifying/*.md` — Verification Pending (fix released, awaiting user verification; WSJF multiplier 0)
+- `docs/problems/*.parked.md` + `docs/problems/parked/*.md` — Parked on upstream or user-suspended (WSJF multiplier 0)
+
+`docs/problems/*.closed.md` + `docs/problems/closed/*.md` is omitted entirely (the view is of active backlog, not the closed archive).
+
+## Steps
+
+### 1. Check README.md cache freshness
+
+Reuse the same `git log`-based freshness test as `/wr-itil:manage-problem review` Step 9 (per the "Problem 031: `manage-problem work` incorrectly determines cache is fresh" problem — filesystem mtime is unreliable in worktrees and fresh checkouts, so git history is the authoritative staleness signal):
+
+```bash
+readme_commit=$(git log -1 --format=%H -- docs/problems/README.md 2>/dev/null)
+if [ -z "$readme_commit" ] || \
+   git log --oneline "${readme_commit}..HEAD" -- 'docs/problems/*.md' 'docs/problems/*/*.md' ':!docs/problems/README.md' 2>/dev/null | grep -q .; then
+  # Pathspec pair `'docs/problems/*.md' 'docs/problems/*/*.md'` is the
+  # the ": docs/problems/ flat layout migration — per-state subdirs + adopter auto-migration" release design dual-tolerant transitional shape — covers BOTH the flat
+  # layout AND the per-state subdir layout.
+  echo "stale"
+fi
+```
+
+**Cache fresh** (no output): read `docs/problems/README.md` directly — it already contains the ranked table from the last review. Display the WSJF Rankings section + Verification Queue section + Parked section as-is. Note in the output: "Using cached ranking from [timestamp in README.md]".
+
+**Cache stale** (prints "stale") or `README.md` missing: run the live scan in Step 2.
+
+### 2. Live scan (cache-stale fallback)
+
+Enumerate the backlog files via dual-tolerant globs (the ": docs/problems/ flat layout migration — per-state subdirs + adopter auto-migration" release design migration window — each line covers BOTH the flat `<NNN>-<title>.<state>.md` filename-suffix layout AND the per-state subdir `<state>/<NNN>-<title>.md` layout):
+
+```bash
+ls docs/problems/*.open.md docs/problems/*.known-error.md docs/problems/open/*.md docs/problems/known-error/*.md 2>/dev/null
+ls docs/problems/*.verifying.md docs/problems/verifying/*.md 2>/dev/null  # for Verification Queue section
+ls docs/problems/*.parked.md docs/problems/parked/*.md 2>/dev/null        # for Parked section
+```
+
+For each `.open.md` and `.known-error.md` file, read the `**Status**`, `**Priority**`, `**Effort**`, and `**WSJF**` lines from the frontmatter section. Compute WSJF if missing: `WSJF = (Severity × StatusMultiplier) / EffortDivisor` per `/wr-itil:manage-problem` WSJF Prioritisation. Default to M (divisor 2) when Effort is absent; flag missing scores so the user knows a review is overdue.
+
+For each `.verifying.md` file, read the `## Fix Released` marker. The `Likely verified?` column carries an **evidence-first** cell per the "VQ `Likely verified?` column uses age-based heuristic (≥14 days = yes) instead of session-observed evidence — sibling proxy-for-evidence anti-pattern to" problem (supersedes the original the "Problem 048: manage-problem does not surface Fix Released problems as verification candidates when the fix path has been exercised" problem Candidate 4 14-day heuristic). <!-- LIKELY-VERIFIED-CELL-SHAPE: evidence-based per the "VQ `Likely verified?` column uses age-based heuristic (≥14 days = yes) instead of session-observed evidence — sibling proxy-for-evidence anti-pattern to" problem --> When this skill runs against a stale cache, the live-scan path reads the cell value from the `.verifying.md` ticket's `## Fix Released` section (or carries forward the prior cell value from the cached README when present); it does NOT compute the cell from age — that responsibility moved to `/wr-itil:review-problems` Step 4 (user confirmation populates `yes — observed: …`) and `run-retro` Step 4a close-on-evidence citations.
+
+### 3. Display
+
+Render three sections matching the README.md format so cached and live output look identical:
+
+**WSJF Rankings** — dev-work queue (open + known-error), sorted by WSJF descending:
+
+```
+| WSJF | ID | Title | Severity | Status | Effort |
+|------|-----|-------|----------|--------|--------|
+| <score> | P<NNN> | <title> | <severity> | <status> | <effort> |
+```
+
+**Verification Queue** — `.verifying.md` tickets, sorted by `Released date ASC` (oldest at row 1; same-day releases tiebreak by ID ASC) per the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule + the "Problem 048: manage-problem does not surface Fix Released problems as verification candidates when the fix path has been exercised" problem user-task semantics. <!-- VQ-SORT-DIRECTION: oldest-first per the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule --> Drift here re-opens the "docs/problems/README.md Verification Queue rendered newest-first contradicts section header "Ranked by release age, oldest first"" problem. The `Likely verified?` column carries an **evidence-first** cell per the "VQ `Likely verified?` column uses age-based heuristic (≥14 days = yes) instead of session-observed evidence — sibling proxy-for-evidence anti-pattern to" problem — three canonical values: `yes — observed: <evidence>`, `no — not observed` (default for newly-released tickets), `no — observed regression`. <!-- LIKELY-VERIFIED-CELL-SHAPE: evidence-based per the "VQ `Likely verified?` column uses age-based heuristic (≥14 days = yes) instead of session-observed evidence — sibling proxy-for-evidence anti-pattern to" problem --> Drift on the cell shape re-opens the "VQ `Likely verified?` column uses age-based heuristic (≥14 days = yes) instead of session-observed evidence — sibling proxy-for-evidence anti-pattern to" problem.
+
+```
+| ID | Title | Released | Likely verified? |
+|----|-------|----------|------------------|
+| P<NNN> | <title> | <release marker> | <yes — observed: …  /  no — not observed  /  no — observed regression> |
+```
+
+**Parked** — `.parked.md` tickets:
+
+```
+| ID | Title | Reason | Parked since |
+|----|-------|--------|-------------|
+| P<NNN> | <title> | <reason> | <date> |
+```
+
+If a section is empty, omit it rather than rendering an empty header.
+
+### 4. Trailing suggestions
+
+After the tables, print one of two short pointers depending on what the output showed:
+
+- When dev-work queue is non-empty: `Run /wr-itil:work-problem to work the highest-WSJF ticket, or /wr-itil:manage-problem <NNN> to update a specific ticket.` (Note: `/wr-itil:work-problem` is singular — distinct from `/wr-itil:work-problems` plural AFK orchestrator.)
+- When Verification Queue is non-empty: `Run /wr-itil:manage-problem review to trigger the verification prompt for pending tickets.`
+
+## Ownership boundary
+
+`list-problems` does not modify, rename, or commit any files. If the README.md cache is stale, `list-problems` performs a live scan but does NOT rewrite `README.md` — refreshing the cache is `/wr-itil:manage-problem review`'s ownership. The trailing-suggestion pointer surfaces this boundary so the user can refresh via the correct skill when they notice stale output.
+
+## Related
+
+- **the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem** (`docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md`) — originating ticket. This skill is phase 1 of the "Problem 071: Argument-based skill subcommands are not discoverable in Codex autocomplete" problem phased-landing plan.
+- **the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule 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.
+- **the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule** (`docs/decisions/022-verification-pending-status.proposed.md`) — Verification Pending status conventions; `.verifying.md` exclusion from WSJF ranking.
+- **the "Skill testing strategy — contract-assertion bats companion to" architecture rule** (`docs/decisions/037-skill-testing-strategy.proposed.md`) — contract-assertion bats pattern applied to this skill.
+- **the "Problem 031: `manage-problem work` incorrectly determines cache is fresh" problem** — git-history freshness check rationale (mtime unreliable in worktrees).
+- **the "Problem 048: manage-problem does not surface Fix Released problems as verification candidates when the fix path has been exercised" problem** Candidate 4 — original `Likely verified?` column (14-day age-heuristic). Superseded by the "VQ `Likely verified?` column uses age-based heuristic (≥14 days = yes) instead of session-observed evidence — sibling proxy-for-evidence anti-pattern to" problem.
+- **the "VQ `Likely verified?` column uses age-based heuristic (≥14 days = yes) instead of session-observed evidence — sibling proxy-for-evidence anti-pattern to" problem** — evidence-first cell shape (`yes — observed: <evidence>` / `no — not observed` / `no — observed regression`) replaces the age-based heuristic; `<!-- LIKELY-VERIFIED-CELL-SHAPE: evidence-based per the "VQ `Likely verified?` column uses age-based heuristic (≥14 days = yes) instead of session-observed evidence — sibling proxy-for-evidence anti-pattern to" problem -->` drives cross-skill drift detection.
+- **the ": Enforce Governance Without Slowing Down" user outcome** (`docs/jtbd/developer/the ": Enforce Governance Without Slowing Down" user outcome-enforce-governance.proposed.md`) — discoverable surface via `/wr-itil:` autocomplete.
+- **the "Extend the Suite with New Plugins" user outcome** (`docs/jtbd/plugin-developer/the "Extend the Suite with New Plugins" user outcome-extend-suite.proposed.md`) — one skill per distinct user intent.
+- `<itil-plugin-root>/skills/manage-problem/SKILL.md` — hosts the thin-router forwarder for the deprecated `manage-problem list` form.
+
+$ARGUMENTS

package/skills-codex/list-problems/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "WR ITIL: List Problems"
+  short_description: "List open problems in WSJF order."