원클릭으로
init-project
Initialize project with PRD and checkpoints. Use for "init project", "new project", "start project".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Initialize project with PRD and checkpoints. Use for "init project", "new project", "start project".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Executes all tasks in a specific phase using wave-based parallel execution (max 4 agents per wave). Spawns small-coder and high-coder agents based on progress.json complexity. Updates progress.json after EACH wave so completed tasks immediately unblock dependents. Accepts phase number as argument (/execute-phase 3) or asks via AskUserQuestion. Triggers on: execute phase, run phase, build phase, develop phase, start phase.
Generates Vitest test files from test-plan.md using the qa-specialist agent. Reads the test plan and vitest best practices, then spawns qa-specialist agents to produce .test.ts files in the root tests/ directory for features, shared tests, and Supabase integration tests. Tests verify behavior via database operations and RLS policies — no UI testing. Triggers on: generate test, generate tests, create tests, write tests, test generation.
Orchestrates sequential project planning. First validates user intent via AskUserQuestion (MANDATORY), then spawns ui-ux-specialist to create ui-ux-plan.md, then tech-lead-specialist to create dev-plan.md from ui-ux-plan.md, then spawns frontend-specialist and backend-specialist in parallel to create their detailed plans from dev-plan.md, then spawns qa-specialist to create test-plan.md from dev-plan.md and backend-plan.md. Triggers on: plan, create plan, plan project, project plan, full plan, prd to plan.
Runs ALL Vitest tests across /features, /tests, and /supabase directories. Executes tests via npx vitest run, collects results, and generates test.result.json (replaced on every run). Uses qa-specialist to analyze failures and provide actionable feedback. Triggers on: run test all, run all tests, test all, vitest all, run tests.
Runs Vitest tests for a specific phase chosen by the user. Reads test-plan.md to identify phases, asks user which phase to run via AskUserQuestion, executes only those test files, and generates test.result.json (replaced on every run). Uses qa-specialist to analyze failures. Triggers on: run test phase, test phase, run phase test, test specific phase.
Verifies and updates tests after code changes. Detects what changed (git diff, changes.json), compares against test-plan.md, then spawns qa-specialist agents to update test-plan.md and edit/create test files in /features, /tests, /supabase. Use after /developer or manual changes to keep tests in sync. Triggers on: verify test, verify tests, sync tests, update tests, check tests, test verify.
SOC 직업 분류 기준
| name | init-project |
| description | Initialize project with PRD and checkpoints. Use for "init project", "new project", "start project". |
| argument-hint | [project description] |
| disable-model-invocation | true |
| user-invocable | true |
Scaffold project from reference template, then create PRD and checkpoints through interactive questions.
<CWD>/
├── app/ # Next.js app router (from template)
├── components/ # UI components (from template)
├── hooks/ # Custom hooks (from template)
├── lib/ # Utilities (from template)
├── stores/ # Zustand stores (from template)
├── supabase/ # Migrations (from template)
├── public/ # Static assets (from template)
├── .claude/ # Rules + skills + settings (from template)
├── .planning/
│ ├── PRD.md # Requirements + features (generated)
│ └── CHECKPOINTS.md # Progress tracker (generated)
├── package.json # Dependencies (from template)
├── CLAUDE.md # Project instructions (from template)
└── ...config files # tsconfig, biome, etc. (from template)
/init-project → Scaffold from reference/ → bun install → Interactive Questions → PRD → Checkpoints → Auto-start CP1
The reference/ directory lives inside this skill's directory:
.claude/skills/init-project/reference/
Resolve the path relative to this SKILL.md file location.
Copy all files from reference/ to the current working directory:
rsync -a --exclude='node_modules' --exclude='.next' --exclude='tsconfig.tsbuildinfo' --exclude='next-env.d.ts' \
.claude/skills/init-project/reference/ ./
Important: This uses rsync to merge (not overwrite existing files unless they exist in reference). The .claude/ directory in reference will be merged with the existing .claude/ in CWD.
bun install
Show progress:
Scaffolding project from template...
✅ Copied template files to project
✅ Dependencies installed
Proceeding to project setup...
Check connections silently:
mcp__supabase__list_projects
mcp__shadcn__list_shadcn_components
Show status:
MCP servers connected:
- Supabase: Connected (project: "xxx")
- shadcn/ui: Connected (59 components)
If not connected, warn and stop.
Use AskUserQuestion for EACH question with smart suggestions.
AskUserQuestion:
question: "What type of app are you building?"
header: "App Type"
options:
- label: "SaaS / Dashboard"
description: "Admin panels, analytics, user management"
- label: "E-commerce"
description: "Product listings, cart, checkout"
- label: "Social / Community"
description: "Posts, comments, user profiles"
- label: "Productivity / Tools"
description: "Task management, notes, utilities"
Based on app type, suggest names:
AskUserQuestion:
question: "What's your project name?"
header: "Name"
options:
# If SaaS:
- label: "AdminHub"
description: "Dashboard and admin panel"
- label: "MetricFlow"
description: "Analytics and metrics"
# If E-commerce:
- label: "ShopBase"
description: "Online store"
- label: "CartFlow"
description: "Shopping platform"
# If Productivity:
- label: "TaskFlow"
description: "Task management"
- label: "NoteSpace"
description: "Notes and docs"
# Always include Other for custom input
AskUserQuestion:
question: "What problem does this solve?"
header: "Problem"
options:
# Based on app type, suggest common problems:
# If SaaS:
- label: "Track and manage user data"
description: "CRUD operations, user management"
- label: "Visualize metrics and analytics"
description: "Charts, reports, dashboards"
# If E-commerce:
- label: "Sell products online"
description: "Product catalog, checkout flow"
- label: "Manage inventory"
description: "Stock tracking, orders"
# If Productivity:
- label: "Organize tasks and projects"
description: "Todo lists, project boards"
- label: "Take and organize notes"
description: "Note-taking, knowledge base"
AskUserQuestion:
question: "Select MVP features (pick 3-4)"
header: "Features"
multiSelect: true
options:
# Based on app type, suggest relevant features:
# If SaaS/Dashboard:
- label: "User authentication"
description: "Login, signup, profile"
- label: "Dashboard overview"
description: "Stats, charts, summary"
- label: "Data management (CRUD)"
description: "Create, read, update, delete"
- label: "Search & filters"
description: "Find and filter data"
# If E-commerce:
- label: "Product catalog"
description: "List and view products"
- label: "Shopping cart"
description: "Add to cart, manage items"
- label: "Checkout flow"
description: "Payment, order confirmation"
- label: "Order history"
description: "View past orders"
# If Productivity:
- label: "Task CRUD"
description: "Create, edit, delete tasks"
- label: "Categories/Projects"
description: "Organize items"
- label: "Due dates & reminders"
description: "Time-based features"
- label: "Search & filters"
description: "Find items quickly"
Show summary and ask confirmation:
## Project Summary
**Name**: TaskFlow
**Type**: Productivity / Tools
**Problem**: Organize tasks and projects
**MVP Features**:
1. User authentication
2. Task CRUD
3. Categories/Projects
4. Search & filters
**Checkpoints** (auto-generated):
- CP1: Database & Auth (3 tasks)
- CP2: Core Features (4 tasks)
- CP3: Polish & Deploy (3 tasks)
Create project files?
AskUserQuestion:
question: "Create project with these settings?"
header: "Confirm"
options:
- label: "Yes, create project"
description: "Generate PRD and checkpoints, start CP1"
- label: "Change features"
description: "Go back and modify feature selection"
- label: "Start over"
description: "Begin from app type selection"
Write .planning/PRD.md with collected info:
# [Name] - PRD
## Overview
- **Project**: [name]
- **Type**: [type]
- **Created**: [date]
- **Status**: In Progress
## Problem
[selected problem]
## Target User
[inferred from type]
## MVP Features
| ID | Feature | Description | Priority |
|----|---------|-------------|----------|
| F1 | [feature] | [description] | P0 |
| F2 | [feature] | [description] | P0 |
| F3 | [feature] | [description] | P1 |
| F4 | [feature] | [description] | P1 |
## Tech Stack
- Framework: Next.js 16
- Styling: Tailwind CSS v4
- UI: shadcn/ui
- Backend: Supabase
- Forms: react-hook-form + zod
After generating the PRD, update scaffolded files with the user's project name:
package.json → Update "name" field to kebab-case of project name.claude/settings.json → Update "name" and "description" fields# Example: If user chose "TaskFlow"
# package.json: "name": "task-flow"
# .claude/settings.json: "name": "TaskFlow", "description": "Organize tasks and projects"
Auto-generate checkpoints based on features:
Pattern:
# Project Checkpoints
## Status
- **Project**: [name]
- **Progress**: 0/3 checkpoints
- **Current**: CP1
---
## CP1: Database & Auth ⬜
> Setup foundation
- [ ] Create database tables with RLS
- [ ] Setup authentication flow
- [ ] Generate TypeScript types
**Done when**: User can sign up, login, and data is secure
---
## CP2: Core Features ⬜
> Build main functionality
- [ ] [Feature 1 - main task]
- [ ] [Feature 2 - main task]
- [ ] [Feature 3 - main task]
- [ ] [Feature 4 - main task]
**Done when**: All MVP features working
---
## CP3: Polish & Deploy ⬜
> Final touches
- [ ] Add loading & error states
- [ ] Mobile responsive check
- [ ] Deploy to Vercel
**Done when**: App is production-ready
✅ Project initialized!
Created:
├── .planning/PRD.md
└── .planning/CHECKPOINTS.md
Checkpoints:
1. CP1: Database & Auth (3 tasks)
2. CP2: Core Features (4 tasks)
3. CP3: Polish & Deploy (3 tasks)
Starting CP1 automatically...
Immediately execute /checkpoint start CP1.
Features: Auth, Dashboard, CRUD, Reports, Settings
CP1: DB + Auth
CP2: Dashboard + CRUD
CP3: Reports + Polish
Features: Auth, Products, Cart, Checkout, Orders
CP1: DB + Auth + Products schema
CP2: Product listing + Cart + Checkout
CP3: Orders + Polish
Features: Auth, Posts, Comments, Profiles, Feed
CP1: DB + Auth + Profiles
CP2: Posts + Comments + Feed
CP3: Notifications + Polish
Features: Auth, Items CRUD, Categories, Search
CP1: DB + Auth
CP2: Items + Categories + Search
CP3: Polish + Deploy