BF product-operations-and-governance
Define and run product governance — recurring decision rights, intake, portfolio cadences, evidence standards, and cross-functional operating contracts. Covers six review cadences (intake, portfolio, roadmap, experiment, launch, lifecycle) with named accountable owners, minimum evidence standards per decision type, and escalation paths. Supports lightweight and high-assurance operating modes with configurable governance patterns. Use when designing a product governance model, resolving contested decisions, establishing evidence standards, recording exceptions and escalations, or building cross-functional operating contracts. Do NOT use for executive governance (capital allocation, org structure — route to chief-of-staff-methodology or strategy-frameworks), for technical delivery gates (CI/CD, release approval — route to release-engineering or spec-driven-development), or to impose a universal org chart.
Define and run product governance — recurring decision rights, intake, portfolio cadences, evidence standards, and cross-functional operating contracts.
As a process F 49/100 · Will not run — References files that are not bundled: ../chief-of-staff-methodology/SKILL.md, ../strategy-frameworks/SKILL.md, ../release-engineering/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../chief-of-staff-methodology/SKILL.md - warning
missing-refreference to a missing file: ../strategy-frameworks/SKILL.md - warning
missing-refreference to a missing file: ../release-engineering/SKILL.md - warning
missing-refreference to a missing file: ../spec-driven-development/SKILL.md - warning
missing-refreference to a missing file: ../product-roadmapping-and-portfolio/SKILL.md - warning
missing-refreference to a missing file: ../product-experimentation/SKILL.md - warning
missing-refreference to a missing file: ../product-strategy/SKILL.md - warning
missing-refreference to a missing file: ../product-methodology/SKILL.md - warning
missing-refreference to a missing file: ../technical-program-management/SKILL.md
Process rating: all ten parameters 49/100
- 0Tools and files. 9 referenced file(s) missing: ../chief-of-staff-methodology/SKILL.md, ../strategy-frameworks/SKILL.md, ../release-engineering/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 8 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3776 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 916: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 21 headings
- +3Step-by-step instructions: 15 items
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.