home / skills / phrazzld / claude-config / log-onboarding-issues

log-onboarding-issues skill

/skills/log-onboarding-issues

This skill audits onboarding, generates prioritized GitHub issues for findings, avoids duplicates, and formats issues for efficient triage and fixing.

npx playbooks add skill phrazzld/claude-config --skill log-onboarding-issues

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.9 KB
---
name: log-onboarding-issues
description: |
  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.
---

# /log-onboarding-issues

Run onboarding audit and create GitHub issues for all findings.

## What This Does

1. Invoke `/check-onboarding` to audit new user experience
2. Parse findings by priority (P0-P3)
3. Check existing issues to avoid duplicates
4. Create GitHub issues for each finding

**This is an issue-creator.** It creates work items, not fixes. Use `/fix-onboarding` to fix issues.

## Process

### 1. Run Primitive

Invoke `/check-onboarding` skill to get structured findings.

### 2. Check Existing Issues

```bash
gh issue list --state open --label "domain/onboarding" --limit 50
```

### 3. Create Issues

For each finding:

```bash
gh 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');
```

2. **Onboarding wizard:**
- Welcome screen
- First action prompt
- Success celebration

3. **Empty state with CTA:**
"Create your first X to get started"

---
Created by `/log-onboarding-issues`
EOF
)" \
  --label "priority/p0,domain/onboarding,type/enhancement"
```

### 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`
```

## Priority Mapping

| 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 |

## Output

After running:
```
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
```

## Related

- `/check-onboarding` - The primitive (audit only)
- `/fix-onboarding` - Fix onboarding issues
- `/cro` - Conversion optimization
- `/groom` - Full backlog grooming

Overview

This skill runs an onboarding audit and creates GitHub issues for every finding, organized by priority. It surfaces gaps in new-user experience so teams can triage and assign work without manually translating audit results into tickets.

How this skill works

It invokes the /check-onboarding primitive to get structured findings, parses each finding into a priority (P0–P3), checks existing open issues to avoid duplicates, and then creates formatted GitHub issues for each unique finding. Issues include a clear Problem, Impact, and Suggested Fix section and are labeled by priority, domain, and type.

When to use it

  • After a new user-experience audit to convert findings into actionable tickets
  • When preparing a backlog for a product/UX sprint focused on activation
  • To ensure consistent issue formatting and labeling for onboarding work
  • Before stakeholder reviews so work items are visible and triage-ready

Best practices

  • Run /check-onboarding first to get structured findings; this skill creates issues, not fixes
  • Review existing domain/onboarding issues to avoid duplicates and consolidate similar findings
  • Classify each finding by priority using the provided P0–P3 mapping to guide triage
  • Include concrete suggested fixes or a pointer to /fix-onboarding when feasible
  • Keep issue bodies concise: Problem, Impact, Suggested Fix, and provenance line

Example use cases

  • Automatically create P0 tickets for critical gaps like missing onboarding flow or broken auth callbacks
  • Bulk-generate issues after a CRO review to hand off to product and engineering
  • Standardize onboarding-related backlog items with consistent labels for reporting
  • Seed sprint planning with prioritized, reproducible onboarding work items

FAQ

Does this skill fix the issues it creates?

No. This skill only creates issues. Use /fix-onboarding to apply automated fixes or implement changes.

How does it avoid creating duplicate issues?

It queries open issues with the domain/onboarding label and checks for existing similar findings before creating new tickets.