portfolio-status
Roll up the portfolio from _log.yaml — risk distribution, upcoming deadlines, stale matters, materiality totals, stage distribution, and flagged anomalies. Use when the user asks "where do we stand", "how many open matters", or wants a portfolio rollup or status across all active matters.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.0w
- Forks
- 2.0k
01 前言 Front Matter
- name
- portfolio-status
- description
- Roll up the portfolio from _log.yaml — risk distribution, upcoming deadlines, stale matters, materiality totals, stage distribution, and flagged anomalies. Use when the user asks "where do we stand", "how many open matters", or wants a portfolio rollup or status across all active matters.
- argument-hint
- [--all | --risk=high | --stale]
03 SKILL.md 正文
/portfolio-status
- Load
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md→ risk calibration (defines how to read therisk:field). - Follow the workflow and reference below.
- Parse
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml. Filter closed matters by default (include with--all). - Produce rollup: risk distribution, deadlines in next 14/30/60 days, matters with no update in >30 days, materiality totals, stage distribution.
- Flag anomalies — everything marked critical, overdue next_deadline, matters without outside counsel assigned where risk is medium or high.
Portfolio Status
Purpose
One read that answers: what do I own right now, what needs attention, and what's slipping? Output is scannable — designed for a counsel who has three minutes before their next call.
Load context
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml— source of truth~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md— risk calibration (to interpret risk/materiality fields correctly)
Flags & filters
Default: active matters only (exclude status: closed).
Flags:
--all— include closed--risk=high(orcritical/medium/low) — filter by risk band--stale— only matters withlast_updated> 30 days--type=employment— filter by matter type--owner=[name]— filter by business/HR/comms owner
The rollup
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
# Portfolio Status — [today]
**Active matters:** [N]
**Closed (ytd):** [N] *(shown only with --all)*
---
## By risk
| Risk | Count | Matters |
|---|---|---|
| Critical | [N] | [slugs] |
| High | [N] | [slugs] |
| Medium | [N] | [count only — expand with `--risk=medium`] |
| Low | [N] | [count only] |
## Upcoming deadlines
| Within | Matters |
|---|---|
| 14 days | [slug — deadline — brief] |
| 15–30 days | [...] |
| 31–60 days | [...] |
*Overdue `next_deadline` flagged separately below.*
## Materiality
| Category | Count | Total exposure (midpoint) |
|---|---|---|
| Reserved | [N] | [$X] |
| Disclosed | [N] | [$X] |
| Monitored | [N] | — |
| None | [N] | — |
## By stage
[table: pleadings / discovery / dispositive motions / trial prep / settlement / appeal]
---
## ⚠️ Anomalies & flags
- **Overdue deadlines:** [list slugs where next_deadline has passed]
- **Stale (>30d no update):** [list]
- **Conflicts unresolved:** [list slugs with `conflicts.status in [pending, not-run]`]
- **Conflicts bypassed (override active):** [list slugs where `conflicts.override.by` is populated — permanent flag until manually cleared]
- **High/critical risk without outside counsel:** [list]
- **Reserved without last_updated in >60d:** [list] — reserve recalibration likely overdue
- **Hold not issued on active litigation:** [list]
- **Missing fields:** [slug → field]
---
## Closing advice
[One or two sentences on what to look at first, if anything stands out. Not boilerplate — only if something truly stands out.]
Anomaly rules
These are the checks that make the skill useful rather than decorative:
- Overdue deadline:
next_deadline < todayandstatus != closed - Stale:
last_updated < today - 30dandstatus != closed - Conflicts unresolved:
conflicts.status in [pending, not-run]andstatus != closed3b. Conflicts override active:conflicts.override.by != null(never auto-clears) - High-risk uncovered:
risk in [high, critical]andoutside_counsel.firm == null - Stale reserve:
materiality == reservedandlast_updated < today - 60d - Hold gap:
status in [threatened, active, discovery, trial, appeal]andlegal_hold.issued == false— preservation duty attaches at reasonable anticipation, sothreatenedmatters are in scope. - Missing fields: any required field null —
risk,materiality,status,opened,conflicts.status
Close with the next-steps decision tree
End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.
If the portfolio has more than ~10 matters, or any time the user asks: offer the dashboard (see CLAUDE.md ## Outputs → Dashboard offer for data-heavy outputs). Shape the offer for this output — counts by risk tier, a timeline of upcoming deadlines, and a sortable matter ledger with status, conflicts check, and last-touched date.
What this skill does not do
- Make decisions. It surfaces what needs attention; the user decides priority.
- Pretend precision it doesn't have. Exposure midpoints are rough and should be labeled so.
- Replace a real MMS. This is a working-memory rollup, not a system of record.
04 同仓库更多 Skills
reg-feed-watcher
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
policy-redraft
Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.
policy-diff
Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.
matter-workspace
Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.
gaps
Open gaps tracker — what's flagged and not yet closed. Use when the user asks "what gaps are open", "gap tracker", "remediation status", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.