mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-11 19:47:12 +03:00
Magnus HedemarkGitHubusername <username>factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>* feat(product-lifecycle-learning): add product lifecycle learning skill (#194) Introduce a new skill to close the launch-to-learning loop for product features and capabilities. Covers: - Post-launch outcome review with explicit epistemic categories (expected/observed/uncertain/inferred) - Assumption ledger updates with confidence shifts - Multi-dimensional feature health assessment - Six lifecycle decisions: continue/improve/harvest/pivot/pause/retire - Full retirement lifecycle: deprecation communication, migration paths, customer treatment during sunset, and internal cleanup - Durable retained learning records that feed back into roadmap, analytics, adoption, experimentation, and specifications Ships 4 references (discovery brief, epistemic discipline, retirement lifecycle, feedback destinations), 6 templates (outcome review, assumption ledger update, feature health record, retirement decision, sunset plan, retained learning record), and 7 eval cases including adversarial coverage. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * fix(product-lifecycle-learning): regenerate marketplace with corrected description The Claude marketplace JSON contained the original description starting with "Close" which was replaced with "Compare" to satisfy the imperative-verb quality check. Regenerate to match the corrected SKILL.md frontmatter. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * fix(product-lifecycle-learning): regenerate llms.txt with corrected description Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> --------- Co-authored-by: username <username> Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
1.8 KiB
1.8 KiB
Assumption Ledger Update
Update the assumption ledger with evidence from the outcome review. For each assumption that drove the feature, record whether it held, weakened, or broke, and adjust confidence accordingly.
Feature Identity
| Field | Value |
|---|---|
| Feature / capability name | |
| Prior assumption ledger date | |
| Update date | |
| Updater |
Assumption Updates
For each assumption in the prior ledger, record the evidence from the outcome review and the confidence shift.
| # | Assumption | Prior confidence | Evidence from outcome review | Held / Weakened / Broke | New confidence | Notes |
|---|---|---|---|---|---|---|
| 1 | High / Medium / Low | High / Medium / Low | ||||
| 2 | ||||||
| 3 |
New Assumptions Surfaced
What new assumptions did the outcome review surface that were not in the prior ledger?
| # | New assumption | Trigger (what observation surfaced this) | Initial confidence | Should this be tested? |
|---|---|---|---|---|
| 1 | High / Medium / Low | Yes / No | ||
| 2 |
Assumptions to Retire
Which prior assumptions are no longer relevant and should be removed from the active ledger?
| # | Assumption | Reason for retirement |
|---|---|---|
| 1 | ||
| 2 |
Ledger Health
- Total assumptions (active):
- High-confidence assumptions:
- Assumptions that weakened or broke this cycle:
- Assumptions overdue for re-examination (no update in >2 cycles):
- Blind spots: (areas where we have no assumptions but probably should)
Routing
- Updated assumptions routed to roadmap (product-roadmapping-and-portfolio)
- Testable new assumptions routed to experimentation (product-experimentation)
- Measurement-gap assumptions routed to analytics (product-analytics-and-measurement)