BF product-lifecycle-learning
Compare intended product outcomes against observed results to close the launch-to-learning loop: collect post-launch evidence, distinguish expected from observed from uncertain from inferred claims, update assumptions, assess feature health, and choose among continue/improve/harvest/pivot/pause/retire — including retirement lifecycles with deprecation, migration, customer treatment, and retained reusable learning. Do not use for incident postmortems or root-cause analysis (routes to incident-learning or site-reliability-engineering); do not use for analytics instrumentation or metric dashboard design (routes to product-analytics-and-measurement); do not use arbitrary thresholds as universal retirement rules — decisions require human judgment and context.
Compare intended product outcomes against observed results to close the launch-to-learning loop: collect post-launch evidence, distinguish expected from…
As a process F 48/100 · Will not run — References files that are not bundled: ../site-reliability-engineering/SKILL.md, ../product-analytics-and-measurement/SKILL.md, ../product-roadmapping-and-portfolio/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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../site-reliability-engineering/SKILL.md - warning
missing-refreference to a missing file: ../product-analytics-and-measurement/SKILL.md - warning
missing-refreference to a missing file: ../product-roadmapping-and-portfolio/SKILL.md - warning
missing-refreference to a missing file: ../spec-driven-development/SKILL.md - warning
missing-refreference to a missing file: ../product-adoption/SKILL.md - warning
missing-refreference to a missing file: ../product-experimentation/SKILL.md
Process rating: all ten parameters 48/100
- 0Tools and files. 6 referenced file(s) missing: ../site-reliability-engineering/SKILL.md, ../product-analytics-and-measurement/SKILL.md, ../product-roadmapping-and-portfolio/SKILL.md
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4401 tokens
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 764: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.