Files
magnus919_agent-skills/product-operations-and-governance/templates/review-cadence.md
T
Magnus HedemarkGitHubusername <username>factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
77562664b8 feat(product-operations-and-governance): add product operations and governance skill (#216)
Add a new skill for product governance — recurring decision rights, intake,
portfolio cadences, evidence standards, and cross-functional operating
contracts. Covers six review cadences with named accountable owners,
minimum evidence standards per decision type, and escalation paths.

Supports lightweight (small teams, minimal ceremony) and high-assurance
(regulated/safety-critical) operating modes with four configurable
governance patterns. Distinguishes product governance from executive
governance (routes to chief-of-staff-methodology, strategy-frameworks) and
technical delivery gates (routes to release-engineering, spec-driven-development).

Includes: SKILL.md with governance boundary statement, README.md,
discovery brief, 5 fillable templates (operating model, decision-rights map,
review cadence, exception record, escalation record), 6 evals covering
lightweight mode, high-assurance, contested decisions, exceptions,
evidence-missing escalation, and an adversarial case.

Closes #193

Co-authored-by: username <username>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
2026-08-02 17:27:16 -04:00

5.7 KiB

Review Cadence Configuration

Fill one section per review type. Each review has a defined purpose, participants, inputs, outputs, and decision authority. Frequency and formality scale with the operating mode.

Context

  • Product / portfolio: [fill]
  • Operating mode: [fill: lightweight / high-assurance]
  • Date: [fill]

Intake / Opportunity Review

  • Purpose: Decide which new proposals, requests, or opportunities enter the product system for further evaluation.
  • Frequency: [fill: e.g., "weekly (lightweight)" or "continuous with weekly triage (high-assurance)"]
  • Participants:
    • Required: [fill: roles]
    • Optional: [fill: roles]
  • Inputs:
    • [fill: e.g., "Problem statement or opportunity brief"]
    • [fill: e.g., "Strategic alignment check (high-assurance)"]
    • [fill: e.g., "Rough sizing or capacity impact"]
  • Outputs:
    • [fill: e.g., "Accept / Reject / Defer decision with rationale"]
    • [fill: e.g., "Assigned owner for accepted items"]
    • [fill: e.g., "Deferral revisit date (if deferred)"]
  • Decision authority: [fill: e.g., "Product Lead decides; council vote for contested items"]
  • Quorum (high-assurance only): [fill: minimum attendees for valid review]
  • Mode-specific notes: [fill: any differences between lightweight and high-assurance execution]

Portfolio Review

  • Purpose: Sequence and resource-allocate across the portfolio of bets; make trade-off decisions when capacity is constrained.
  • Frequency: [fill: e.g., "monthly" or "quarterly"]
  • Participants:
    • Required: [fill]
    • Optional: [fill]
  • Inputs:
    • [fill: e.g., "All active bet records with updated confidence, evidence, and dependencies"]
    • [fill: e.g., "Capacity model (team-weeks available per period)"]
    • [fill: e.g., "Strategic priorities from executive governance"]
  • Outputs:
    • [fill: e.g., "Prioritized portfolio: Now / Next / Later with rationale"]
    • [fill: e.g., "Resource allocation decisions"]
    • [fill: e.g., "Deferred or deprioritized bets with rationale"]
  • Decision authority: [fill]
  • Quorum (high-assurance only): [fill]
  • Mode-specific notes: [fill]

Roadmap Review

  • Purpose: Review evidence updates for committed roadmap items; decide continue, pause, kill, or revisit.
  • Frequency: [fill: e.g., "bi-weekly (lightweight)" or "weekly (high-assurance)"]
  • Participants:
    • Required: [fill]
    • Optional: [fill]
  • Inputs:
    • [fill: e.g., "Updated bet records with new evidence"]
    • [fill: e.g., "Dependency status updates"]
    • [fill: e.g., "Stakeholder feedback or market signals"]
  • Outputs:
    • [fill: e.g., "Updated Now/Next/Later"]
    • [fill: e.g., "Continue / Pause / Kill / Revisit decisions per bet"]
    • [fill: e.g., "Roadmap communication for stakeholders"]
  • Decision authority: [fill]
  • Quorum (high-assurance only): [fill]
  • Mode-specific notes: [fill]

Experiment Review

  • Purpose: Review experiment results; decide whether evidence supports proceeding, iterating, or stopping.
  • Frequency: [fill: e.g., "per experiment completion" or "weekly for active experiments"]
  • Participants:
    • Required: [fill]
    • Optional: [fill]
  • Inputs:
    • [fill: e.g., "Experiment readout with statistical analysis (high-assurance) or qualitative signal (lightweight)"]
    • [fill: e.g., "Guardrail report — all guardrail metrics within bounds?"]
    • [fill: e.g., "Decision recommendation from experiment owner"]
  • Outputs:
    • [fill: e.g., "Proceed / Stop / Iterate decision with rationale"]
    • [fill: e.g., "Updated bet record with experiment outcome"]
    • [fill: e.g., "Escalation if results are ambiguous and decision is contested"]
  • Decision authority: [fill]
  • Quorum (high-assurance only): [fill]
  • Mode-specific notes: [fill]

Launch Review

  • Purpose: Confirm readiness to ship; accept residual risk; make the go/no-go/defer call.
  • Frequency: [fill: e.g., "per launch" or "weekly launch window"]
  • Participants:
    • Required: [fill: e.g., "Product Lead, Engineering Lead, QA Lead, Security (high-assurance), Support Lead"]
    • Optional: [fill]
  • Inputs:
    • [fill: e.g., "Readiness evidence packet (checklist, test results, performance data)"]
    • [fill: e.g., "Risk register with accepted and unaccepted risks"]
    • [fill: e.g., "Rollback plan verified"]
    • [fill: e.g., "Support readiness and communication plan"]
  • Outputs:
    • [fill: e.g., "Go / No-Go / Defer decision"]
    • [fill: e.g., "Accepted risks with owners and revisit triggers"]
    • [fill: e.g., "Launch communication"]
  • Decision authority: [fill: e.g., "Product Lead for go/no-go; risk acceptance above threshold requires exec sign-off"]
  • Quorum (high-assurance only): [fill]
  • Mode-specific notes: [fill]

Lifecycle / Health Review

  • Purpose: Assess product health; decide continue-as-is, increase investment, harvest, or retire.
  • Frequency: [fill: e.g., "quarterly" or "per major release cycle"]
  • Participants:
    • Required: [fill]
    • Optional: [fill: e.g., "Finance (high-assurance), Support Lead, Sales Lead"]
  • Inputs:
    • [fill: e.g., "Usage data (DAU/MAU, retention, adoption)"]
    • [fill: e.g., "Outcome metrics vs. expected"]
    • [fill: e.g., "Cost data (infrastructure, support, engineering allocation)"]
    • [fill: e.g., "Competitive intelligence and market signals"]
  • Outputs:
    • [fill: e.g., "Lifecycle decision: Continue / Invest / Harvest / Retire"]
    • [fill: e.g., "Updated investment level and resource allocation"]
    • [fill: e.g., "Migration or customer communication plan (if retiring)"]
  • Decision authority: [fill: e.g., "Product Council recommends; executive sponsor approves retire decisions"]
  • Quorum (high-assurance only): [fill]
  • Mode-specific notes: [fill]