メニュー
Track progress with auto-flow execution. Use for "checkpoint", "progress", "status", "start CP", "complete", "resume".
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/potenlab/marketplace-potenlab --skill checkpointコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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.
SKILL.md を表示中
SOC 職業分類に基づく
| name | checkpoint |
| description | Track progress with auto-flow execution. Use for "checkpoint", "progress", "status", "start CP", "complete", "resume". |
| argument-hint | [start|complete|status|resume] [CP#] |
| disable-model-invocation | true |
| user-invocable | true |
Auto-flow execution with human approval at checkpoint completion only.
/checkpoint start CP1
↓
[Auto-implement ALL tasks]
↓
Build + Lint + Test + Verify
↓
Show Diff → Human Approval → Commit
↓
Auto-start next checkpoint
| Action | Description |
|---|---|
start [CP#] | Begin checkpoint, auto-implement all tasks |
complete | Verify + commit (called automatically) |
status | Show progress dashboard |
resume [CP#] | Resume interrupted checkpoint |
Read .planning/CHECKPOINTS.md and .planning/PRD.md.
Count tasks and estimate files:
Checkpoint: CP1 - Database Setup
Tasks: 3
Estimated files: ~5
If >5 tasks OR >10 estimated files:
⚠️ This checkpoint is large (6 tasks, ~12 files).
Consider splitting into smaller checkpoints.
Continue anyway? [y/n]
Update CHECKPOINTS.md:
## CP1: Database Setup 🔄
> Started: [date]
Check if any task involves UI:
*.tsx in components/, app/If UI work detected:
🎨 UI work detected. Applying /baseline-ui rules:
- No gradients unless requested
- No animations unless requested
- Use Tailwind defaults
- shadcn/ui components
Load .claude/rules/ui.md into context.
## Starting CP1: Database Setup
Tasks to implement:
1. [ ] Create users table with RLS
2. [ ] Create tasks table with RLS
3. [ ] Generate TypeScript types
I'll implement all tasks, then ask for your approval.
Beginning...
For each task:
Announce task:
### Task 1/3: Create users table with RLS
Implement - Do the actual work
Quick verify (silent):
bun run build
Track progress in memory:
✓ Task 1/3 complete
Save partial progress to CHECKPOINTS.md:
- [x] Create users table with RLS ← partial
- [ ] Create tasks table with RLS
Continue to next task - No pause
If build fails:
⚠️ Task 1 failed build:
[error message]
Attempting fix...
Fix and retry (max 3 attempts).
If unfixable:
❌ Stuck on Task 1 after 3 attempts.
Options:
1. Skip and continue (mark as TODO)
2. Pause for human help
3. Rollback this task
All tasks implemented. Running final verification...
Automatically proceed to complete flow.
Run all checks:
# Build
bun run build
# Lint
bun run lint
# Tests (if script exists)
bun run test --passWithNoTests 2>/dev/null || true
## CP1 Verification
| Check | Status |
|-------|--------|
| Build | ✅ Pass |
| Lint | ✅ Pass |
| Tests | ✅ Pass (or N/A) |
| Tasks | ✅ 3/3 complete |
If any check fails:
## CP1 Verification: ISSUES FOUND
| Check | Status | Issue |
|-------|--------|-------|
| Lint | ⚠️ | 2 warnings in users.ts |
Auto-fixing lint issues...
Auto-fix if possible, then re-verify.
git diff --stat HEAD
git diff --name-only HEAD
## Changes Summary
**Files changed**: 5
**Lines**: +245 / -12
| File | Changes |
|------|---------|
| supabase/migrations/001_users.sql | +45 (new) |
| supabase/migrations/002_tasks.sql | +38 (new) |
| lib/supabase/database.types.ts | +120 (new) |
| lib/supabase/client.ts | +30 / -10 |
| .planning/CHECKPOINTS.md | +12 / -2 |
### Key Changes
- Created users table with id, email, name, avatar_url
- Created tasks table with user_id foreign key
- Added RLS policies for both tables
- Generated TypeScript types from schema
## Ready to Commit CP1
**Checkpoint**: CP1 - Database Setup
**Tasks**: 3/3 complete
**Files**: 5 changed (+245/-12)
### Commit Message
feat(db): add users and tasks tables with RLS
- Created users table with profile fields
- Created tasks table linked to users
- Added RLS policies for row-level security
- Generated TypeScript types from schema
Checkpoint: CP1
Use AskUserQuestion:
Review the changes above. Ready to commit?
Options:
git diff outputIf "View full diff":
Show full git diff output, then ask again.
If "Request changes":
What changes would you like?
> [user input]
Make changes, re-run verification, ask again.
If "Approve": Proceed to commit.
git add -A
git commit -m "feat(db): add users and tasks tables with RLS
- Created users table with profile fields
- Created tasks table linked to users
- Added RLS policies for row-level security
- Generated TypeScript types from schema
Checkpoint: CP1
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"
Update .planning/CHECKPOINTS.md:
## CP1: Database Setup ✅
> Completed: [date]
> Commit: abc1234
- [x] Create users table with RLS
- [x] Create tasks table with RLS
- [x] Generate TypeScript types
## CP1 Complete! ✅
Commit: abc1234
Files: 5 changed (+245/-12)
Progress: ████░░░░░░ 1/3 checkpoints
Starting CP2: User Authentication...
Automatically execute /checkpoint start CP2.
If last checkpoint:
## 🎉 Project Complete!
All checkpoints done:
- ✅ CP1: Database Setup (abc1234)
- ✅ CP2: User Authentication (def5678)
- ✅ CP3: Dashboard (ghi9012)
Total commits: 3
Ready to deploy!
For recovering from interruption:
Read CHECKPOINTS.md to find partial progress:
## CP1: Database Setup 🔄
- [x] Create users table ← done
- [ ] Create tasks table ← resume here
- [ ] Generate types
## Resuming CP1: Database Setup
Progress: 1/3 tasks complete
Resuming from: "Create tasks table"
Continue?
Pick up from next incomplete task.
## Project: Task Manager
Progress: ████████░░ 2/3 checkpoints
| CP | Name | Status | Tasks | Commit |
|----|------|--------|-------|--------|
| 1 | Database | ✅ | 3/3 | abc1234 |
| 2 | Auth | ✅ | 4/4 | def5678 |
| 3 | Dashboard | ⬜ | 0/3 | - |
**Next**: /checkpoint start CP3
<type>(<scope>): <summary>
<body - bullet points of what was done>
Checkpoint: CP#
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Types: feat, fix, refactor, chore, docs