project-plan

## Purpose Produce a project plan that defines scope, milestones, timeline, ownership, dependencies, budget, quality standards, and risk at the delivery level - the document that answers "what are we building, in what order, who owns each part, and by when" for anyone tracking the project, not just the engineers building it. **This is not a technical design document.** It does not specify how any single component works - it specifies the shape and sequence of the overall effort so that individual technical-blueprint and implementation-plan documents have a timeline and ownership structure to slot into. ## Input **Works best with:** The name of the project and a description of its overall goal and scope. **Also valuable:** Team size and roles, hard deadlines or launch dates, budget constraints, known dependencies on other teams or vendors, prior similar projects and how long they took. **Example invocation:** `Create a project plan for building a subscription-billing SaaS product from scratch. Team of 3 engineers, 1 designer, 1 PM. Target: usable beta in 3 months. No hard external deadline but investors expect a demo by month 4.` ## Key Concepts ### Work Breakdown Structure (WBS) Decompose the project into progressively smaller deliverables until each leaf item is small enough to estimate confidently (typically 1 day - 2 weeks of work). A WBS is a tree, not a flat list: Project -> Phases -> Workstreams -> Deliverables -> Tasks. ### Estimation Methodology Use a structu...