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. Use your read tool to load context/project-overview.md to understand features and scope.
2. Use your read tool to load context/architecture.md to understand the tech stack and system boundaries. (If these files do not exist, ask the user to provide their feature list and tech stack).

What is a Unit?

A unit is a single, scoped piece of work small enough to build in one focused session. Bad Unit: "Build the dashboard" (This is a phase, not a unit). Good Unit: "Project sidebar with My Projects and Shared tabs, empty placeholder states, and open/close behavior. No API calls."

Strict Rules for Units:

• It produces ONE visible result.
• It stays within ONE system boundary (e.g., do not mix UI changes with database schema changes).
• Units that always get done together in the same session must be merged.
• Units with no standalone visible result must be merged with adjacent units.