project-plannerlisted

# Project Planner ## Overview Turns a fuzzy goal into a concrete, scheduled plan. Produces a Work Breakdown Structure (WBS), milestones, an explicit dependency graph, defensible effort estimates, a critical path, and a risk register. Keywords: project plan, work breakdown structure, WBS, milestones, dependencies, critical path, estimation, scheduling, roadmap, task decomposition, Gantt, sequencing. Use this skill whenever the input is a goal/spec/idea and the desired output is "what needs to happen, in what order, and roughly how long". ## When to use - "Plan the migration to X" / "Break this feature into tasks" / "Build a roadmap for Q3". - The user has a deliverable but no task list, sequence, or estimate. - An existing task list needs dependencies, estimates, or a critical path added. ## Workflow Follow these steps in order. Do not skip clarification. 1. **Clarify the goal and constraints.** Capture: the single end deliverable ("done" definition), hard deadline (if any), team/resource availability, and any fixed external dependencies. Ask at most 3–5 sharp questions if these are missing. See `references/clarifying-questions.md`. 2. **Decompose into a WBS.** Break the goal top-down into deliverable-oriented work packages using the 100% rule (children fully cover the parent, no overlap). Stop decomposing at the 8/80 rule: each leaf task is 8–80 hours of work. Number hierarchically (1, 1.1, 1.1.1). See `references/wbs-method.md`. 3. **Define milestones.** Mark zero-dura