Loading...
Loading...
Run /check-onboarding, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-onboarding instead if you want to fix issues immediately.
npx skill4agent add phrazzld/claude-config log-onboarding-issues/check-onboarding/fix-onboarding/check-onboardinggh issue list --state open --label "domain/onboarding" --limit 50gh issue create \
--title "[P0] No onboarding flow - users dropped into empty app" \
--body "$(cat <<'EOF'
## Problem
After signup, users land on an empty dashboard with no guidance. They don't know what to do first.
## Impact
- High drop-off after signup
- Users never experience core value
- Support tickets asking "how do I start?"
- Lost users who never return
## Suggested Fix
Run `/fix-onboarding` or implement:
1. **First-run detection:**
```typescript
const isNewUser = !user.hasCompletedOnboarding;
if (isNewUser) redirect('/onboarding');/log-onboarding-issues
### 4. Issue Format
**Title:** `[P{0-3}] Onboarding issue`
**Labels:**
- `priority/p0` | `priority/p1` | `priority/p2` | `priority/p3`
- `domain/onboarding`
- `type/enhancement` | `type/bug`
**Body:**
```markdown
## Problem
What's broken in new user experience
## Impact
Effect on activation and retention
## Suggested Fix
Code snippet, pattern, or skill to run
---
Created by `/log-onboarding-issues`| Gap | Priority |
|---|---|
| No onboarding flow | P0 |
| Broken auth callback | P0 |
| Paywall before value | P0 |
| No empty states | P1 |
| No first-action guidance | P1 |
| Complex initial forms | P1 |
| No loading states | P1 |
| No progressive disclosure | P2 |
| No tooltips/hints | P2 |
| No tour option | P2 |
| Retention hooks missing | P3 |
Onboarding Issues Created:
- P0: 1 (no onboarding flow)
- P1: 4 (empty states, guidance, forms)
- P2: 3 (progressive disclosure, hints)
- P3: 2 (notifications, email capture)
Total: 10 issues created
View: gh issue list --label domain/onboarding/check-onboarding/fix-onboarding/cro/groom