/plan-down

name: plan-down
description: Method clarity-driven planning workflow using zen-mcp tools (chat, planner, consensus). Phase 0 uses chat to judge if user provides clear implementation method. Four execution paths based on automation_mode × method clarity - Interactive/Automatic × Clear/Unclear. All paths converge at planner for task decomposition. Produces complete plan.md file. Use when user requests "create a plan", "generate plan.md", "use planner for planning", "help me with task decomposition", or similar planning tasks.

Plan-Down - Method-Driven Four-Path Intelligent Planning Generator

Overview

This skill provides a comprehensive method clarity-driven planning workflow that intelligently adapts to both user interaction preference (Interactive/Automatic) and implementation method clarity (Clear/Unclear).

**Core Innovation:** Uses zen-mcp chat as decision module to assess whether user provides a "clear implementation method" before planning.

**Four Execution Paths:** 1. **Interactive + Clear**: Direct planning with user approval 2. **Interactive + Unclear**: Multi-round dialogue to clarify method, then plan 3. **Automatic + Clear**: Fully automated planning 4. **Automatic + Unclear**: AI chain (clink → chat → consensus) to enrich method, then plan

The final output is a complete `plan.md` file ready for implementation.

**Technical Architecture:**

• **zen-mcp chat**: Method clarity judgment + interactive clarification + deep thinking (via clink)
• **zen-mcp planner**: Interactive, sequential planning tool with revision and branching capabilities
• **zen-mcp consensus**: Multi-model method validation (only for Automatic + Unclear path)
• **Main Claude Model**: Context gathering, workflow orchestration, plan.md generation
• **User**: Provides ideas/requirements (interactive mode) or none (automatic mode)

**New Four-Path Workflow:**

User Request → Phase 0 (chat: Method Clear?) → [Conditional Phase 1] → Phase 2 (planner) → Phase 3 (plan.md)
                        ↓                              ↓
                   Clear / Unclear           Clear: Skip to Phase 2
                                            Unclear: Phase 1 (Clarify/Enrich)
                                                    ↓
                                            Interactive: Dialogue with user
                                            Automatic: clink → chat → consensus

**Division of Responsibilities:**

**Phase 0 (Method Clarity Assessment - ALWAYS):**

• **chat tool**: Judge if user provides clear implementation method
• **Main Claude**: Gather context from CLAUDE.md/PROJECTWIKI.md

**Phase 1 (Method Clarification/Enrichment - CONDITIONAL):**

• **Path A (Interactive + Unclear)**: chat multi-round dialogue with user to clarify
• **Path B (Automatic + Unclear)**: clink → gemini CLI → chat → consensus → synthesis
• **Main Claude**: Orchestrate clarification/enrichment process

**Phase 2 (Task Decomposition - ALL PATHS CONVERGE):**

• **planner tool**: Task breakdown, milestone definition, dependency mapping, structured planning
• **Main Claude**: Invoke planner with clear/enriched method

**Phase 3 (Final Plan Generation - ALL PATHS):**

• **Main Claude**: Generate and save plan.md directly from planner output (no intermediate review)

When to Use This Skill

Trigger this skill when the user requests:

• "Help me create a plan"
• "Generate plan.md"
• "Use planner for task planning"
• "Help me with task decomposition"
• "Create an implementation plan"
• "Plan the project"
• Any request for systematic planning and task breakdown

**Use Cases:**

• Feature development planning
• Project implementation roadmaps
• Refactoring strategies
• Migration plans
• Research initiatives
• Complex task breakdowns

Operation Mode (automation_mode - READ FROM SSOT)

automation_mode definition and constraints: See CLAUDE.md「📚 共享概念速查」

**This skill's role**: Skill Layer (read-only), read from context `[AUTOMATION_MODE: true/false]`

• `false` → Interactive: User confirms plan outline before saving
• `true` → Automated: Auto-approve decisions (plan outline, consensus), log to auto_log.md

Workflow: Intelligent Planning Process with Method Clarity Assessment

Overview: Decision Flow Based on Method Clarity

flowchart TD
    Start[User Request] --> Read[Read automation_mode from context]
    Read --> Judge{Use chat to judge:<br/>Method Clear?}

    Judge -->|Clear| Clear[Method Clear]
    Judge -->|Unclear| Unclear[Method Unclear]

    Clear --> CheckMode1{automation_mode?}
    Unclear --> CheckMode2{automation_mode?}

    CheckMode1 -->|false| Path1[Interactive + Clear:<br/>planner → plan.md]
    CheckMode1 -->|true| Path2[Automatic + Clear:<br/>planner → plan.md]

    CheckMode2 -->|false| Path3[Interactive + Unclear:<br/>chat dialogue → planner → plan.md]
    CheckMode2 -->|true| Path4[Automatic + Unclear:<br/>clink → chat → consensus → planner → plan.md]

    Path1 --> End[Final plan.md]
    Path2 --> End
    Path3 --> End
    Path4 --> End

Phase 0: Method Clarity Assessment (CRITICAL - First Step)

**Main Claude's Action:**

1. **automation_mode check**: `[AUTOMATION_MODE: false]` → Interactive / `true` → Automated

2. **Gather Initial Context:**

**a) Read Global Standards (CRITICAL):**

• **Global CLAUDE.md**: `/home/vc/.claude/CLAUDE.md` - Global rules (G1-G11), phase requirements (P1-P4), model development workflow

**b) Read Project-Specific Standards (if exist):**

• **Project CLAUDE.md**: `./CLAUDE.md` - Project-specific rules and processes

**c) Read Project Documentation:**

• PROJECTWIKI.md - Project knowledge base
• README.md - Project overview
• plan.md (if exists) - Existing plan
• docs/adr/*.md - Architecture Decision Records

**Standards Priority (when conflicts):** 1. Global CLAUDE.md (highest priority) 2. Project CLAUDE.md 5. PROJECTWIKI.md

3. **Invoke zen-mcp chat to assess method clarity:**

   Tool: mcp__zen__chat