Magnus HedemarkGitHubusername <username>factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>* feat(product-adoption): add product adoption skill Add product-adoption skill for diagnosing and designing product adoption across consumer, B2B, internal-tool, and public-service contexts. - SKILL.md with adoption pipeline (acquisition, activation, adoption, retention, expansion), evidence-based decision points, non-SaaS support, routing to go-to-market and prose references to not-yet-landed skills - README.md with 5 required human-facing sections - references/: discovery-brief.md, adoption-lifecycle-concepts.md, non-saas-adoption-contexts.md, behavior-change-and-education.md - templates/: adoption-plan.md, activation-time-to-value-diagnostic.md, segmentation-and-rollout-record.md, sustained-use-review.md - evals/evals.json with 7 output-quality cases covering internal tool, public service, low feature discovery, enterprise cohort rollout, pause-expansion evidence, and anti-trigger acquisition/instrumentation routing - Updated root README.md catalog section, references/skill-triggers.md, and regenerated catalogs Closes #191 Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * fix(product-adoption): add missing SKILL.md and README.md Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * chore(product-adoption): regenerate catalogs 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>
3.0 KiB
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.