Design onboarding flows that guide users to value quickly without being annoying.
/onboarding-flow-designer1-2 days → 15 min
Compared to doing it manually
/onboarding-flow-designerType this in Claude to run the skill
New users sign up but do not stick around. They are not getting to the aha moment fast enough.
.claude/skills/ folder in your project/onboarding-flow-designer in Claude to run the skill/one-pager-creatorCreate compelling one-page feature briefs that align stakeholders quickly.
/product-brief-writerWrite one-page product briefs to get buy-in before investing in full specs.
/user-story-writerWrite clear user stories with acceptance criteria following the INVEST principles.
/technical-spec-writerWrite technical specifications with architecture, data models, and API designs.
Good onboarding gets users to their "aha moment" fast. Focus on one key action, reduce friction, show value before asking for commitment. Measure time-to-value and activation rate, not completion rate.
As short as possible while still enabling success. Progressive disclosure works better than front-loading. Show users what they need now, teach advanced features later. Most users won't complete long onboarding flows.
Onboarding is the process (tours, tutorials, setup). Activation is the outcome (user experiences core value). You can complete onboarding without activating. Focus on activation metrics, not onboarding completion.
Run this skill inside your PM Operating System, or download it on its own.
Use all 70 skills, workflows, and sub-agents in a system that knows your company, product, and customers.