菜单
Consolidates legacy task files (docs/planning/06-tasks.md, etc.) into the root TASKS.md. Use this whenever task files are scattered across multiple locations. Invoke immediately on "migrate tasks", "move 06-tasks to TASKS", or "consolidate tasks" requests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Cross-project experience memory — your persistent knowledge base across sessions. Remembers what worked, what failed, and why, so every new session starts smarter. Log outcomes → recall lessons → apply patterns. Use when starting work that other projects have solved, when you need to avoid past mistakes, or when onboarding to a new project area. Also logs skill execution outcomes to improve future routing. Responds to: 'memento', 'cross-project knowledge', 'what did we learn', 'past experience', 'avoid repeating', 'session memory', 'global memory', '스킬 성능', '스킬 추천', '스킬 건강', '어떤 스킬이 좋아'.
cmux 창 분할 기반 멀티-AI 합의 리뷰 엔진. 동일 워크스페이스에서 Gemini/Codex 패널을 나란히 분할해 3-Stage 파이프라인(의견 → 반론 → 합성)을 진짜 병렬로 실행합니다. multi-ai-review의 순차 실행 대신 두 AI가 동시에 리뷰하는 것을 실시간으로 볼 수 있음. "/cmux-ai-review", "cmux 코드 리뷰", "AI 패널 리뷰", "병렬 리뷰" 등 cmux 환경에서 여러 AI의 동시 리뷰가 필요한 요청이라면 반드시 이 스킬을 사용하세요.
Claude + Gemini CLI + Codex CLI multi-AI consensus engine. 3-Stage Pipeline (opinions → rebuttal → synthesis) drives consensus across domains: code review, market analysis, investment diligence, risk assessment, and more. Automatically detects domain from natural language and applies appropriate preset. Triggers: - "review this", "convene a council", "get multiple AI opinions", "deep review", "consensus" - "market analysis", "macro analysis", "investment review", "risk assessment" - Any situation needing multiple perspectives — trigger proactively
Routes each agent role to the optimal AI model (Claude/Gemini/Codex) and executes it. Automatically assigns Codex for code writing, Gemini for design, and Claude for planning and orchestration. Use this skill whenever you see "use Codex for code", "use Gemini for design", "use a different AI", or "model routing" requests. Triggers on /multi-ai-run.
Comprehensive quality audit before phase completion or deployment. Performs planning conformance, DDD validation, security checks, tests, browser verification, and quantitative metrics. Also enforces verification-before-completion discipline — no claims without evidence. Run this skill before deploying, before merging a PR, after completing significant changes, and whenever anyone claims 'it works' or 'tests pass'. Triggers immediately on 'quality check', 'pre-deploy check', 'audit this', 'QA', 'verify this', 'does this work', '품질 검사', '배포 전 검사'. Trigger: /audit, /evaluate, /verify.
cmux 창 분할 기반 멀티-AI 병렬 태스크 실행. 동일 워크스페이스에서 Codex(코드)/Gemini(디자인)/Claude(계획)를 패널로 분할해 동시에 실행합니다. multi-ai-run의 순차 실행과 달리 진짜 병렬. "/cmux-ai-run", "cmux로 AI 분업", "창 분할 병렬 실행", "codex gemini 동시 실행" 등 cmux 환경에서 여러 AI를 동시에 돌리고 싶은 요청이라면 반드시 이 스킬을 사용하세요.
| name | tasks-migrate |
| description | Consolidates legacy task files (docs/planning/06-tasks.md, etc.) into the root TASKS.md. Use this whenever task files are scattered across multiple locations. Invoke immediately on "migrate tasks", "move 06-tasks to TASKS", or "consolidate tasks" requests. |
| triggers | ["/tasks-migrate","태스크 마이그레이션","06-tasks를 TASKS로","태스크 통합","migrate tasks"] |
| version | 1.0.0 |
Scans legacy task files (docs/planning/06-tasks.md, task.md, etc.) and consolidates them into the root TASKS.md.
TASKS.md (with deduplication)┌─────────────────────────────────────────────────────────────┐
│ 1. Detection Phase │
├─────────────────────────────────────────────────────────────┤
│ • Check whether TASKS.md exists │
│ • Scan for legacy files (in priority order) │
│ • Count discovered checkbox items │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 2. Analysis Phase │
├─────────────────────────────────────────────────────────────┤
│ • Extract Task IDs (P*-T*, T*.*) │
│ • Classify by layer (T0–T3, P*) │
│ • Detect duplicates │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 3. User Confirmation │
├─────────────────────────────────────────────────────────────┤
│ • Output migration summary │
│ • User chooses: create / merge / cancel │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 4. Output Phase │
├─────────────────────────────────────────────────────────────┤
│ • Create or merge TASKS.md │
│ • Append Migration Report section │
└─────────────────────────────────────────────────────────────┘
Check for task files in the following priority order:
# Priority order
ls -la TASKS.md 2>/dev/null
ls -la docs/planning/06-tasks.md 2>/dev/null
ls -la docs/planning/tasks.md 2>/dev/null
ls -la docs/tasks.md 2>/dev/null
ls -la planning/tasks.md 2>/dev/null
ls -la .tasks.md 2>/dev/null
ls -la task.md 2>/dev/null
Fallback: If none of the above are found, search using the *tasks*.md pattern.
Extract checkbox items from discovered files:
Extracted targets:
- [ ] Incomplete task
- [x] Completed task
- [/] In progress (optional: normalize to - [ ] (in progress))
Task ID patterns:
P\d+(?:-[A-Z]\d+)?(?:-T\d+)? # P1-T1, P2-S1-T3
T\d+(?:\.\d+)+ # T0.1, T1.12, T3.4
Classification criteria:
| ID Pattern | Layer | Section |
|---|---|---|
T0.* | Skeleton | ## T0 — Skeleton |
T1.* | Muscles | ## T1 — Muscles |
T2.* | Muscles Advanced | ## T2 — Muscles (advanced) |
T3.* | Skin | ## T3 — Skin |
P*-* | Phase-based | ## P* — Project/Phase tasks |
| (no ID) | Uncategorized | ## Uncategorized |
Output the migration summary and ask the user to confirm:
## Migration Summary
### Discovered Files
| File | Tasks | Checked | Unchecked |
|------|-------|---------|-----------|
| docs/planning/06-tasks.md | 25 | 20 | 5 |
| task.md | 3 | 1 | 2 |
### ID Distribution
- T0.* (Skeleton): 5
- T1.* (Muscles): 12
- T2.* (Advanced): 3
- T3.* (Skin): 5
- P*-T* (Phase): 3
- No ID: 0
### Expected Result
- TASKS.md create/merge: 28 items
- Duplicates removed: 2
Confirm via AskUserQuestion:
TASKS.md structure:
# TASKS.md
> Canonical task file for this project.
> Migrated: {date}
## T0 — Skeleton
- [ ] T0.1: Project structure setup
- [x] T0.2: Routing configuration
## T1 — Muscles
- [ ] T1.1: Authentication feature implementation
- [ ] T1.2: API integration
## T2 — Muscles (advanced)
- [ ] T2.1: Caching layer
- [ ] T2.2: Error handling
## T3 — Skin
- [ ] T3.1: Apply animations
- [ ] T3.2: Responsive design
## P* — Project/Phase tasks
- [x] P1-T1: Design document complete
- [ ] P2-T1: Hook implementation
---
## Migration Report
| Source | Imported | Duplicates Skipped |
|--------|----------|-------------------|
| docs/planning/06-tasks.md | 25 | 2 |
| task.md | 3 | 0 |
**Total**: 28 tasks imported
**Date**: 2026-03-03
--dry-run to preview without making changes/tasks-migrate
# or
"Migrate 06-tasks.md to TASKS.md"
"Consolidate legacy task files"
/workflow-guide — Diagnose whether migration is needed/agile — Run a sprint after migration/recover — Reference when recovering task files