---

name: planning description: "This skill should be used when designing implementation plans, decomposing complex work into tasks, or making architectural decisions during ultrawork sessions. Used by orchestrator (interactive mode) and planner agent (auto mode)."

Planning Protocol

Overview

Define how to analyze context, make design decisions, and decompose work into tasks.

Two modes:

• Interactive: Orchestrator conducts Deep Interview for decisions
• Auto: Planner agent makes decisions based on context alone (--auto or --skip-interview)

---

Phase 1: Read Context

Read session files in order:

1. session.json - goal and metadata
2. context.json - summary, key files, patterns from explorers
3. exploration/*.md - detailed findings as needed

---

Phase 2: Complexity Analysis

Analyze goal and context to determine interview depth:

Note: User can request more rounds via adaptive check. No upper limit.

---

Phase 3: Deep Interview (Interactive Mode)

Skip if: --auto or --skip-interview flag set

Interview Structure

Each round asks 4-5 questions using AskUserQuestion (max 4 questions per call).

Context-Aware Options (CRITICAL)

Options marked [...] MUST be generated from exploration context, NOT generic templates.

See references/context-aware-options.md for:

• Generation process from context.json and exploration/*.md
• Option generation rules by question type
• Context-aware vs generic examples
• Validation checklist

Interview Rounds

Rounds are adjusted based on complexity assessment:

Note: User can request additional rounds via adaptive check. No upper limit.

See references/interview-rounds.md for:

• Detailed question templates for each round
• Domain-specific question templates
• Adaptive check pattern
• Decision recording format

---

Phase 4: Document Design

IMPORTANT: Design documents go to PROJECT directory.

CopyWORKING_DIR=$(bun $SCRIPTS/session-get.js --session ${CLAUDE_SESSION_ID} --field working_dir)
DESIGN_PATH="$WORKING_DIR/docs/plans/$(date +%Y-%m-%d)-{goal-slug}-design.md"

Write comprehensive design.md including:

• Overview and approach selection
• Interview decisions with rationale (from Phase 3)
• Architecture and components
• Error handling strategy
• Testing strategy
• Scope (in/out)

See references/design-template.md for complete template.

---

Phase 5: Decompose Tasks

Task Guidelines

Create Tasks with Scripts

Use task-create.js for each task. Always include a final verify task.

See references/task-examples.md for:

• Complete script command examples
• Task decomposition patterns by feature type
• Dependency graph examples

---

Output Summary

Return planning summary with:

• Complexity assessment and interview rounds completed
• Key decisions from interview (table format)
• Task graph showing IDs, subjects, dependencies, complexity
• Files created (design doc, task files)

---

Flag Reference

Additional Resources

Reference Files

• references/brainstorm-protocol.md - Interactive question flow and approach exploration
• references/context-aware-options.md - Context-aware option generation rules and examples
• references/design-template.md - Complete design document template
• references/interview-rounds.md - Detailed interview round templates for all complexity levels
• references/task-examples.md - Task decomposition examples with script commands