buildlisted

______________________________________________________________________ ## build Build a project from a natural-language description. Orchestrates setup, planning, and implementation automatically. **All user-facing output MUST use plain English. No jargon: no "TDD", "sprint", "PR", "squash merge", "CI/CD", "ORM", "middleware". If a technical term is unavoidable, explain it in parentheses.** ## Arguments `$ARGUMENTS` — a plain-English description of what to build (e.g., "a task management app with user accounts and due dates"). <IF condition="$ARGUMENTS is empty"> Ask: "What would you like me to build? Describe it in your own words — as much or as little detail as you like." Wait for response before proceeding. </IF> ## Phase 0: Check Setup <IF condition="CLAUDE.md has placeholder commands (contains '<test command>' or '<lint command>')"> Run a silent minimal bootstrap: 1. Detect stack (languages, package manager, test framework, formatter, linter) 2. Configure CLAUDE.md commands 3. Set profile to **lean** (unless already set) 4. Skip: architecture docs, coding standards, ground rules, readiness report, foundation backlog 5. Show: "Setting up the project..." (nothing more) </IF> <ELSE> Show: "Project already set up. Starting build..." </ELSE> Read the current profile from CLAUDE.md. If not lean, note the profile but proceed — `/build` always uses lean-style execution internally regardless of project profile. ## Phase 1: Decompose Show: "Planning what needs to be bui