foundry-pmo

Plugin foundry-pmo from marketplace foundry in fedcal/foundry. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• forecast-delivery

  Answer "when will this be done" with a probability distribution computed from measured throughput — Monte Carlo over the last 8-12 periods, scope-growth measured rather than assumed away, p50/p85/p95 dates, and a deterministic bracket as a sanity check. Also computes cycle time percentiles, throughp

• github-setup

  Bootstrap repository governance with the gh CLI — label taxonomy, milestones, a Projects v2 board, branch protection or rulesets, issue and PR templates, and required checks. Idempotent, safe to re-run. Use when starting a repository or bringing an existing one under governance. Not for CI pipeline

• groom-backlog

  Run a working grooming session over the real issue tracker — split oversized items with SPIDR, estimate as ranges, order by value density, close stale items, flag anything missing acceptance criteria, and report WIP breaches. Use before a sprint or milestone starts, or whenever the top of the backlo

• jira-setup

  Bring a Jira Cloud project under governance with exact, idempotent REST v3 and Agile API calls — issue type scheme, a workflow whose statuses map cleanly to status categories, the field set including story points and sprint resolved by name, board and sprint configuration, saved JQL filters, and aut

• risk-review

  Run a periodic risk review — re-score existing risk.v1 artifacts, identify new risks with category prompts, check detection signals against real repository data, and escalate everything that crossed its threshold. Use at a milestone gate, on a fixed cadence, or after any event that changed the plan.

• roadmap

  Create or revise a delivery roadmap, producing a plan.v1 artifact plus a human-readable ROADMAP.md. Use when starting a project, planning a quarter, or when a re-planning trigger has fired and the existing roadmap must be revised rather than rewritten. Not for sprint planning or task breakdown.

• run-retrospective

  Facilitate a retrospective that ends with one owned, dated change instead of a list of observations — evidence gathered from the board before opinions are collected, a format chosen for the situation rather than by habit, blameless framing that attacks the system, and a check that last cycle's actio

• run-sprint

  Run one Sprint end to end against the real board — Planning that produces a Sprint Goal before it selects items, a Daily that replans the next 24 hours, a Review that changes the Product Backlog, and a close-out that returns undone work instead of rolling it silently. Each event has an entry gate th

• slack-workflow

  Wire delivery events into Slack without creating a channel nobody reads — channel taxonomy with owners, a suppression policy applied before any integration is built, Block Kit messages that lead with the ask, incident channel protocol, least-privilege bot scopes, and an alert-fatigue audit that meas

• status-report

  Generate a status report from real repository and plan data — burn-up against plan.v1, gate progress with the actual check output, blockers with owners and measured age, and a forecast expressed as a range. Use for a periodic report, a milestone checkpoint, or a stakeholder update. Never assembled f

• sync-tracker

  Detect which issue tracker a project actually uses, read its board, and normalise every item into tracker-item.v1 so flow metrics and sprint reports never touch a provider payload. Covers GitHub Issues, Jira Cloud, Linear and GitLab, resolves state through status categories rather than renameable na

• write-requirements

  Elicit and record requirements as requirement.v1 artifacts with the ambiguity checklist applied — story mapping, Given/When/Then acceptance criteria, measurable non-functional targets, and requirement-to-test traceability. Use before planning or building anything whose success criteria are not yet w

Subagents (10)

• backlog-manager

  Use to keep a backlog healthy — splitting oversized items with SPIDR, enforcing definition of ready and definition of done, applying WIP limits, retiring ageing items, detecting duplicates, and rejecting anything without acceptance criteria. Works over the real issue tracker via gh. Do not use for r

• delivery-reporter

  Use to produce a status report a stakeholder can act on — progress against plan.v1 read from real repository data, burn-up rather than burn-down, blockers with named owners and ageing, and a forecast expressed as a confidence range. Reports bad news early and plainly. Do not use for planning, re-seq

• flow-analyst

  Use to measure delivery empirically and forecast from history rather than from hope — cycle time and its distribution, throughput, work in progress, Little's Law, cumulative flow, ageing work in progress, DORA's four keys, and Monte Carlo forecasting over past throughput instead of a velocity multip

• github-operator

  Use to run a GitHub repository through the gh CLI — label taxonomy, milestones, Projects v2 fields and views, branch protection and rulesets, issue and PR templates, required checks, automation workflows, and release publication. Every action is an exact, idempotent gh command. Do not use for writin

• requirements-analyst

  Use to turn stakeholder intent into verifiable requirement.v1 artifacts — user story mapping, Given/When/Then acceptance criteria, non-functional requirements with measurable targets, requirement-to-test-to-release traceability, and ambiguity detection that refuses words like "fast", "secure" or "us

• risk-manager

  Use to build and maintain a risk register that is actually used — category-driven identification prompts, probability x impact quantified in money and time, mitigations with a named owner and a review date, detection signals, and escalation thresholds that fire automatically. Emits risk.v1. Do not u

• roadmap-planner

  Use to build or revise a delivery roadmap that survives contact with reality — outcome-framed milestones with exit criteria, dependency and critical-path analysis, capacity-based sequencing, an explicit "not now" list, and named re-planning triggers. Emits plan.v1. Do not use for sprint-level task b

• scrum-facilitator

  Use to run or repair the Scrum events as the 2020 Scrum Guide defines them — Sprint Planning topics one/two/three, the Daily as a plan for the next 24 hours, Sprint Review as a working session with stakeholders, and the Retrospective as a commitment to one change. Diagnoses the named anti-patterns (

• slack-operator

  Use to make Slack a working surface for delivery rather than a notification dump — channel taxonomy and naming, which events deserve a message and which do not, incident channel protocol, thread discipline, Block Kit message design, app scopes and least privilege, and retention and export implicatio

• tracker-operator

  Use to read and mutate an issue tracker through one provider-independent interface — GitHub Issues, Jira Cloud, Linear or GitLab — detecting which provider a project actually uses, normalising every item into tracker-item.v1, and expressing each mutation as an exact idempotent command or API call. O

Similar plugins