activation-path
Activation Path
Reduce unnecessary commitment while preserving identity, security, consent, and data integrity, then design the minimum path to experienced value. Product tours are not a substitute for a coherent workflow, and account creation is not activation.
If .agents/marketing-context.md exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read signup-workflow.md for field review, flow choice, trust, mobile, and post-submit states. Read activation-workflow.md for activation models, the minimum path, components, recovery, and experiments.
Operating contract
- Define eligible users, entry sources, the intended account state, security requirements, the observable activation behavior, baseline, and downstream retention.
- Inspect every step, field, alternative sign-in path, validation, error, verification, interruption, prerequisite, first action, first result, and failure path.
- Mark each step required now, safely deferred, automatically inferred, optional, or removable; distinguish motivation, comprehension, trust, technical failure, and avoidable effort.
- Specify the complete revised journey with copy, states, events, assistance, persistence, and channel handoffs.
- Measure downstream retention and quality, not step completion alone; protect fraud controls, privacy, recovery, accessibility, and valid consent.
Do not remove necessary security, trade customer quality for completion rate, force tours, fake completion, or hide required work until late.
Return
Current-flow evidence, activation definition, bottleneck, revised journey, field table, complete interface copy, all states, event contract, recovery paths, dependencies, and the ship or experiment decision.