name: ultimate-onboard
description: Drop into ANY project and fully analyze, clean up, document, and configure for parallel agentic work. The nuclear option for project onboarding. Spawns parallel agents for maximum speed.
license: MIT
metadata:
author: thesimpleapp
version: "1.0"

Ultimate Project Onboarding

The nuclear option. Drop into ANY project and make it production-ready for agentic development.

What This Does

ANY PROJECT (messy, undocumented, unfamiliar)
                    ↓
           ┌───────────────────┐
           │  ULTIMATE ONBOARD │
           │                   │
           │  5 Parallel Agents│
           │  Full Analysis    │
           │  Auto Cleanup     │
           │  Complete Docs    │
           └───────────────────┘
                    ↓
PRODUCTION-READY (clean, documented, configured)

Phases

Phase 1: Parallel Analysis (5 Agents)

Spawn 5 agents simultaneously to map the entire codebase:

Agent 1: STRUCTURE
├── Map folder structure
├── Identify entry points
├── Trace build pipeline
└── Output: STRUCTURE.md

Agent 2: PATTERNS
├── Identify coding patterns
├── Find inconsistencies
├── Detect frameworks/libraries
└── Output: PATTERNS.md

Agent 3: DATA
├── Map database schema
├── Trace data flow
├── Identify API contracts
└── Output: DATA_FLOW.md

Agent 4: DEPENDENCIES
├── Audit package.json/pubspec
├── Find outdated packages
├── Security vulnerabilities
└── Output: DEPENDENCIES.md

Agent 5: TECH_DEBT
├── Find code smells
├── Identify dead code
├── Measure complexity
└── Output: TECH_DEBT.md

Phase 2: Synthesis

Combine all 5 reports into unified understanding:

# Architecture Overview

## Tech Stack
- Frontend: [detected]
- Backend: [detected]
- Database: [detected]
- Infrastructure: [detected]

## Key Patterns
- State management: [pattern]
- API layer: [pattern]
- Component structure: [pattern]

## Critical Files
- Entry: [files]
- Config: [files]
- Core logic: [files]

## Health Score
- Code quality: X/10
- Documentation: X/10
- Test coverage: X/10
- Dependency health: X/10

Phase 3: Parallel Cleanup (Conditional)

If user approves, spawn cleanup agents:

Agent A: FORMATTING
├── Apply consistent formatting
├── Fix linting errors
├── Standardize imports
└── Non-breaking changes only

Agent B: DEAD_CODE
├── Remove unused imports
├── Delete commented code
├── Remove unreachable code
└── Safe deletions only

Agent C: NAMING
├── Fix inconsistent naming
├── Rename unclear variables
├── Add missing type annotations
└── Semantic improvements

Agent D: STRUCTURE
├── Move misplaced files
├── Create missing folders
├── Update imports
└── Organize by feature

Phase 4: Documentation Generation

Auto-generate all project docs:

CLAUDE.md
├── Project summary
├── Key patterns
├── File locations
├── Commands

.claude/
├── rules/
│   ├── business-logic.md
│   ├── coding-standards.md
│   └── architecture.md
└── standards/
    ├── components.md
    ├── testing.md
    └── api.md

docs/
├── ARCHITECTURE.md
├── API.md
├── CONTRIBUTING.md
└── SETUP.md

Phase 5: Configure for Power Mode

Set up for parallel agentic development:

.claude/
├── settings.json          # Model preferences
└── rules/
    ├── parallel-safe.md   # Which files can parallel edit
    ├── module-owners.md   # Agent assignments
    └── no-touch.md        # Critical files to protect

Execution Commands

Full Onboard (All Phases)

/ultimate-onboard

→ Runs all 5 phases
→ Creates all documentation
→ Configures for parallel work

Analysis Only

/ultimate-onboard --analyze-only

→ Phase 1 + 2 only
→ No changes to codebase
→ Outputs reports only

Quick Mode

/ultimate-onboard --quick

→ Single agent analysis
→ CLAUDE.md only
→ Fast for familiar codebases

Output Files

Parallel Safety Rules

When spawning multiple agents:

SAFE to parallelize:
✓ Different feature folders
✓ Independent test files
✓ Separate documentation files
✓ Non-overlapping modules

NOT safe:
✗ Shared utilities
✗ Config files
✗ Database migrations
✗ Core type definitions

Detection Patterns

Framework Detection

React:     package.json has "react"
Next.js:   next.config.* exists
Vue:       package.json has "vue"
Flutter:   pubspec.yaml exists
Express:   package.json has "express"
Supabase:  supabase/ folder exists

Pattern Detection

State: Redux | Zustand | Riverpod | Context
API:   REST | GraphQL | tRPC
Style: Tailwind | CSS Modules | Styled
Test:  Jest | Vitest | pytest | flutter_test

Example Output: CLAUDE.md

# ProjectName

## Overview
E-commerce platform built with Next.js, Supabase, and Tailwind.

## Quick Commands
- `npm run dev` - Start development
- `npm run build` - Production build
- `npm test` - Run tests

## Architecture
- `/app` - Next.js app router pages
- `/components` - React components
- `/lib` - Utilities and helpers
- `/supabase` - Database migrations

## Key Patterns
- Server components by default
- Client components in `/components/client/`
- Supabase for auth and database
- Zustand for client state

## Database
- Supabase project: [ref]
- Key tables: users, products, orders
- RLS enabled on all tables

## Standards
See `.claude/rules/` for coding standards.

Integration

After onboarding, seamlessly use other skills:

/ultimate-onboard     → Project fully understood
       ↓
/sprint-planning      → Plan features with full context
       ↓
/parallel-swarm       → Execute with multiple agents
       ↓
/code-review          → Quality gate

Hardware Optimization

With 64 cores / 128GB RAM:

Phase 1: 5 parallel agents (analysis)
Phase 3: 4 parallel agents (cleanup)
Phase 4: 3 parallel agents (docs)

Total time: ~5 minutes for medium codebase
vs ~25 minutes sequential

Rollback

All changes are tracked:

# Undo cleanup changes
git checkout -- .

# Keep only documentation
git checkout -- src/
git add docs/ CLAUDE.md .claude/