buildlisted

# Build A structured 4-phase approach to every build. Forces research and planning before a single line of code is written. Prevents building the wrong thing fast. The 4 phases must happen in order. Claude does not move to the next phase until Naveen approves the current one. --- ## The 4 Phases ### Phase 1 — Research Before planning anything, understand the problem and the landscape. Claude must answer: - What is the best approach for this specific problem? - What libraries, APIs, or tools are most appropriate? - What are the known pitfalls or edge cases for this type of build? - Are there simpler alternatives to what Naveen described? Output: a short research summary (5–10 lines max). No code yet. Wait for Naveen's approval before moving to Phase 2. --- ### Phase 2 — Plan Turn the research into a concrete, step-by-step build plan. Claude must produce: - A numbered list of build phases (each phase = one logical chunk of work) - What each phase produces (a file, a function, a working endpoint, etc.) - Any dependencies between phases (Phase 3 requires Phase 2 to be complete) - Estimated complexity per phase (simple / moderate / complex) Output: a structured plan. No code yet. Each phase in the plan maps to a separate git branch: `feature/phase-1-scaffold`, `feature/phase-2-core-logic`, etc. Wait for Naveen's approval before moving to Phase 3. --- ### Phase 3 — Track Before implementing, create a tracking checklist from the plan. Claude must produce: - A che