* test(evals): scope claims to harness model fixtures and revision Append the neckbeard claims-scoping sentence to one representative expected_output per per-skill manifest so every corpus member states VAL-EVL-032 scope (harness, model, fixtures, revision under test). Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * test(product-lifecycle): upgrade integrated launch trajectory Add an explicit launch-decision assertion to the new-product lifecycle case so the integrated product-launch scenario terminates in a launch decision recorded as a lifecycle evidence-ledger entry (VAL-CRP-010), and scope its expected_output claims per VAL-EVL-032. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * test(production-excellence): add integrated migration reconciliation failure case Add integrated-migration-reconciliation-failure: the production-excellence gate model returns No-go on a reconciliation mismatch, records the failure evidence, produces a rollback/roll-forward decision with an accountable owner, and does not proceed to launch (VAL-CRP-012). Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * test(agent-production-operations): add privacy boundary escalation case Add integrated-privacy-boundary-escalation (VAL-CRP-015): the runtime control plan halts a cross-boundary EU PII trace export before any data processing, names the privacy boundary, and escalates to jurisdiction- specific legal review and a human operator. Also add a tool-authority- health handoff assertion to the read-only contract case (VAL-CRP-016). Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * test(lifecycle-evals): add lifecycle evaluation corpus Add the #204 corpus home: run tooling (run-corpus.sh, fake adapter only), programmatic coverage validator (validate-corpus-coverage.py), machine- readable coverage index + human-readable coverage matrix, regression- detection and fixture/source notes, the bounded discovery brief, and a one-snapshot committed set of fake-adapter per-trial run artifacts with harness/model/date scoping fields. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> --------- Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Product Adoption
Diagnose and design product adoption — onboarding, activation, behavior change, feature discovery, rollout segmentation, and sustained use — for consumer, B2B, internal-tool, and public-service products.
Why Install This Skill
Your agent can design an adoption plan anchored in evidence rather than marketing assumptions. It distinguishes acquisition, activation, adoption, retention, and expansion as separate stages with different owners and interventions. It knows when to pause a rollout based on cohort activation evidence — and when to stop an adoption effort entirely and feed that decision into lifecycle learning.
This skill works for products that are not SaaS subscriptions: internal tools, public services, consumer apps, and non-subscription B2B products. It does not assume NPS, conversion rates, or MRR benchmarks are universal.
What You Get
| Directory | Purpose |
|---|---|
| SKILL.md | Core methodology: adoption pipeline, evidence-based decision points, routing |
| references/discovery-brief.md | Bounded discovery: maps existing GTM/acquisition material, ownership boundaries |
| references/adoption-lifecycle-concepts.md | Acquisition, activation, adoption, retention, expansion definitions |
| references/non-saas-adoption-contexts.md | Internal tools, public services, consumer, B2B non-SaaS patterns |
| references/behavior-change-and-education.md | Behavior-change frameworks, in-product education, accessibility-first design |
| templates/adoption-plan.md | End-to-end adoption plan with evidence gates and pause/stop criteria |
| templates/activation-time-to-value-diagnostic.md | Structured diagnostic for low activation or long time-to-value |
| templates/segmentation-and-rollout-record.md | Cohort segmentation and phased rollout tracking |
| templates/sustained-use-review.md | Post-launch review of adoption health |
Quick Start
Load SKILL.md for the methodology overview and file map, then load specific
references and templates as the situation demands.
Triggers
- Diagnosing low activation, slow time-to-value, or poor feature discovery
- Designing an adoption, onboarding, or rollout plan
- Segmenting users into rollout cohorts with evidence-based progression gates
- Reviewing sustained use after launch
- Designing in-product education, behavior-change interventions, or accessibility-aware flows
- Working with internal tools, public services, or non-SaaS products
Requirements
No technical dependencies. Behavioral frameworks from Fogg Behavior Model, COM-B, and evidence-based education design. Consumes adoption evidence from product analytics but does not own instrumentation.