Pre-action boundary checking — validates agent tool calls against declared capabilities and task contracts
日本語の概要は準備中です。原文の説明を表示しています。
Research-validated planning — research → plan → verify cycle for high-confidence implementation plans
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Research-validated planning that eliminates the gap between research assumptions and actual code. Orchestrates a 3-phase cycle: Discovery Research → Reality-Check Planning → Plan Verification.
Teams-compatible — works both from the main conversation (R010) and inside Agent Teams members. When used in Teams, the member directly executes the 3-phase workflow without Skill tool invocation.
Full phase detail: guides/deep-plan/phases.md
/deep-plan <topic-or-issue>
/deep-plan "implement caching layer for API responses"
/deep-plan #325 new authentication system
/deep-plan Rust async runtime migration
Research-only analysis produces findings based on assumptions about the codebase. These assumptions often diverge from reality:
| Assumption | Reality | Impact |
|---|---|---|
| "Feature X is missing" | Already implemented | Wasted effort on duplicate work |
| "Pattern Y is needed" | Partially exists | Over-engineering existing code |
| "Library Z is required" | Already a dependency | Unnecessary integration effort |
/deep-plan solves this by cross-referencing research findings against actual code before committing to a plan.
3-phase pipeline:
| Phase | Name | Key Activity | Model |
|---|---|---|---|
| 1 | Discovery Research | 10-team parallel via /research | sonnet + opus |
| 2 | Reality-Check Planning | 3 Explore agents + gap analysis | haiku + opus |
| 3 | Plan Verification | 3 focused verification teams | sonnet + opus |
| Rule | Detail |
|---|---|
| Phase 1 | Full /research skill invocation (10 teams) |
| Phase 2 | Max 3 parallel Explore agents (R009) |
| Phase 3 | Max 3 parallel verification teams (R009) |
| Orchestrator only | Main conversation manages all phases (R010) |
| Intent display | Show phase plan before execution (R015) |
| Ecomode | Auto-activate for team result aggregation (R013) |
| REVISE limit | Max 2 cycles before user escalation |
| Skill | Scope | Code Verification | Phases |
|---|---|---|---|
/research | Analysis only | None — assumption-based | 1 |
| Plan mode | Planning only | Yes — code exploration | 1 |
/structured-dev-cycle | Full implementation | Yes — stage-by-stage | 6 |
/deep-plan | Analysis + Planning + Verification | 3-pass cross-verification | 3 |
R010 Universal /tmp Script Bypass (#1052): ALL .claude/ modifications MUST use /tmp/*.sh script via Bash. Direct Write/Edit/Bash on .claude/ triggers CC sensitive-path guard regardless of bypassPermissions.
Phase 3 verification report path: .claude/outputs/sessions/{YYYY-MM-DD}/deep-plan-{HHmmss}.md
When spawning the final synthesis agent to write this artifact, include verbatim in the agent prompt:
**Sensitive-path artifact protocol (mandatory for this task)**
Write the artifact under `.claude/outputs/` using the /tmp/*.sh bypass:
1. Build script in /tmp: cat > /tmp/deep-plan-<timestamp>.sh <<'EOF' ... EOF
2. Script content: mkdir -p .claude/outputs/sessions/<date>/ && cat > .claude/outputs/sessions/<date>/deep-plan-<HHmmss>.md <<'ARTIFACT' ... ARTIFACT
3. Execute: bash /tmp/deep-plan-<timestamp>.sh
4. Cleanup: rm /tmp/deep-plan-<timestamp>.sh
DO NOT use Write/Edit directly on `.claude/outputs/` — CC sensitive-path guard triggers regardless of bypassPermissions/allow rules.
See R006 "Sensitive Path Handling" + feedback_sensitive_path_tmp_bypass.md.
| Phase | Without Agent Teams | With Agent Teams |
|---|---|---|
| Phase 1 | Delegates to /research (handles internally) | Delegates to /research (handles internally) |
| Phase 2 | Up to 3 Explore agents via Agent tool | Up to 3 Explore agents via Agent tool (below threshold) |
| Phase 3 | 3 agents via Agent tool | 3 agents — prefer Agent Teams for coordination |
After PASS verdict:
[Advisory] Verified plan ready for implementation.
├── For complex implementations (10+ files): /structured-dev-cycle
├── For parallel task execution: superpowers:subagent-driven-development
└── For simple tasks (< 3 files): proceed directly
When spawning agents via the Agent tool during this skill's execution, always pass mode: "bypassPermissions". The Agent tool default (acceptEdits) overrides agent frontmatter permissionMode, causing permission prompts during unattended execution.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Pre-action boundary checking — validates agent tool calls against declared capabilities and task contracts
日本語の概要は準備中です。原文の説明を表示しています。
Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial code review using attacker mindset — trust boundary, attack surface, business logic, and defense evaluation
日本語の概要は準備中です。原文の説明を表示しています。
Apache Airflow best practices for DAG authoring, testing, and production deployment
日本語の概要は準備中です。原文の説明を表示しています。
Alembic migration patterns for naming conventions, safety checks, expand-contract, env.py configuration, and CI integration
日本語の概要は準備中です。原文の説明を表示しています。
Pre-routing ambiguity analysis — scores request clarity and asks clarifying questions when needed (inspired by ouroboros)
日本語の概要は準備中です。原文の説明を表示しています。