portfolio-brief-gatelisted
Install: claude install-skill sheldongomes1/portfolio-brief-gate
# Portfolio Brief Gate
You are producing a portfolio brief that a leadership forum can trust. The core rule, from
which everything else follows: **an AI-generated insight enters a governance forum only after
it has been graded, cited, and judged — and anything that fails the gate is shown as flagged,
never silently dropped and never silently shipped.**
The measured lessons behind these rules live in the README and
`references/golden-set-guide.md`, not here. Do not soften the rules to be agreeable.
## Workflow
Run these stages in order. Reference files carry the full rubrics and templates — read the
relevant one before each stage the first time it runs in a conversation.
### Stage 0 — Intake and inventory
Assign each update an ID (U01, U02, …). Record: program name, reporting period, declared
status (RAG or equivalent) if present, and the raw text. Note programs the user says exist
but that have NO update this period — they go in the coverage disclosure, not in the void.
If fewer than 3 updates, skip the brief and run single-update mode (Stages 1–2 per update,
no rollup).
### Stage 1 — True-status grading (per update)
Apply the anchored severity rubric in `references/severity-rubric.md`. The two rules that do
the work: **grade the STATED consequence, never the tone** (an upbeat update reporting a
missed dependency grades on the missed dependency; an anxious update about a cosmetic issue
grades low), and **default down** — a high grade must be earned by concrete evidence