Portfolio Review

---
name: portfolio-review
description: |-
  Read-only cross-task board across every active task in all projects. Runs scripts/portfolio-review.sh to classify each active task as done-unclosed, blocked, my-move, stale, or in-flight, then renders one ranked board with a single recommended next action per row, so picking the next thread and catching finished-but-unarchived tasks stop depending on memory. An --outcomes mode reports closed-task outcome telemetry (merge status, cycle time) instead of the live board. Use when you have many concurrent active tasks and want a portfolio-level view of whose move it is and what has gone quiet, when deciding which task to pick up next, or when sweeping for tasks that should be closed. Do not use for routing inside a single active task (use what-next), for a deep checkpoint of one task (use where-we-at), or to change any task's state (this command never writes).
metadata:
  category: "state-and-navigation"
  primary-cursor-mode: "Ask"
  multi-repo-aware: "false"
  context-layers-consumed: "memory"
  context-layers-produced: ""
  tools: "Read, Bash, Glob, Grep"
  x-wos-profiles: "core, full"
  provenance: "first-party"
  suggested-model: "claude-haiku-4-5"
---

Act as a senior workflow orchestrator looking across the whole portfolio of active tasks, not inside any single one.

Goal:
Render a read-only board of every active task across all projects, classified and ranked, with one recommended next action per row, so the maintainer sees at a glance whose move it is, what is finished-but-unarchived, and what has gone quiet.

Mandatory context bootstrap (before any output):
- Read these sections in `WORKFLOW_OPERATING_SYSTEM.md` first:
  - `## LLM execution contract`
  - `## Editor mode policy` (mode definitions only; the tool mapping table is lazy-loaded in `wos/editor-mode-mappings.md` and needed only for non-Claude-Code tools)
  - `## Global output contract` (including **Adaptive handoff** and **Mode selection rule**)
  - `## Cross-cutting workflow guardrails`
- **Bootstrap tiers:** the light-weight commands (`branch-commit`, `what-next`, `where-we-at`, `slice-closure`, `compact-task-memory`) plus the high-frequency `implement-approved-slice` and `sync-task-state` (v3 wave1 item D) read the four sections above with two subsections of `## Cross-cutting workflow guardrails` skipped: `### External web access (centralized)` and `### Sequencing heuristics (by phase)`. Everything else is read at every tier, including `### Proposal vs approved persistence` and `### Substrate peer ownership (per ADR-0034)`, since all seven write substrate sections and reason about PROPOSED (`state-reconcile` stays on the full tier for cross-artifact judgment). The full tier is measured at 12109 tokens, the four always-read sections combined; the two skipped subsections are 1,034 of those (measured 2026-09-28), so the reduced tier is about 11,074. The leaf-reviewer tier (`verify-against-rubric`, ADR-0226) reads only `## Global output contract`, measured at 5215 tokens, plus its rubric.
- **Session bootstrap reuse (skip-if-unchanged; v3 wave1 item D):** WHEN this conversation already read the bootstrap sections in an earlier turn still VISIBLE in the context window AND `WORKFLOW_OPERATING_SYSTEM.md` has not changed since, the command MAY skip the re-read and cite the earlier one, emitting one Command transcript line: `Bootstrap: reusing turn <N> read, WOS unchanged`. Scoped exception to the context-budget re-fetch rule (`wos/context-budget.md`, "The re-fetch rule"), because these sections are one large, static, byte-identical read repeated every turn; every other tool result still re-fetches. VISIBLE means the section text itself is still present and quotable now, not merely that a record of the earlier read exists: a harness that clears a tool result while the record survives (ADR-0114) has not satisfied VISIBLE, and self-declared memory after a compaction never qualifies. A stateless-per-turn harness is excluded. The transcript line is mandatory; a silent skip is invalid output.
- **Resolving the spec and `wos/<topic>.md`:** canonical repository FIRST. Otherwise use active-adapter docs: `~/.claude/workflow-docs` (`CLAUDE_WORKFLOW_DOCS_DIR`), `~/.cursor/workflow-docs` (`WORKFLOW_DOCS_DIR`; project `.cursor/workflow-docs` on project installs), `~/.codex/workflow-docs` (`CODEX_WORKFLOW_DOCS_DIR`), or `<kimi-home>/workflow-docs` (`KIMI_WORKFLOW_DOCS_DIR`). Nonempty overrides win. Kimi home: `KIMI_CODE_HOME`, else existing `~/.kimi-code`, else existing `~/.kimi`, default `~/.kimi-code`. Use one root for both paths; try other adapters if absent or unknown. Report resolved root, fallback to other adapters, or missing mandatory context in `### Command transcript`. Installed snapshots refresh and prune retired topics only on sync.
- Read additional sections only when relevant to this command's role.
- Align all routing recommendations and next-command suggestions with the current command set.
- **Official next-command names only:** recommendations, including `Run now`, use registered names from `commands/<name>.md` or `commands/<name>/SKILL.md`; installed mode uses the available Fhorja command or skill inventory. No invented aliases. `Run now: none` with `Mode: N/A` ends only if no honest next step exists, defined under `### Official command names (routing integrity)` (ADR-0126).
Required inputs:
- none required (the command scans every `projects/*/active/*/TASK_STATE.md`)
- optional: `--project <client>__<project>` to scope to one project
- optional: `--stale-days N` to set the idle threshold (default 7)
- optional: `--initiative` to report the dependency view over `INITIATIVE_INDEX.md` (which sub-task is unblocked and startable next) instead of the cross-task board (ADR-0062)
- optional: `--outcomes` to report closed-task outcome telemetry from `projects/*/OUTCOMES.jsonl` (per-project closed count, effective merge-status counts, and cycle-time medians) instead of the cross-task board

Task repository files to update:
- none (this command is strictly read-only; it never writes any task's memory)

Operating rules:
- Do not implement code; do not write or modify any task's memory. This is a reporting command.
- **Handoff:** end with the adaptive `### Handoff` block per `WORKFLOW_OPERATING_SYSTEM.md` `## Global output contract` (Mode A compact or Mode B full).
- **Run the helper first.** Execute `scripts/portfolio-review.sh` (pass through any `--project` / `--stale-days` the user gave). It globs every active task, extracts phase, recommended next command, blocker state, and idle days, classifies each, and prints a ranked table plus per-class totals. Read its output; do not re-read all task folders yourself. Run it from the task repository root, the directory holding `projects/`: it reads the directory it runs from, and exits 2 with `not scanned, no projects/ directory` anywhere else. Resolve `scripts/portfolio-review.sh` against the WORKFLOW ROOT (the clone, or the installed docs directory, which ships it per ADR-0224). WHEN it is in neither, or exits 2, say so in `### Command transcript` and render no board: an empty board would read as "no active task".
- **Initiative dependency mode (ADR-0062).** When the user passes `--initiative`, run `scripts/portfolio-review.sh --initiative` (with any `--project`): it parses `projects/*/INITIATIVE_INDEX.md`, builds the blocked-by DAG in the shell, and reports each sub-task as done / ready / blocked, one `start now` recommendation (the first unblocked not-done task), plus dangling-ref and possible-cycle warnings. The cross-link column is free text, so parsing is best-effort: when the helper warns it could not parse a row or found a dangling ref, surface that, do not invent a dependency. This mode is read-only like the board; it never writes `INITIATIVE_INDEX.md` (the orchestrator is its sole writer per ADR-0040).
- **Outcomes telemetry mode.** When the user passes `--outcomes`, run `scripts/portfolio-review.sh --outcomes` (with any `--project`): it walks each project's `OUTCOMES.jsonl` per the read contract in `templates/OUTCOMES.schema.md`, resolves each task's effective merge status latest-event-wins (a later revert or reopen line overrides an earlier outcome), and prints per project the closed-task count, effective-status counts (merged, waived, not-merged, reverted, reopened), the median total cycle days, and the median days for each phase boundary present. A project with no ledger yet, or a run with no ledger anywhere, reports "no outcome records yet" rather than failing. This mode is measurement only: it reports what happened, it never gates a workflow step, and it never writes.
- **HTML board projection (a sibling script, not a mode of this command).** For the offline HTML portfolio board (active tasks, initiative rows, outcome summaries, and any running background runs), point the user to `python3 scripts/build-portfolio-board.py`: it consumes this command's helper via `scripts/portfolio-review.sh --json` (the same classifier, so the taxonomy cannot drift) and writes the gitignored `projects/BOARD.html`. Generating the board belongs to that standalone script; this command stays strictly read-only and never writes the board itself.
- **Classes (the helper's taxonomy):**
  - `done-unclosed`: phase reads closed/done/delivery, or the next command is terminal (`task-close`, `pr-package`, `branch-commit`, `where-we-at`, `slice-closure`). Finished or one step from it, still sitting in `active/`. Recommend closing/archiving.
  - `blocked`: the Open questions / blockers section explicitly mentions a blocker. Recommend the unblocking action.
  - `my-move`: the recommended next command is a maintainer decision (`approve-plan`, `decision-interview`, `targeted-questions`, `approve-proposed`, `resolve-contract-gaps`, `contract-signoff`). The ball is in the maintainer's court.
  - `stale`: idle beyond the threshold with no clearer signal. Recommend a checkpoint (`where-we-at`) or a resume.
  - `in-flight`: recently active, agent-side next step. Usually leave alone.
- **One action per row.** For each row, give the single most useful next move in plain terms (close it, approve it, unblock it via X, check it with where-we-at, or leave it). Do not expand into multi-step plans; the per-task detail lives in each task's own `what-next` / `where-we-at`.
- **Lead with the actionable classes.** Surface `done-unclosed`, `blocked`, and `my-move` first (these need the maintainer); summarize `stale` and `in-flight` more briefly.
- Honor the helper's classification; only override a row's class when the TASK_STATE content plainly contradicts it (note the override).
- The board reads across all projects, which may include private client task names; the output is local and not committed, so this is acceptable. Do not copy client task names into any committed artifact.

Required output:
1. The per-class totals line (done-unclosed / blocked / my-move / stale / in-flight).
2. The ranked board, actionable classes first, with one recommended action per row.
3. A short "top of your list" call-out: the 1 to 3 highest-value moves right now (usually: close the oldest done-unclosed, unblock the oldest blocked, make the pending decision).
4. What to explicitly ignore for now (the in-flight rows).

### Claim grounding (active epistemic humility)
**Claim grounding (active epistemic humility).** This block governs what you may assert and how you record it. It is keyed to the substrate section you are writing, not to which command is running, and it is INERT on any output that writes none of the claim-bearing sections below. Full contract and rationale: `wos/active-epistemic-humility.md`.

1. When this applies. This block fires ONLY while you are writing a claim-bearing substrate section: `TASK_STATE.md ## Current known facts`, `## Risks to watch`, `## Observations`, `## Active files in scope`, `## Canonical decisions`; `DECISIONS.md ## Locked decisions`; `IMPLEMENTATION_PLAN.md ## Current gaps`, `## Risks and mitigations`; `IMPACT_ANALYSIS.md`; `EXTERNAL_RESEARCH.md`; `REFERENCES.md`; or any section whose content is a statement a later command or a human decision will act on. WHEN your output writes none of these, this block imposes nothing: skip it and proceed. This is the D-13 inert clause; a fully-grounded or claim-free output pays nothing.

2. The unit is the load-bearing claim. A load-bearing claim is one a downstream command or a human decision consumes. A passing aside is not load-bearing; a statement someone will act on is. Apply the rest of this block per load-bearing claim, not per sentence.

3. Ground it or abstain. Before you assert a load-bearing claim, trace it to the enumerable grounded set: a captured `REFERENCES.md` entry, a file read in this session, command output actually seen, or a passing deterministic gate. A claim supported only by model memory is OUTSIDE the grounded set, including when you are right, because that support is not observable. WHEN a load-bearing claim falls outside the set, do NOT assert it: either investigate until it is grounded, or abstain per rule 6.

4. Status records provenance, never confidence. WHERE you attach an epistemic status to a claim, the status names WHERE THE CLAIM CAME FROM: a `REFERENCES.md` entry title, a file path plus line, or the gate output it came from. It SHALL NOT express a degree of certainty. Do NOT add a confidence field, a numeric threshold, or a self-assessment prompt anywhere; a self-reported confidence signal is not a usable control signal (`wos/active-epistemic-humility.md` Part 1.3). A status whose referent slot is empty is read as UNKNOWN, not as a weak yes.

5. Persisted claims carry the status; chat-only claims carry it when they route. Every load-bearing claim you write into a task-memory artifact carries its provenance referent, and that referent travels with the claim so a later command reads it too; do not drop it at the write boundary. A load-bearing claim that appears only in a chat-turn output carries a status only when it crosses the grounding boundary and triggers a route (an abstention, an escalation).

6. Abstain as a routed continuation, never a bare refusal. WHEN you abstain, name the specific investigation that would settle the question AND route to the command that runs it (`capture-references`, `code-locate`, `incident-triage`, or the fitting one). A withholding that stalls the work is invalid output. Abstention is distinct from `NO_OP`: `NO_OP` means there is no work to do; abstention means there is work and the grounding to do it is missing.

7. An unfired gate is not evidence. The absence of a fired check does not mean grounding existed. Do not read silence here as a pass.
### Standard output layout (required)
Produce the command output using this structure (English only):

### Artifact changes
Follow `## Global output contract` in `WORKFLOW_OPERATING_SYSTEM.md` for `APPLIED` / `PROPOSED` / `SKIP` rules. Every listed file carries one of those three tokens, in Lean output too; a prose verb like "written" is not a label.

### Command transcript
Brief audit trail (max 4 lines; max 3 in no-op runs with `NO_OP_TRACE`).

### Handoff
Use the adaptive ending format of `WORKFLOW_OPERATING_SYSTEM.md` `## Global output contract`. Every Handoff is one fenced `text` block with all four lines, `Run now:`, `Mode:`, `Work complexity:` and `Reason:`, on a stop and on a refusal too; the terminal form is `Run now: none` with `Mode: N/A`. A new `Mode:`, a model or a fresh session is never a stop, an offered choice is one, and `Reason:` names a role, never a model.
### Definition of done (command output)
- `scripts/portfolio-review.sh` was run and its board interpreted, not re-derived by hand.
- `### Artifact changes` is `None` (this command never writes).
- The actionable classes (done-unclosed, blocked, my-move) are surfaced first, each row with one recommended action.
- A "top of your list" call-out names the 1 to 3 highest-value moves.
- Before declaring this output done, confirm it satisfies the shared **Definition of done (command outputs)** and **Gate conditions** in WORKFLOW_OPERATING_SYSTEM.md.

Quality bar:
Optimize for a fast, honest, scannable portfolio view that tells the maintainer where to spend the next move. No per-task deep dives, no writes.