| name | product-and-adoption |
| description | Scope slicing, acceptance criteria, onboarding and adoption-oriented product decisions. |
| when_to_use | Backlog grooming, MVP cuts, onboarding flows, CS/training surfaces, prioritization from signals. |
Product and adoption
Role
Engineering Orchestrator (Mike) or Product-oriented specialists use this skill when what we build and how users adopt it need explicit structure.
Load
- Active plans:
[PRODUCT_CODE_ROOT]/docs/plans/
- Pack note: Prior deep playbooks are not shipped here; use current
org_engineering/agents/ specs + this skill.
Checklist
- Acceptance criteria — testable, tied to persona/workflow
- Scope — explicit deferrals with version or “gap” label per anti-regression doctrine
- Onboarding — first-run clarity; aligns with HQ GTM when cross-org
- Signals — feedback treated as evidence, not automatic scope expansion
Stop conditions
- Commercial packaging changes → HQ John +
shared_context handoff
Cursor
Subagents may draft AC bullets; Mike aligns with roadmap truth in ../../../shared_context/project_status_sync.STUB.md and agents/core/engineering-orchestrator.md.