@windyroad/itil 0.9.0 → 0.10.0-preview.144

package/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "wr-itil",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "description": "ITIL-aligned IT service management for Claude Code"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/itil",
-  "version": "0.9.0",
+  "version": "0.10.0-preview.144",
   "description": "ITIL-aligned IT service management for Claude Code (problem, and future incident/change skills)",
   "bin": {
     "windyroad-itil": "./bin/install.mjs"

package/skills/list-problems/SKILL.md

@@ -0,0 +1,110 @@
+---
+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
+---
+
+# 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 P071 phased-landing split of `/wr-itil:manage-problem list` per ADR-010 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:
+- `docs/problems/*.open.md` — open tickets (under investigation)
+- `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 ADR-022:
+- `docs/problems/*.verifying.md` — Verification Pending (fix released, awaiting user verification; WSJF multiplier 0)
+- `docs/problems/*.parked.md` — Parked on upstream or user-suspended (WSJF multiplier 0)
+
+`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 P031 — 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/README.md' 2>/dev/null | grep -q .; then
+  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 glob:
+
+```bash
+ls docs/problems/*.open.md docs/problems/*.known-error.md 2>/dev/null
+ls docs/problems/*.verifying.md 2>/dev/null  # for Verification Queue section
+ls 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 and extract the release age for the `Likely verified?` column per P048 Candidate 4 (within-skill default: 14 days = `yes`).
+
+### 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 release age (oldest first):
+
+```
+| ID | Title | Released | Likely verified? |
+|----|-------|----------|------------------|
+| P<NNN> | <title> | <release marker> | yes (N days) / no (N days) |
+```
+
+**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
+
+- **P071** (`docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md`) — originating ticket. This skill is phase 1 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-022** (`docs/decisions/022-verification-pending-status.proposed.md`) — Verification Pending status conventions; `.verifying.md` exclusion from WSJF ranking.
+- **ADR-037** (`docs/decisions/037-skill-testing-strategy.proposed.md`) — contract-assertion bats pattern applied to this skill.
+- **P031** — git-history freshness check rationale (mtime unreliable in worktrees).
+- **P048** Candidate 4 — the 14-day `Likely verified?` heuristic.
+- **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.
+- `packages/itil/skills/manage-problem/SKILL.md` — hosts the thin-router forwarder for the deprecated `manage-problem list` form.
+
+$ARGUMENTS

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

@@ -0,0 +1,100 @@
+#!/usr/bin/env bats
+# Contract assertions for /wr-itil:list-problems (P071 split slice 1).
+#
+# This skill hosts the "list open and known-error problems" user intent
+# previously hidden behind /wr-itil:manage-problem 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)
+#
+# 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-022 — Verification Pending status conventions (list-problems respects `.verifying.md` exclusion)
+#   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-problems (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-problems$" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md frontmatter description names the list intent (P071)" {
+  # Description must name "list" and "problem" so Claude Code autocomplete
+  # surfaces the user intent rather than a generic name.
+  run grep -inE "^description:.*list.*problem|^description:.*problem.*list" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md frontmatter allowed-tools is read-only (P071 + architect Q3)" {
+  # Architect Q3: pure read-only list display. 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)" {
+  # The skill reads .open.md and .known-error.md files from docs/problems/.
+  # .verifying.md and .parked.md are excluded from the dev-work ranking per
+  # ADR-022 (Verification Pending) and the Parked-policy; but they MAY be
+  # shown in dedicated sections. The SKILL.md must name both `.open.md` and
+  # `.known-error.md` glob patterns explicitly so the contract is legible.
+  run grep -inE "\.open\.md" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+  run grep -inE "\.known-error\.md" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "SKILL.md reuses the git-log freshness check from manage-problem review (P071 + architect Q4)" {
+  # Architect Q4: reuse the git-log freshness check from manage-problem
+  # review (same skill suite, same cache semantics per P031).
+  run grep -inE "git log.*README\.md|readme_commit|git log -1 --format=%H" "$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)" {
+  # Architect advisory: list-problems 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-problems 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 "work"` / etc. patterns.
+  run grep -inE "If arguments start with|If arguments contain" "$SKILL_FILE"
+  [ "$status" -ne 0 ]
+}

package/skills/manage-problem/SKILL.md

@@ -1,7 +1,8 @@
 ---
 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.
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill
+deprecated-arguments: true
 ---
 
 # Problem Management Skill
@@ -125,11 +126,25 @@ What "work" means depends on the problem's status:
 
 Determine the operation from `$ARGUMENTS`:
 - If arguments start with a number (e.g., "011"), this is an update or transition
-- If arguments contain "list", show a summary of all open problems
+- If arguments contain "list", **delegate to `/wr-itil:list-problems`** via the Skill tool. See "Deprecated-argument forwarders" below.
 - If arguments contain "work", run a **review** first (step 9), then begin working the highest-WSJF problem
 - If arguments contain "review", run the review (step 9) only
 - Otherwise, this is a new problem creation
 
+#### 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 1 — new skill `/wr-itil:list-problems`):
+
+When `$ARGUMENTS` contains the word `list` as a top-level argument (not inside a ticket body edit), delegate to `/wr-itil:list-problems` via the Skill tool and emit this systemMessage verbatim:
+
+> `/wr-itil:manage-problem list is deprecated; use /wr-itil:list-problems 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-problems` and returns the new skill's output verbatim. Duplicating the logic would harden the deprecation window into a permanent fork.
+
+Forwarders for `work`, `review`, `<NNN> known-error`, and `<NNN> close` land in subsequent P071 phased-landing slices (see P071 ticket's "Split proposal" section for the full plan). Until those slices land, the corresponding Step-2+ branches continue to execute inline.
+
 ### 2. For new problems: Check for duplicates FIRST
 
 Before creating, search existing problems for similar issues. The user may not know a problem already exists.

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

@@ -0,0 +1,66 @@
+#!/usr/bin/env bats
+# Contract assertions for manage-problem's `list` subcommand forwarder (P071 split slice 1).
+#
+# Per ADR-010 amended (Skill Granularity section) + P071 phased plan:
+# `/wr-itil:manage-problem list` delegates to the new `/wr-itil:list-problems`
+# 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)
+#
+# 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-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-problem 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-problem Step 1 forwards 'list' argument to /wr-itil:list-problems (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-problems" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-problem 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-problems|deprecated.*list-problems|removed in .* next major version" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}
+
+@test "manage-problem 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-problems reference.
+  run grep -inE "delegate.*list-problems|Skill tool.*list-problems|list-problems.*Skill tool" "$SKILL_FILE"
+  [ "$status" -eq 0 ]
+}