Project Planner

Break a large, complex project into manageable tasks with clear dependencies, progress tracking, and a visual diagram.

Project to Plan

$ARGUMENTS

Planning Workflow

This skill has exactly two possible outputs: a full plan (Phases 0-4), or (when the scope fails the gate in Step 0.2) clarifying questions and nothing else. Never both in the same turn.

Portability: No Task/TaskCreate tools in this environment? Do the analysis yourself instead of delegating to an Explore agent, and track the resulting tasks as a plain markdown checklist (- [ ] Task name, blocked by: ...) instead of TaskCreate calls. The phases and the dependency diagram are the deliverable; the Task tool is just Claude Code's way of tracking them. In an eval or sandbox run, never call the real session Task/TaskCreate/TaskUpdate/TaskList tools: those mutate the operator's actual task list. If the prompt instead asks you to record intended calls into a file (e.g. outputs/tasks.json), do that instead and treat it as the graded deliverable.

Phase 0: Project Analysis

Step 0.1: Understand Project Scope

Use a Haiku-powered Explore agent for token-efficient codebase analysis: