메뉴
Save or resume work context. Use for "save", "pause", "resume", "continue", "stopping".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | session |
| description | Save or resume work context. Use for "save", "pause", "resume", "continue", "stopping". |
| argument-hint | [save|resume] |
| disable-model-invocation | true |
| user-invocable | true |
Save context when stopping, resume when returning.
| Action | Triggers |
|---|---|
save | "save", "pause", "stopping", "done for today" |
resume | "resume", "continue", "where was I" |
git status
git log --oneline -3
Read .planning/CHECKPOINTS.md for current progress.
Write .planning/HANDOFF.md:
# Session Handoff
**Date**: [date]
**Checkpoint**: CP2 - Authentication
## Progress
- ✅ CP1: Database (committed)
- 🔄 CP2: Authentication (in progress)
- [x] Login form
- [ ] Register form ← stopped here
- [ ] Password reset
## Current State
- Branch: main
- Uncommitted changes: Yes/No
- Last commit: abc1234 "feat(db): setup tables"
## Next Step
Continue with "Register form" in CP2.
## Notes
[Any important context]
If uncommitted changes exist:
⚠️ You have uncommitted changes.
Options:
1. Create WIP commit
2. Stash changes
3. Leave as-is
Session saved to .planning/HANDOFF.md
To continue later: /session resume
Read .planning/HANDOFF.md.
If missing, read .planning/CHECKPOINTS.md instead.
bun run build
git status
## Welcome Back!
**Project**: Task Manager
**Last session**: 2026-02-01
### Where You Left Off
Checkpoint: CP2 - Authentication
Task: Register form (not started)
### To Continue
I'll continue implementing CP2.
Ready to start?
If user confirms, automatically run /checkpoint start CP2 to continue.