Claude Skill

portfolio-governance

Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everyt

LLM Mart · 0 points · 23 views 0 listing impressions 0 install-command copies
Download cbrock84-headcount-plugins_pmo_skills_portfolio-governance-98d1c17.zip · 2 KB
This skill couldn't be refreshed from GitHub on the last check — you're seeing the last imported snapshot.

Install

skills CLI npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/portfolio-governance
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cbrock84-headcount@llmmart
Git git clone https://github.com/cbrock84/headcount.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole cbrock84/headcount collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Portfolio governance

The portfolio question is not which projects are good. Most proposed work is defensible in isolation. It is which projects the organization can actually finish, given that finishing is what produces value and starting produces none.

Intake as a real gate

Without a single front door, work enters through relationships and volume, and the portfolio becomes the sum of who asked most persistently.

Require the same minimum from every proposal regardless of who is asking: the outcome sought, the evidence it matters, a rough size, the accountable owner, and what will not happen if it proceeds. That last one is the honest part — capacity is fixed, so approving anything is declining something else, whether or not the decline is ever stated.

Prioritize against capacity, not against merit

Ranking by value produces a list where everything above the line is approved and the line is imaginary. Prioritization only means something when the cut is made at real, measured delivery capacity — see operations:capacity-and-demand-planning for the throughput side.

Limit work in progress. An organization running twenty concurrent initiatives with capacity for eight does not deliver twenty slowly; it delivers roughly eight, considerably later, with the overhead of context-switching across all twenty. Fewer things, finished, is faster in wall-clock terms — which is counter-intuitive and is why the discipline requires governance rather than good intentions.

Stage gates that can say no

A gate whose only outcome is approval is a status meeting. Each gate must be able to stop, pause, or redirect, and needs a named decision-maker with the authority to do it.

Gate on what has been learned since the last one, not on whether documentation was produced. The useful question is whether the case still holds now that more is known — and it frequently does not, which is exactly the information the gate exists to surface.

Stopping is the hardest and most valuable act

Organizations start well and stop badly. Sunk cost, sponsor prestige and the discomfort of admitting error keep dead projects consuming capacity that the whole portfolio needs.

Make stopping a normal, non-punitive outcome. Where stopping is treated as failure, projects are never stopped — they are quietly starved, which is the same cost with none of the released capacity and no decision anyone can point to.

Resource contention

Contention across projects is resolved here, at the portfolio, not by the projects negotiating among themselves. Left to negotiation, the outcome reflects seniority of the sponsors rather than value to the organization.

Watch for the same scarce specialist appearing on the critical path of several initiatives — the most common invisible cause of portfolio-wide slippage.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Approve work without naming what it displaces.
  • Set a priority order without a line drawn at real capacity.
  • Run a gate that cannot stop anything.
  • Starve a project instead of stopping it.
Files (headcount)
  • references
    • sources.md 1.8 KB
      Loading…
  • SKILL.md 3.7 KB
    ---
    name: portfolio-governance
    description: Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.
    ---
    
    # Portfolio governance
    
    The portfolio question is not which projects are good. Most proposed work is defensible in isolation.
    It is which projects the organization can actually finish, given that finishing is what produces
    value and starting produces none.
    
    ## Intake as a real gate
    
    Without a single front door, work enters through relationships and volume, and the portfolio becomes
    the sum of who asked most persistently.
    
    Require the same minimum from every proposal regardless of who is asking: the outcome sought, the
    evidence it matters, a rough size, the accountable owner, and what will not happen if it proceeds.
    That last one is the honest part — capacity is fixed, so approving anything is declining something
    else, whether or not the decline is ever stated.
    
    ## Prioritize against capacity, not against merit
    
    Ranking by value produces a list where everything above the line is approved and the line is
    imaginary. Prioritization only means something when the cut is made at real, measured delivery
    capacity — see `operations:capacity-and-demand-planning` for the throughput side.
    
    **Limit work in progress.** An organization running twenty concurrent initiatives with capacity for
    eight does not deliver twenty slowly; it delivers roughly eight, considerably later, with the
    overhead of context-switching across all twenty. Fewer things, finished, is faster in wall-clock
    terms — which is counter-intuitive and is why the discipline requires governance rather than good
    intentions.
    
    ## Stage gates that can say no
    
    A gate whose only outcome is approval is a status meeting. Each gate must be able to stop, pause, or
    redirect, and needs a named decision-maker with the authority to do it.
    
    Gate on what has been learned since the last one, not on whether documentation was produced. The
    useful question is whether the case still holds now that more is known — and it frequently does not,
    which is exactly the information the gate exists to surface.
    
    ## Stopping is the hardest and most valuable act
    
    Organizations start well and stop badly. Sunk cost, sponsor prestige and the discomfort of admitting
    error keep dead projects consuming capacity that the whole portfolio needs.
    
    Make stopping a normal, non-punitive outcome. Where stopping is treated as failure, projects are
    never stopped — they are quietly starved, which is the same cost with none of the released capacity
    and no decision anyone can point to.
    
    ## Resource contention
    
    Contention across projects is resolved here, at the portfolio, not by the projects negotiating among
    themselves. Left to negotiation, the outcome reflects seniority of the sponsors rather than value to
    the organization.
    
    Watch for the same scarce specialist appearing on the critical path of several initiatives — the
    most common invisible cause of portfolio-wide slippage.
    
    ## Sources
    
    `references/sources.md` in this skill lists the outside authorities that settle the questions
    here — what each one is authoritative for, and what you may do with it. Check them before
    answering on anything they cover, and cite what you used. Most are free to read and not free
    to reproduce; the use note on each is binding.
    
    ## Never
    
    - Approve work without naming what it displaces.
    - Set a priority order without a line drawn at real capacity.
    - Run a gate that cannot stop anything.
    - Starve a project instead of stopping it.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.