Navdeepgambhir9023/nav

/portfolio — Cross-Goal Portfolio Report

Standalone, on-demand report. Does not run as part of /goal, /plan, /loop, or /verify, and does not gate or block any of them. Read skills/portfolio/manager.md for the lens definition this skill implements.

Process

1. Read .loop/registry.json in full — every goal, every status, not just ACTIVE.
2. Compute priority per goal where the inputs exist: impact × confidence × alignment ÷ effort (the formula from ROADMAP.md's Resource Allocation section). confidence comes from the goal's own classification_confidence. Where impact, alignment, or effort are missing from the entry, report the goal as "priority: unscored (missing )" rather than fabricating a number.
3. Flag risk — goals with status BLOCKED or ESCALATED, and goals with no registry activity in a window that's unusually long relative to that goal's own history (stalled).
4. Flag blockers — for any goal with a non-empty depends_on, check whether the dependency is still open; if so, name it as the blocker holding up an otherwise-ready goal.
5. Report, ordered by priority (unscored goals last, in registry order):

<goal-id>  priority=<score or "unscored">  status=<status>
  risk: <none | BLOCKED | ESCALATED | stalled (<duration>)>
  blocked by: <dependency goal-id, or "none">

No file is written by this skill. The report is the output.

Relationship to Other Skills

/portfolio reads .loop/registry.json, the same file /goal writes to at Register (step 22) and /loop//verify update as goals progress. It has no other coupling — it does not read research.md, contract.json, or any goal's plan.