@windyroad/itil 1.2.0 → 2.0.0-preview.1111

package/skills/transition-problems/SKILL.md

@@ -1,27 +1,27 @@
 ---
 name: wr-itil:transition-problems
-description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, P057 re-stage, P063 external-root-cause detection, P062 README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per ADR-014 batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
+description: "Batch-advance multiple problem tickets through the lifecycle in one invocation — Open → Known Error, Known Error → Verification Pending, Verification Pending → Closed. Loops the per-ticket /wr-itil:transition-problem mechanic (rename, Status edit, the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem re-stage, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection, the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem README refresh) without paying N× SKILL.md reload latency or violating split-skill execution ownership. Produces ONE shared commit covering all surviving transitions per the "Governance Skills Commit Their Own Completed Work" architecture rule batch-grain. Use when closing the Verification Queue at the end of a `/wr-retrospective:run-retro` Step 4a pass, batch-closing release-aged verifyings during `/wr-itil:work-problems` AFK orchestration, or confirming multiple Step 9d verifications in `/wr-itil:manage-problem review`. Singular sibling — `/wr-itil:transition-problem` (one ticket per invocation)."
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Skill, Agent
 ---
 
 # Transition Problems — Batch Lifecycle Advance
 
-Advance multiple problem tickets along the ITIL lifecycle in one invocation. The skill is the **batch executor** for the user-initiated transition path — it accepts a list of `<NNN> <status>` pairs, runs each pair's per-ticket mechanic inline (pre-flight checks, P063 external-root-cause detection, `git mv` + Status edit + P057 re-stage, `## Fix Released` for the `verifying` destination), refreshes `docs/problems/README.md` ONCE at the end (P062 at batch grain), and commits all surviving transitions in ONE commit per ADR-014.
+Advance multiple problem tickets along the ITIL lifecycle in one invocation. The skill is the **batch executor** for the user-initiated transition path — it accepts a list of `<NNN> <status>` pairs, runs each pair's per-ticket mechanic inline (pre-flight checks, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection, `git mv` + Status edit + the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem re-stage, `## Fix Released` for the `verifying` destination), refreshes `docs/problems/README.md` ONCE at the end (the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem at batch grain), and commits all surviving transitions in ONE commit per the "Governance Skills Commit Their Own Completed Work" architecture rule.
 
-This skill is the plural sibling of `/wr-itil:transition-problem`, mirroring the P071 singular/plural split precedent established by `/wr-itil:work-problem` (singular) and `/wr-itil:work-problems` (plural). Per ADR-010 amended Skill Granularity rule, batch-transition is a distinct user intent from single-transition (different ergonomics, different commit grain, different cost profile) and therefore lives on its own skill surface.
+This skill is the plural sibling of `/wr-itil:transition-problem`, mirroring the "Problem 071: Argument-based skill subcommands are not discoverable in Claude Code autocomplete" problem singular/plural split precedent established by `/wr-itil:work-problem` (singular) and `/wr-itil:work-problems` (plural). Per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended Skill Granularity rule, batch-transition is a distinct user intent from single-transition (different ergonomics, different commit grain, different cost profile) and therefore lives on its own skill surface.
 
-## Why this skill exists (P117)
+## Why this skill exists (the "No batch-transition surface for multiple problem tickets in a single run-retro / review cycle" problem)
 
-Closing N tickets via the singular skill costs N× SKILL.md reload into the caller's context every time the singular is invoked from a batch caller (run-retro Step 4a, manage-problem review Step 9d, work-problems release-batched closures). This is the very SKILL.md-runtime-size pressure P097 captures, and the inline-batch workaround documented in P117 (running `git mv` + Edit + commit outside the singular skill's authoritative-executor scope) violates the ADR-010 amended ownership boundary.
+Closing N tickets via the singular skill costs N× SKILL.md reload into the caller's context every time the singular is invoked from a batch caller (run-retro Step 4a, manage-problem review Step 9d, work-problems release-batched closures). This is the very SKILL.md-runtime-size pressure the "Problem 097: SKILL.md files mix runtime-necessary steps with maintainer-facing rationale, bloating every skill invocation" problem captures, and the inline-batch workaround documented in the "No batch-transition surface for multiple problem tickets in a single run-retro / review cycle" problem (running `git mv` + Edit + commit outside the singular skill's authoritative-executor scope) violates the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended ownership boundary.
 
-The plural surface eliminates both costs: ONE SKILL.md load (this file), N pair iterations in-band, ONE commit at the end. Per ADR-010 amended "Split-skill execution ownership", the plural carries an inline scoped copy of the singular's per-ticket mechanic ("copy, not move") rather than re-invoking the singular via the Skill tool — Skill-tool re-invocation N times would reintroduce the very N× reload cost the ticket targets.
+The plural surface eliminates both costs: ONE SKILL.md load (this file), N pair iterations in-band, ONE commit at the end. Per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended "Split-skill execution ownership", the plural carries an inline scoped copy of the singular's per-ticket mechanic ("copy, not move") rather than re-invoking the singular via the Skill tool — Skill-tool re-invocation N times would reintroduce the very N× reload cost the ticket targets.
 
 ## Name distinction (transition-problem vs transition-problems)
 
-- **`/wr-itil:transition-problem`** (singular) — one ticket per invocation. The authoritative executor for the single-transition user-initiated path (P093 / ADR-010 amended). Use when the user wants to transition one specific ticket and stop.
+- **`/wr-itil:transition-problem`** (singular) — one ticket per invocation. The authoritative executor for the single-transition user-initiated path (the "Problem 093: `/wr-itil:transition-problem` ↔ `/wr-itil:manage-problem` circular delegation for `<NNN> <status>` args" problem / the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended). Use when the user wants to transition one specific ticket and stop.
 - **`/wr-itil:transition-problems`** (plural, this skill) — batch transition. Accepts a list of `<NNN> <status>` pairs and runs each through an inline copy of the per-ticket mechanic, single commit at the end. Use when closing multiple verifyings at once or batch-marking known-error after a multi-ticket review.
 
-Both names coexist intentionally per the P071 singular/plural precedent. Plugin-developers reading this skill should recognise the same shape as `work-problem`/`work-problems`, `list-problems`, and `review-problems` — distinct intents for distinct ergonomic surfaces.
+Both names coexist intentionally per the "Problem 071: Argument-based skill subcommands are not discoverable in Claude Code autocomplete" problem singular/plural precedent. Plugin-developers reading this skill should recognise the same shape as `work-problem`/`work-problems`, `list-problems`, and `review-problems` — distinct intents for distinct ergonomic surfaces.
 
 ## Arguments
 
@@ -34,7 +34,7 @@ A space-separated list of `<NNN> <status>` pairs. Repeating the singular skill's
 - `<NNN>` — three-digit ticket ID (e.g. `063`).
 - `<status>` — destination status. One of:
   - `known-error` — Open → Known Error (root cause + workaround documented).
-  - `verifying` — Known Error → Verification Pending (fix released; awaiting user verification per ADR-022).
+  - `verifying` — Known Error → Verification Pending (fix released; awaiting user verification per the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule).
   - `close` — Verification Pending → Closed (user has confirmed the fix works in production).
 
 **Examples:**
@@ -44,7 +44,7 @@ A space-separated list of `<NNN> <status>` pairs. Repeating the singular skill's
 /wr-itil:transition-problems 070 known-error 080 verifying 094 close
 ```
 
-The pair tokens are **data parameters**, not word-subcommands — the same shape rule the singular's argument table cites against P071. Pairs are processed in argument order; each runs the full per-pair mechanic independently.
+The pair tokens are **data parameters**, not word-subcommands — the same shape rule the singular's argument table cites against the "Problem 071: Argument-based skill subcommands are not discoverable in Claude Code autocomplete" problem. Pairs are processed in argument order; each runs the full per-pair mechanic independently.
 
 If the argument count is odd, or any pair's tokens are malformed (`<NNN>` not three digits; `<status>` not in the enum), emit a usage message and stop without touching git.
 
@@ -52,9 +52,9 @@ If the argument count is odd, or any pair's tokens are malformed (`<NNN>` not th
 
 **In scope:**
 - Parse the pair list and validate each pair's argument shape (count is even; IDs are `\d{3}`; statuses are in the enum).
-- For each pair, run the per-ticket mechanic inline: ticket-file discovery, transition-path validation, pre-flight checks, P063 external-root-cause detection (Open → Known Error only), `git mv` to the new suffix, Status field edit, `## Fix Released` section write (Known Error → Verification Pending only), explicit P057 re-stage.
-- After the loop, refresh `docs/problems/README.md` ONCE per P062 (single render reflecting all surviving renames).
-- Commit ALL surviving transitions + the refreshed README in ONE commit per ADR-014 batch-grain unit-of-work.
+- For each pair, run the per-ticket mechanic inline: ticket-file discovery, transition-path validation, pre-flight checks, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection (Open → Known Error only), `git mv` to the new suffix, Status field edit, `## Fix Released` section write (Known Error → Verification Pending only), explicit the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem re-stage.
+- After the loop, refresh `docs/problems/README.md` ONCE per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem (single render reflecting all surviving renames).
+- Commit ALL surviving transitions + the refreshed README in ONE commit per the "Governance Skills Commit Their Own Completed Work" architecture rule batch-grain unit-of-work.
 - Report the per-pair outcome: succeeded pairs, failed pairs (with reason category), commit SHA.
 
 **Out of scope:**
@@ -62,7 +62,7 @@ If the argument count is odd, or any pair's tokens are malformed (`<NNN>` not th
 - Backlog re-ranking — that's `/wr-itil:review-problems`.
 - Ticket creation or bare-update flows — those stay on `/wr-itil:manage-problem`.
 - Parking — the `.parked.md` suffix has its own path on `/wr-itil:manage-problem`.
-- Auto-transitions inside review — Step 9b uses manage-problem's in-skill Step 7 block ("copy, not move") per ADR-010 amended.
+- Auto-transitions inside review — Step 9b uses manage-problem's in-skill Step 7 block ("copy, not move") per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended.
 - Release draining — `push:watch` / `release:watch` are owned by the caller (`/wr-itil:work-problems` orchestrator Step 6.5, or `/wr-itil:manage-problem` Step 12).
 
 ## Steps
@@ -79,13 +79,13 @@ If parsing fails at this stage, NO git operations have run. The user can re-invo
 
 ### 2. Per-pair execution loop (inline copy of the singular's per-ticket mechanic)
 
-> **Copy, not move (per ADR-010 amended Split-skill execution ownership).** The body below is a scoped inline copy of `/wr-itil:transition-problem` Steps 2–6 (discovery, validation, pre-flight, P063 detection, rename + Edit + re-stage). The per-pair commit step (singular Step 8) is INTENTIONALLY OMITTED — batch semantics replace it with the single commit in Step 4 below.
+> **Copy, not move (per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended Split-skill execution ownership).** The body below is a scoped inline copy of `/wr-itil:transition-problem` Steps 2–6 (discovery, validation, pre-flight, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem detection, rename + Edit + re-stage). The per-pair commit step (singular Step 8) is INTENTIONALLY OMITTED — batch semantics replace it with the single commit in Step 4 below.
 >
 > Drift between the singular and this inline copy is detected by the contract-assertion bats (`packages/itil/skills/transition-problems/test/transition-problems-contract.bats`) which asserts shared substring presence (e.g. the `git add docs/problems/` re-stage phrase) in BOTH files. If you edit one, edit the other.
 
 For each pair `(NNN, status)` in argument order:
 
-**2a. Discover the ticket file.** Dual-tolerant lookup spans flat layout AND per-state subdir layout per RFC-002 migration window:
+**2a. Discover the ticket file.** Dual-tolerant lookup spans flat layout AND per-state subdir layout per 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
@@ -104,13 +104,13 @@ If no file is found OR multiple files are found (suffix-exclusive lifecycle viol
 
 **2c. Run pre-flight checks** for the destination (same gating as the singular):
 
-- Open → Known Error (`known-error`): root cause documented; ≥ 1 investigation task ticked; reproduction test or reference; workaround documented; effort bucket re-rated if scope shifted (P047); status multiplier re-rated from Open 1.0 to Known Error 2.0 and WSJF recomputed with the post-transition status and current Effort (P498).
+- Open → Known Error (`known-error`): root cause documented; ≥ 1 investigation task ticked; reproduction test or reference; workaround documented; effort bucket re-rated if scope shifted (the "Problem 047: WSJF effort buckets are coarse and not re-rated at lifecycle transitions" problem); status multiplier re-rated from Open 1.0 to Known Error 2.0 and WSJF recomputed with the post-transition status and current Effort (the "WSJF uses the pre-transition status multiplier" problem).
 - Known Error → Verification Pending (`verifying`): fix implemented; release marker available (version, commit SHA, or date) for the `## Fix Released` section.
 - Verification Pending → Closed (`close`): user has explicitly confirmed the fix works in production. AFK callers (work-problems orchestrator) MUST supply the close pair via prior user authorisation (e.g. an `AskUserQuestion`-batched closure prompt at the orchestrator layer); this skill never auto-closes on inference.
 
 If any pre-flight fails, record the pair as `pre-flight-failed` with the failed-check list and continue to the next pair.
 
-**2d. P063 external-root-cause detection** (Open → Known Error only — fires per pair).
+**2d. the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem external-root-cause detection** (Open → Known Error only — fires per pair).
 
 Strict tokens (within Root Cause Analysis): `upstream`, `third-party`, `external`, `vendor`; or scoped npm package pattern `@[\w-]+/[\w-]+`.
 
@@ -120,18 +120,18 @@ if grep -iE '\b(upstream|third-party|external|vendor)\b|@[[:alnum:]_-]+/[[:alnum
 fi
 ```
 
-**Already-noted check** — before firing, grep for `- **Upstream report pending** --` (canonical ASCII per P210) or the legacy em-dash variant `- **Upstream report pending** —` (the grep MUST match BOTH variants for backward compatibility) or `- **Reported Upstream:**` or a `## Reported Upstream` section. If present, skip the prompt for this pair.
+**Already-noted check** — before firing, grep for `- **Upstream report pending** --` (canonical ASCII per the "work-problems SKILL.md AFK-fallback marker wording uses em-dash, forces consumer-side whitespace surgery" problem) or the legacy em-dash variant `- **Upstream report pending** —` (the grep MUST match BOTH variants for backward compatibility) or `- **Reported Upstream:**` or a `## Reported Upstream` section. If present, skip the prompt for this pair.
 
-**Branch on interactivity (per ADR-013 Rule 1 / Rule 6):**
+**Branch on interactivity (per the "Structured User Interaction for Governance-Skill Decisions" architecture rule Rule 1 / Rule 6):**
 
 - **Interactive** (`AskUserQuestion` available): use the same three-option prompt the singular's Step 5 documents (invoke /wr-itil:report-upstream / defer-and-note / not-actually-upstream).
-- **AFK / non-interactive** (orchestrator markers — "AFK", "work-problems", "batch-work", "ALL_DONE" — present in the invoking context): default to defer-and-note. Append `- **Upstream report pending** -- external dependency identified; invoke /wr-itil:report-upstream when ready` (canonical ASCII per P210) to the ticket's `## Related` section. Do NOT auto-invoke `/wr-itil:report-upstream` (its Step 6 security branch is interactive — per ADR-024).
+- **AFK / non-interactive** (orchestrator markers — "AFK", "work-problems", "batch-work", "ALL_DONE" — present in the invoking context): default to defer-and-note. Append `- **Upstream report pending** -- external dependency identified; invoke /wr-itil:report-upstream when ready` (canonical ASCII per the "work-problems SKILL.md AFK-fallback marker wording uses em-dash, forces consumer-side whitespace surgery" problem) to the ticket's `## Related` section. Do NOT auto-invoke `/wr-itil:report-upstream` (its Step 6 security branch is interactive — per the "Cross-project problem-reporting contract — `report-upstream` skill in `@windyroad/itil`" architecture rule).
 
 The detection is per-pair; each Open → Known Error pair runs its own check independently.
 
-**2e. Rename, edit, re-stage** (P057 staging-trap rule applied per pair).
+**2e. Rename, edit, re-stage** (the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem staging-trap rule applied per pair).
 
-> **Staging trap (P057).** `git mv` stages only the rename. After the `Edit` tool modifies the renamed file, you MUST explicitly `git add` it before continuing — without the explicit re-stage, the content edit leaks into the next commit. The plural inherits this rule per pair; the per-pair re-stage is non-negotiable.
+> **Staging trap (the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem).** `git mv` stages only the rename. After the `Edit` tool modifies the renamed file, you MUST explicitly `git add` it before continuing — without the explicit re-stage, the content edit leaks into the next commit. The plural inherits this rule per pair; the per-pair re-stage is non-negotiable.
 
 ```bash
 # Open → Known Error
@@ -141,7 +141,7 @@ git add docs/problems/known-error/<NNN>-<title>.md
 ```
 
 ```bash
-# Known Error → Verification Pending (per ADR-022)
+# Known Error → Verification Pending (per the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule)
 git mv docs/problems/known-error/<NNN>-<title>.md docs/problems/verifying/<NNN>-<title>.md
 # Edit Status to "Verification Pending" AND add ## Fix Released section
 # (release marker, one-sentence summary, Awaiting user verification)
@@ -164,55 +164,55 @@ Record each pair's outcome (succeeded / failed-with-reason) for the summary in S
 Per architect-resolved design (2026-04-26): if a pair fails in any of the substeps above (discovery, validation, pre-flight, git-op), it is skipped and recorded as a failed pair. The loop continues with the next pair. There is NO halt, NO rollback of previously-staged surviving pairs.
 
 Rationale grounded in existing decisions:
-- ADR-014's "complete unit of work" boundary is the BATCH at this grain — a partial batch (succeeded subset) is a legitimate unit. Halting and discarding succeeded pairs (option a) loses validated work the user already authorised.
-- ADR-013 Rule 6 forbids non-interactive destructive operations; rolling back staged renames (option c) requires `git reset` which is exactly the destructive class Rule 6 names.
+- the "Governance Skills Commit Their Own Completed Work" architecture rule's "complete unit of work" boundary is the BATCH at this grain — a partial batch (succeeded subset) is a legitimate unit. Halting and discarding succeeded pairs (option a) loses validated work the user already authorised.
+- the "Structured User Interaction for Governance-Skill Decisions" architecture rule Rule 6 forbids non-interactive destructive operations; rolling back staged renames (option c) requires `git reset` which is exactly the destructive class Rule 6 names.
 - Mirrors the `/wr-itil:work-problems` Step 4 classifier precedent (skip-and-surface; commit succeeded work; failed pairs surfaced in summary).
 
 **Zero-success path.** If ALL pairs failed (no pair survived to the staging step), DO NOT commit. Skip Steps 4 and 5's commit branches; emit a failure summary listing each failed pair's reason and stop without touching git.
 
-### 4. Refresh README + commit ONCE (single commit at batch grain per ADR-014)
+### 4. Refresh README + commit ONCE (single commit at batch grain per the "Governance Skills Commit Their Own Completed Work" architecture rule)
 
 After the per-pair loop finishes, IF AT LEAST ONE PAIR SUCCEEDED:
 
-**4a. Refresh `docs/problems/README.md` ONCE (P062 at batch grain).**
+**4a. Refresh `docs/problems/README.md` ONCE (the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem at batch grain).**
 
-Per P062, every Step 7 status transition refreshes README.md. At the batch grain, the refresh runs ONCE — a single render reflecting ALL surviving renames + Status updates. Not N refreshes (that would force the README to thrash N times mid-batch and amplify diff noise).
+Per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem, every Step 7 status transition refreshes README.md. At the batch grain, the refresh runs ONCE — a single render reflecting ALL surviving renames + Status updates. Not N refreshes (that would force the README to thrash N times mid-batch and amplify diff noise).
 
-The refresh follows the same render rules as `/wr-itil:review-problems` Step 9e (glob `docs/problems/*.open.md` / `*.known-error.md` / `*.verifying.md` / `*.parked.md`; rank open + known-error by WSJF; Verification Queue sorted by `Released date ASC` with same-day tiebreak by ID ASC per ADR-022 + P048; Parked section). It does NOT re-rank — existing WSJF values on ticket files are trusted; the refresh is a render, not a re-rank. <!-- VQ-SORT-DIRECTION: oldest-first per ADR-022 --> Drift on the VQ sort direction re-opens P150.
+The refresh follows the same render rules as `/wr-itil:review-problems` Step 9e (glob `docs/problems/*.open.md` / `*.known-error.md` / `*.verifying.md` / `*.parked.md`; rank open + known-error by WSJF; Verification Queue sorted by `Released date ASC` with same-day 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; Parked section). It does NOT re-rank — existing WSJF values on ticket files are trusted; the refresh is a render, not a re-rank. <!-- VQ-SORT-DIRECTION: oldest-first per the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule --> Drift on the VQ sort direction re-opens the "docs/problems/README.md Verification Queue rendered newest-first contradicts section header "Ranked by release age, oldest first"" problem.
 
-**Likely-verified cell shape (P186)**: the `Likely verified?` column carries an **evidence-first** cell — `yes — observed: <evidence>` / `no — not observed` / `no — observed regression`. At batch grain the refresh writes the per-pair cell from the per-pair transition context: a `verifying` destination defaults to `no — not observed` (the batch just released the fix; evidence accrues subsequently); a `close` destination assumes session-observed evidence was the trigger for the batch close (the upstream caller — `run-retro` Step 4a, `review-problems` Step 9d — already verified the evidence) and the row exits the queue (not re-rendered as VQ). <!-- LIKELY-VERIFIED-CELL-SHAPE: evidence-based per P186 --> Drift on the cell shape re-opens P186.
+**Likely-verified cell shape (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 `Likely verified?` column carries an **evidence-first** cell — `yes — observed: <evidence>` / `no — not observed` / `no — observed regression`. At batch grain the refresh writes the per-pair cell from the per-pair transition context: a `verifying` destination defaults to `no — not observed` (the batch just released the fix; evidence accrues subsequently); a `close` destination assumes session-observed evidence was the trigger for the batch close (the upstream caller — `run-retro` Step 4a, `review-problems` Step 9d — already verified the evidence) and the row exits the queue (not re-rendered as VQ). <!-- 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.
 
 ```bash
 git add docs/problems/README.md
 ```
 
-Update the "Last reviewed" line per the **inline P134 rotation mechanism** below. The mechanism is inlined here at the execution site (not deferred via cross-document reference to `manage-problem` SKILL.md Step 5) so a single-pass agent reading this Step 4a does not silently skip the archive step. **Skipping the BEFORE-rewrite archive step destroys the displaced fragment and re-opens P331** (iter-7 + iter-8 of 2026-05-30's AFK work-problems session silently skipped the rotation in 2 of 9 transition-bearing iters under exactly that failure mode). At batch grain the rotation fires ONCE for the entire batch (not per-pair) but the per-pair semantics are otherwise identical to the singular's Step 7. The mechanism MUST execute IN ORDER:
+Update the "Last reviewed" line per the **inline the "`docs/problems/README.md` line 3 narrative-blob accumulator bloat — sibling to (briefing tier 3) on a different surface" problem rotation mechanism** below. The mechanism is inlined here at the execution site (not deferred via cross-document reference to `manage-problem` SKILL.md Step 5) so a single-pass agent reading this Step 4a does not silently skip the archive step. **Skipping the BEFORE-rewrite archive step destroys the displaced fragment and re-opens the "transition-problem SKILL Step 7 Last-reviewed rotation silently skipped across iters" problem** (iter-7 + iter-8 of 2026-05-30's AFK work-problems session silently skipped the rotation in 2 of 9 transition-bearing iters under exactly that failure mode). At batch grain the rotation fires ONCE for the entire batch (not per-pair) but the per-pair semantics are otherwise identical to the singular's Step 7. The mechanism MUST execute IN ORDER:
 
 1. **Read** line 3 of `docs/problems/README.md`: `awk 'NR==3' docs/problems/README.md` (`head -3 | tail -1` or `sed -n '3p'` are acceptable equivalents).
 2. **Append-if-non-empty (BEFORE step 3, not after)** — if line 3 is non-empty AND not a same-session same-verb near-duplicate of the new batch fragment, append the existing line 3 verbatim to `docs/problems/README-history.md` under a `## YYYY-MM-DD` heading (creating the heading on first append for that date; subsequent same-day appends nest under the existing heading). Run this BEFORE the Edit-tool rewrite in step 3 — Edit's replace pattern destroys the displaced content otherwise.
-3. **Rewrite** line 3 of `docs/problems/README.md` with the new batch fragment of form `> Last reviewed: YYYY-MM-DD **batch transition** — P<NNN> <status>, P<NNN> <status>, …` (e.g. `> Last reviewed: 2026-06-01 **batch transition** — P063 close, P067 close, P092 close, P094 close`). Soft cap ≤ 1024 bytes per fragment — if the cohort would exceed it, abbreviate to ID + verb only and let the per-ticket bodies carry the rationale; hard ceiling 5120 bytes per ADR-040 Tier 3 envelope.
-4. **Stage both** — `git add docs/problems/README.md docs/problems/README-history.md` so the same single batch commit per ADR-014 captures both files.
+3. **Rewrite** line 3 of `docs/problems/README.md` with the new batch fragment of form `> Last reviewed: YYYY-MM-DD **batch transition** — P<NNN> <status>, P<NNN> <status>, …` (e.g. `> Last reviewed: 2026-06-01 **batch transition** — the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem close, the "Problem 067: /wr-itil:report-upstream classifier is not problem-first — picks bug / feature / question and emits a bug-shaped default" problem close, the "Problem 092: `/install-updates` Step 4 `<plugin-short-name>` placeholder is ambiguous about the `wr-` prefix" problem close, the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem close`). Soft cap ≤ 1024 bytes per fragment — if the cohort would exceed it, abbreviate to ID + verb only and let the per-ticket bodies carry the rationale; hard ceiling 5120 bytes per the "Session-start briefing surface — SessionStart hook over tiered directory + indexed README" architecture rule Tier 3 envelope.
+4. **Stage both** — `git add docs/problems/README.md docs/problems/README-history.md` so the same single batch commit per the "Governance Skills Commit Their Own Completed Work" architecture rule captures both files.
 
-Canonical rationale anchor: `manage-problem` SKILL.md Step 5 § Last-reviewed line discipline (P134). The cross-reference is preserved for the "why"; the "what" is inlined above for execution-time legibility per P331.
+Canonical rationale anchor: `manage-problem` SKILL.md Step 5 § Last-reviewed line discipline (the "`docs/problems/README.md` line 3 narrative-blob accumulator bloat — sibling to (briefing tier 3) on a different surface" problem). The cross-reference is preserved for the "why"; the "what" is inlined above for execution-time legibility per the "transition-problem SKILL Step 7 Last-reviewed rotation silently skipped across iters" problem.
 
-**4b. Commit gate (per ADR-014).**
+**4b. Commit gate (per the "Governance Skills Commit Their Own Completed Work" architecture rule).**
 
 Satisfy via one of two paths (either produces a bypass marker):
 
 - **Primary**: delegate to subagent type `wr-risk-scorer:pipeline` via the Agent tool.
-- **Fallback** (per ADR-015 / P035): if `wr-risk-scorer:pipeline` is unavailable in the current tool set, invoke `/wr-risk-scorer:assess-release` via the Skill tool — `PostToolUse:Agent` writes the equivalent bypass marker. Do NOT silently skip the gate.
+- **Fallback** (per the "On-Demand Assessment Skills for Governance Plugins" architecture rule / the "Problem 035: manage-problem commit gate has no fallback when subagent delegation is unavailable" problem): if `wr-risk-scorer:pipeline` is unavailable in the current tool set, invoke `/wr-risk-scorer:assess-release` via the Skill tool — `PostToolUse:Agent` writes the equivalent bypass marker. Do NOT silently skip the gate.
 
 **4c. Commit ONCE.**
 
 ONE commit covers: every surviving renamed ticket file + every Status edit + every `## Fix Released` section + the refreshed `docs/problems/README.md`. NO per-pair commits.
 
-**Commit message conventions** (batch variants extending ADR-014's table):
+**Commit message conventions** (batch variants extending the "Governance Skills Commit Their Own Completed Work" architecture rule's table):
 
-- Homogeneous-destination batch: `docs(problems): batch transition — close P063, P067, P092, P094 (4 tickets)`
-- Mixed-destination batch: `docs(problems): batch transition — P063 close, P070 known-error, P094 verifying (3 tickets)`
-- If the batch destination is `verifying` and rides with a fix commit, the commit-message scope follows the singular's pattern: `fix(<scope>): <description> (closes P063, P067)` — but the batch surface is unusual in the riding-with-fix shape; the canonical caller is verification-close housekeeping, not fix-release.
+- Homogeneous-destination batch: `docs(problems): batch transition — close the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem, the "Problem 067: /wr-itil:report-upstream classifier is not problem-first — picks bug / feature / question and emits a bug-shaped default" problem, the "Problem 092: `/install-updates` Step 4 `<plugin-short-name>` placeholder is ambiguous about the `wr-` prefix" problem, the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem (4 tickets)`
+- Mixed-destination batch: `docs(problems): batch transition — the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem close, the "Problem 070: /wr-itil:report-upstream does not check for existing upstream issues before filing" problem known-error, the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem verifying (3 tickets)`
+- If the batch destination is `verifying` and rides with a fix commit, the commit-message scope follows the singular's pattern: `fix(<scope>): <description> (closes the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem, the "Problem 067: /wr-itil:report-upstream classifier is not problem-first — picks bug / feature / question and emits a bug-shaped default" problem)` — but the batch surface is unusual in the riding-with-fix shape; the canonical caller is verification-close housekeeping, not fix-release.
 
-If commit risk is above appetite: auto-apply scorer remediations per **ADR-042 Rule 1** until within appetite, OR halt per ADR-042 Rule 5. **MUST NOT commit above appetite; MUST NOT call `AskUserQuestion` to ask whether to commit anyway** (P377/RFC-029 — framework-mediated, not a one-time-override). If `AskUserQuestion` is unavailable (AFK), the ADR-013 Rule 6 fail-safe applies — skip the commit and report the uncommitted state — apply the same rule the singular does at the same gate.
+If commit risk is above appetite: auto-apply scorer remediations per **the "Auto-apply scorer remediations to reach within appetite — open action-class vocabulary" architecture rule Rule 1** until within appetite, OR halt per the "Auto-apply scorer remediations to reach within appetite — open action-class vocabulary" architecture rule Rule 5. **MUST NOT commit above appetite; MUST NOT call `AskUserQuestion` to ask whether to commit anyway** (the "Skills, agents, and hooks override RISK-POLICY appetite instead of applying it" problem/the ": Apply RISK-POLICY appetite faithfully across all surfaces" release design — framework-mediated, not a one-time-override). If `AskUserQuestion` is unavailable (AFK), the "Structured User Interaction for Governance-Skill Decisions" architecture rule Rule 6 fail-safe applies — skip the commit and report the uncommitted state — apply the same rule the singular does at the same gate.
 
 ### 5. Report the outcome
 
@@ -224,15 +224,15 @@ Emit a structured summary:
 ### Succeeded ({N})
 | Ticket | Previous status | New status | New filename |
 |--------|-----------------|------------|--------------|
-| P063 | Verification Pending | Closed | docs/problems/063-...closed.md |
-| P067 | Verification Pending | Closed | docs/problems/067-...closed.md |
+| the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem | Verification Pending | Closed | docs/problems/063-...closed.md |
+| the "Problem 067: /wr-itil:report-upstream classifier is not problem-first — picks bug / feature / question and emits a bug-shaped default" problem | Verification Pending | Closed | docs/problems/067-...closed.md |
 | ...
 
 ### Failed ({M})
 | Ticket | Destination | Reason |
 |--------|-------------|--------|
-| P099 | known-error | discovery-failed: no ticket found |
-| P101 | verifying | invalid-transition: ticket is .open.md (must go to known-error first) |
+| the "Problem 099: `docs/BRIEFING.md` grows unbounded via run-retro appends — violates progressive disclosure" problem | known-error | discovery-failed: no ticket found |
+| the "`wr-retrospective` has no context-usage analysis — opaque where session tokens are consumed; no guidance on what to trim" problem | verifying | invalid-transition: ticket is .open.md (must go to known-error first) |
 | ...
 
 Commit: {sha}  ({N tickets committed in one batch})
@@ -246,14 +246,14 @@ Release draining is owned by the caller (orchestrator Step 6.5 / manage-problem
 
 `transition-problems` (plural) owns:
 - Pair-list parse + per-pair argument validation.
-- Per-pair execution (inline copy of singular Steps 2–6) — discovery, transition-path validation, pre-flight, P063 detection, rename + Edit + P057 re-stage.
+- Per-pair execution (inline copy of singular Steps 2–6) — discovery, transition-path validation, pre-flight, the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem detection, rename + Edit + the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem re-stage.
 - Per-pair partial-failure tracking (skip-and-surface).
-- ONE README.md refresh at the end (P062 at batch grain).
-- ONE ADR-014 commit at the end through the risk-scorer commit gate.
+- ONE README.md refresh at the end (the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem at batch grain).
+- ONE the "Governance Skills Commit Their Own Completed Work" architecture rule commit at the end through the risk-scorer commit gate.
 - Structured per-pair outcome summary.
 
 `transition-problems` does NOT:
-- Re-invoke `/wr-itil:transition-problem` per pair via the Skill tool — that would re-introduce the N×SKILL.md-reload cost P117 targets. Inline copy per ADR-010 amended "copy, not move".
+- Re-invoke `/wr-itil:transition-problem` per pair via the Skill tool — that would re-introduce the N×SKILL.md-reload cost the "No batch-transition surface for multiple problem tickets in a single run-retro / review cycle" problem targets. Inline copy per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended "copy, not move".
 - Run per-pair commits — only the single batch commit at the end is permitted. The singular's per-invocation commit grain is deliberately re-aggregated at this skill's batch grain.
 - Re-rank the backlog (use `/wr-itil:review-problems`).
 - Create tickets or run the bare-`<NNN>` update flow (use `/wr-itil:manage-problem`).
@@ -262,7 +262,7 @@ Release draining is owned by the caller (orchestrator Step 6.5 / manage-problem
 
 ## Drift management (singular ↔ plural inline copy)
 
-Per ADR-010 amended "Split-skill execution ownership", three call sites now share the per-ticket transition mechanic via "copy, not move":
+Per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended "Split-skill execution ownership", three call sites now share the per-ticket transition mechanic via "copy, not move":
 
 1. `/wr-itil:transition-problem` Steps 2–8 (singular, user-initiated single).
 2. `/wr-itil:transition-problems` Step 2 (this skill, user-initiated batch — inline copy of the singular's Steps 2–6, batch-aggregated commit replacing Step 8).
@@ -270,28 +270,28 @@ Per ADR-010 amended "Split-skill execution ownership", three call sites now shar
 
 Drift detection lives in the contract-assertion bats. `packages/itil/skills/transition-problems/test/transition-problems-contract.bats` asserts shared substring presence (e.g. the `git add docs/problems/` re-stage phrase) in both this file and the singular SKILL.md so a future edit that drops the re-stage rule from one is immediately visible.
 
-When the per-ticket mechanic changes (e.g. a new pre-flight check or P063 token added), update ALL THREE copies in lockstep — the contract bats will fail otherwise, surfacing the drift.
+When the per-ticket mechanic changes (e.g. a new pre-flight check or the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem token added), update ALL THREE copies in lockstep — the contract bats will fail otherwise, surfacing the drift.
 
 ## Related
 
-- **P117** (`docs/problems/117-no-batch-transition-for-multiple-problem-tickets.open.md`) — originating ticket. Closing 4+ tickets in one run-retro / manage-problem review costs N×SKILL.md reload OR an ownership-boundary violation; this skill closes that gap.
-- **P071** (`docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md`) — singular/plural split precedent; established `work-problem`/`work-problems` and `list-problems`/`review-problems` siblings.
-- **P093** (`docs/problems/093-transition-problem-and-manage-problem-circular-delegation-for-nnn-status-args.*.md`) — the circular-delegation ticket whose resolution gave the singular `transition-problem` ownership of the per-ticket mechanic. This skill extends that ownership to the batch grain.
-- **P097** (`docs/problems/097-skill-md-runtime-size.open.md`) — the SKILL.md-runtime-size pressure cluster. P117 is a concrete cost case of P097's broader concern; this plural skill addresses the cost case directly.
-- **ADR-010 amended** (`docs/decisions/010-rename-wr-problem-to-wr-itil.proposed.md` — Skill Granularity + Split-skill execution ownership) — authorises the singular/plural split AND the "copy, not move" inline-copy pattern.
-- **ADR-013** — Rule 1 for interactive prompts; Rule 6 for the AFK non-interactive branch (P063 fallback inherited from the singular per pair).
-- **ADR-014** — governance skills commit their own work. Batch grain is one unit of work — ONE commit at the end covering all surviving transitions.
-- **ADR-022** — `.verifying.md` suffix on release; Verification Pending is a first-class status. Batch verification-close is a common caller (release-aged verifyings drained at the end of a session).
-- **ADR-032** — governance skill invocation patterns. `/wr-itil:work-problems` may delegate batch closures here during AFK orchestration; this skill is foreground-synchronous in that delegation.
-- **ADR-037** — contract-assertion bats pattern. The contract-bats for this skill ALSO performs cross-file drift detection between this SKILL.md and the singular's SKILL.md (the inline-copy invariant).
-- **P057** — `git mv` + Edit staging trap; the per-pair re-stage rule applied N times in this skill's loop.
-- **P062** — README.md refresh on every transition. At batch grain, the refresh fires ONCE at the end (single render covers all surviving renames).
-- **P063** — external-root-cause detection at Open → Known Error. Fires per pair; AFK fallback inherited from the singular (append the stable Upstream report pending marker).
-- **JTBD-001** (`docs/jtbd/developer/JTBD-001-enforce-governance.proposed.md`) — eliminates the N×SKILL.md reload tax + ownership-boundary violation at batch closures; serves the "without slowing down" half of the job.
-- **JTBD-006** (`docs/jtbd/developer/JTBD-006-work-backlog-afk.proposed.md`) — work-problems orchestrator may delegate release-batched closures through this surface during extended AFK runs.
-- **JTBD-101** (`docs/jtbd/plugin-developer/JTBD-101-extend-suite.proposed.md`) — singular/plural split is the established pattern; plugin-developers reading this should immediately recognise the shape.
+- **the "No batch-transition surface for multiple problem tickets in a single run-retro / review cycle" problem** (`docs/problems/117-no-batch-transition-for-multiple-problem-tickets.open.md`) — originating ticket. Closing 4+ tickets in one run-retro / manage-problem review costs N×SKILL.md reload OR an ownership-boundary violation; this skill closes that gap.
+- **the "Problem 071: Argument-based skill subcommands are not discoverable in Claude Code autocomplete" problem** (`docs/problems/071-argument-based-skill-subcommands-are-not-discoverable.open.md`) — singular/plural split precedent; established `work-problem`/`work-problems` and `list-problems`/`review-problems` siblings.
+- **the "Problem 093: `/wr-itil:transition-problem` ↔ `/wr-itil:manage-problem` circular delegation for `<NNN> <status>` args" problem** (`docs/problems/093-transition-problem-and-manage-problem-circular-delegation-for-nnn-status-args.*.md`) — the circular-delegation ticket whose resolution gave the singular `transition-problem` ownership of the per-ticket mechanic. This skill extends that ownership to the batch grain.
+- **the "Problem 097: SKILL.md files mix runtime-necessary steps with maintainer-facing rationale, bloating every skill invocation" problem** (`docs/problems/097-skill-md-runtime-size.open.md`) — the SKILL.md-runtime-size pressure cluster. the "No batch-transition surface for multiple problem tickets in a single run-retro / review cycle" problem is a concrete cost case of the "Problem 097: SKILL.md files mix runtime-necessary steps with maintainer-facing rationale, bloating every skill invocation" problem's broader concern; this plural skill addresses the cost case directly.
+- **the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended** (`docs/decisions/010-rename-wr-problem-to-wr-itil.proposed.md` — Skill Granularity + Split-skill execution ownership) — authorises the singular/plural split AND the "copy, not move" inline-copy pattern.
+- **the "Structured User Interaction for Governance-Skill Decisions" architecture rule** — Rule 1 for interactive prompts; Rule 6 for the AFK non-interactive branch (the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem fallback inherited from the singular per pair).
+- **the "Governance Skills Commit Their Own Completed Work" architecture rule** — governance skills commit their own work. Batch grain is one unit of work — ONE commit at the end covering all surviving transitions.
+- **the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule** — `.verifying.md` suffix on release; Verification Pending is a first-class status. Batch verification-close is a common caller (release-aged verifyings drained at the end of a session).
+- **the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule** — governance skill invocation patterns. `/wr-itil:work-problems` may delegate batch closures here during AFK orchestration; this skill is foreground-synchronous in that delegation.
+- **the "Skill testing strategy — contract-assertion bats companion to" architecture rule** — contract-assertion bats pattern. The contract-bats for this skill ALSO performs cross-file drift detection between this SKILL.md and the singular's SKILL.md (the inline-copy invariant).
+- **the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem** — `git mv` + Edit staging trap; the per-pair re-stage rule applied N times in this skill's loop.
+- **the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem** — README.md refresh on every transition. At batch grain, the refresh fires ONCE at the end (single render covers all surviving renames).
+- **the "Problem 063: manage-problem does not trigger /wr-itil:report-upstream when root cause is external" problem** — external-root-cause detection at Open → Known Error. Fires per pair; AFK fallback inherited from the singular (append the stable Upstream report pending marker).
+- **the ": Enforce Governance Without Slowing Down" user outcome** (`docs/jtbd/developer/the ": Enforce Governance Without Slowing Down" user outcome-enforce-governance.proposed.md`) — eliminates the N×SKILL.md reload tax + ownership-boundary violation at batch closures; serves the "without slowing down" half of the job.
+- **the ": Progress the Backlog While I'm Away" user outcome** (`docs/jtbd/developer/the ": Progress the Backlog While I'm Away" user outcome-work-backlog-afk.proposed.md`) — work-problems orchestrator may delegate release-batched closures through this surface during extended AFK runs.
+- **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`) — singular/plural split is the established pattern; plugin-developers reading this should immediately recognise the shape.
 - `packages/itil/skills/transition-problem/SKILL.md` — singular sibling. Source-of-truth for the per-ticket mechanic this skill carries an inline copy of. When the mechanic changes, update both files in lockstep.
-- `packages/itil/skills/manage-problem/SKILL.md` — third call site of the per-ticket mechanic (in-skill Step 7 block). Per ADR-010 amended "copy, not move", three inline copies coexist.
+- `packages/itil/skills/manage-problem/SKILL.md` — third call site of the per-ticket mechanic (in-skill Step 7 block). Per the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended "copy, not move", three inline copies coexist.
 - `packages/itil/skills/review-problems/SKILL.md` — sibling refresh skill; same README render contract this skill uses for the Step 4a refresh.
 - `packages/itil/skills/work-problem/SKILL.md` and `packages/itil/skills/work-problems/SKILL.md` — singular/plural pair this skill mirrors.
 - `packages/retrospective/skills/run-retro/SKILL.md` — Step 4a verification-close housekeeping is the canonical caller of this batch surface.

package/skills/transition-problems/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "WR ITIL: Transition Problems"
+  short_description: "Advance multiple problems through their lifecycle."