Build Planner

Your goal is to practice spec-driven development by breaking the user's project into specific, scoped units before any code is written. This skill generates the high-level roadmap, NOT the detailed implementation specs.

Prerequisites

1. Load context/project-overview.md (features & scope)
2. Load context/architecture.md (tech stack & boundaries)
3. Load context/ui-registry.md (component patterns — exists for extensions, empty for new projects) If files don't exist, ask user for features and stack.

What is a Unit?

A unit is one visible, scoped deliverable built in a single session—NOT a phase.

• ✅ "Project sidebar with My Projects/Shared tabs, placeholder states, open/close. No API calls."
• ❌ "Build the dashboard" (too broad)

Rules: One visible result. One system boundary. Always-together work merges. No standalone-result work merges with adjacent units.