メニュー
Use when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development. Covers Spec-Driven Development, Context Engineering, and post-dev workflow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use *before* starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm new to this", "I don't know what to ask", "teach me before we start", "blind spot pass", "unknown unknowns", "find my unknowns", or the Korean "내가 뭘 모르는지 알려줘" / "이 분야 처음인데" / "먼저 가르쳐줘" / "블라인드 스팟", or when you hand off a task while admitting you're a non-expert in that field (color grading, video editing, legal, tax, finance, design, an unfamiliar codebase, etc.). Do NOT use for simple factual questions, domains you already know, or directly-actionable work — answer those directly or route to planner / architect.
Turn a one-line description of a repetitive task into a reusable, self-guarding slash command. loop-forge diagnoses the task into one of 5 loop shapes (Batch / Pipeline / Refine / Watch / Explore), interviews for the blanks, and auto-injects two safety devices the user didn't know they needed — an independent verifier (maker ≠ checker) and a hardstop (a budget/count/cooldown ceiling) — then previews the result and stamps it as a `/command` they can run forever. Use when the user says "/loop", "/loop-forge", "/make-it-loop", "automate this", "make this repeatable", "turn this into a command", "do this for all 100 items", "do X every time Y happens", "generate several and pick the best", or otherwise wants to capture a recurring task as a reusable slash command instead of re-typing the prompt by hand. Works in any language: it interviews the user and writes the stamped command in the user's own language. Non-goal — it does not schedule unattended runs (launchd/cron) or publish externally on its own; it stamps t
Use when detecting and running project build systems automatically. Supports npm/yarn/pnpm/pip/poetry/gradle/maven/cargo/go/make. Triggers on build, test run, project setup, package manager detection.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
Use when searching, installing, or improving AI skills and prompts via prompts.chat or skills.sh. Triggers on skill search, prompt lookup, install skill, improve prompt, prompts.chat.
| name | cc-dev-agent |
| description | Use when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development. Covers Spec-Driven Development, Context Engineering, and post-dev workflow. |
Claude Code를 활용한 Spec-Driven 개발 워크플로우 및 Context Engineering 가이드.
/clear 후 새 눈으로 검증 (Boris 원칙)Git Worktree 기반 병렬 개발은 레거시. Agent Teams가 팀 생성/정리를 자동 처리.
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS를 1로 설정~/.claude/settings.json의 env 또는 셸 환경변수/orchestrate --type feature # 기능 구현
/orchestrate --type bugfix # 버그 수정
/orchestrate --type refactor # 리팩토링
→ 상세 가이드: references/sub-agents.md
"Give Claude a way to verify its work. If Claude has that feedback loop, it will 2-3x the quality."
/orchestrate (선택) → 개발 → /handoff-verify
→ /sync-docs (머지 전 문서 동기화 의무)
→ /commit-push-pr --merge
→ /web-checklist
| 단계 | 명령어 | 이유 |
|---|---|---|
| 1 | /orchestrate (선택) | Agent Teams 병렬 개발 |
| 2 | 개발 | 기능 구현 |
| 3 | /handoff-verify | 의도 문서화 + fresh context 자동 검증 (v6 통합) |
| 4 | /sync-docs | 머지 전 문서 동기화 (의무 게이트) — 문서 변경분이 머지 커밋에 포함됨 |
| 5 | /commit-push-pr --merge | 커밋 & PR & 머지 (v7: sync-docs 게이트 내장 — 4단계 누락 시 자동 실행) |
| 6 | /web-checklist | 웹 테스트 체크리스트 |
→ 상세 가이드: references/post-dev-workflow.md
| 명령어 | 용도 | 사용 시점 |
|---|---|---|
/clear | 컨텍스트 완전 초기화 | 새 Task, 에러 루프 탈출, 검증 전 |
/compact | 대화 요약 압축 | 60% 도달 시 |
/context | 현재 사용량 확인 | 복잡한 작업 중 수시 체크 |
→ 상세 가이드: references/context-engineering.md
| 유형 | 용도 |
|---|---|
Explore | 빠른 코드베이스 검색 (Read-only) |
Plan | 구현 계획 설계 |
병렬 처리: 최대 10개 동시 실행
→ 상세 가이드: references/sub-agents.md
Phase 1: 초기화 → CLAUDE.md 생성
Phase 2: 기획 → spec.md, prompt_plan.md 작성
Phase 3: 구현 → TDD Loop 반복 (핵심)
Phase 4: 검증 → 스펙 대조, 코드 리뷰
Phase 5: 배포 → 보안 검토, 최종 점검
| 키워드 | 용도 |
|---|---|
think | 단순 버그 |
think hard | 다중 파일, 원인 불명 |
ultrathink | 아키텍처, 설계 결함 |
→ 상세 사용법: references/troubleshooting.md
.claude/context/
.claude/settings.json
.claude/settings.local.json
.claude/handoff.md
CLAUDE.local.md
| 파일 | 용도 |
|---|---|
references/post-dev-workflow.md | 개발 완료 후 워크플로우 상세 |
references/sub-agents.md | 서브에이전트 + Agent Teams |
references/prompts.md | 복사용 프롬프트 |
references/context-engineering.md | 컨텍스트 엔지니어링 심화 |
references/playwright-agents.md | Playwright 테스트 에이전트 |
references/templates.md | MD 파일 템플릿 |
references/troubleshooting.md | 에러 해결 + Think 키워드 상세 |