Coordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution", "structured thinking", "break this down", "plan this out", "how should I approach", or needs help planning complex implementations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Guide users through structured thinking and recommend appropriate tools for complex tasks.
| Situation | Recommendation |
|---|---|
| Multi-step project, full SDLC | /core:develop command |
| Plan only, implement later | /core:develop --plan-only |
| Resume existing plan | /core:develop @path/to/plan.md |
| Single complex problem needing deep analysis | /think command |
| Security-sensitive or high-stakes work | /core:develop --validate |
| Strategic decision with long-term impact | deep-think-partner agent |
| Simple task, clear steps | Inline guidance (no command needed) |
Detect these signals for structured thinking:
Keyword triggers:
Context triggers:
When structured approach is needed:
1. GATE → Is the request clear and actionable?
2. CONTEXT → What files/patterns are relevant?
3. PLAN → What tasks? Parallel vs sequential?
4. EXECUTE → Deploy specialists, maximize parallelism
5. VALIDATE → Confidence scoring (if needed)
6. REPORT → Summary with next steps
/core:develop <request> [flags]Unified SDLC command with 6-phase pipeline and multi-agent orchestration.
Flags:
--plan-only - Stop after Phase 2 (save plan, don't implement)--validate - Enable deep validation with opus agent--phase=N - Execute specific phase only--auto - Autonomous mode (no checkpoints)Best for: Feature implementations, refactoring projects, any multi-step development task.
Resume mode: /core:develop @path/to/plan.md loads existing plan and continues.
/think [problem]Invoke deep-think-partner for collaborative reasoning.
Best for: Single complex problems, decision analysis, reasoning validation, architectural decisions.
For simpler tasks, provide structured thinking directly:
| Task Type | Model | Use Case |
|---|---|---|
| Gating, routing | haiku | Quick decisions, simple queries |
| Implementation | sonnet | Standard coding, documentation |
| Deep analysis | opus | Architecture, complex reasoning |
When providing orchestration guidance:
## Recommended Approach
**Complexity:** [Low | Medium | High]
**Suggested tool:** [command or inline]
### Why
[Brief explanation of why this approach fits]
### Steps
1. [First step]
2. [Second step]
...
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Create, review, and manage Architecture Decision Records (ADRs) with auto-numbering, template detection, quality review, and index maintenance. Use when user mentions "ADR", "architecture decision", "document this decision", "create ADR", "review ADR", editing ADR files (docs/adr/, doc/adr/, .adr/), or discussing architectural choices and tradeoffs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze system architecture, module structure, API contracts, data models, and code patterns. Use when designing systems, reviewing module boundaries, evaluating API designs, analyzing data models, checking pattern conformance, tracing decisions, or reviewing frontend architecture. Triggers: "architecture", "module design", "API design", "data model", "boundaries", "patterns", "decisions", "frontend architecture".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Converts natural-language descriptions or UI spec files into optimized Google Stitch prompts. Use when creating, refining, or validating design directives for Google Stitch. Use when user says "create a Stitch prompt", "optimize this for Stitch", "convert this spec to a Stitch prompt", "write a UI prompt", or mentions Google Stitch prompt authoring. Follows Stitch best practices with short, directive prompts focused on screens, structure, and visual hierarchy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Zero-dependency live-preview server providing an agent↔browser bidirectional companion. Watches a content directory, wraps HTML fragments in a frame template, broadcasts live-reload over WebSocket, and captures browser-side click events to a JSONL file. Use when an agent needs to show HTML to the user in a browser and react to clicks — mockups, design exploration, gallery browsing, multi-select choices, prototype iteration. Triggered by "live preview", "browser companion", "preview server", "browser mockup", "show in browser", "arkhe-preview", or any skill that wants to write HTML fragments and have the user see them reload in real time.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deletes merged git branches (local and remote) and flags stale unmerged branches for manual review. Use when user mentions "cleanup branches", "delete merged branches", "prune old branches", "remove stale branches", "branch cleanup", or runs /cleanup-branches command.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.