dev-buildlisted

# Build **PHASE 2** of the dev workflow: define → **build** → verify → refactor (optional) Auto-detects stack from CLAUDE.md, assigns TDD to all testable requirements; Implementation Only only when automated tests add no value (visual/config/prototype). **Trigger**: `/dev-build` or `/dev-build [feature-name]` ## Input Reads `.project/features/{feature-name}/feature.json`: requirements (REQ-XXX), architecture, implementation order. ## Output ``` .project/features/{feature-name}/ └── feature.json # Enriched with build, packages, tests.checklist sections ``` ## Process Six phases run sequentially: 1. PHASE 0: Context Loading 2. PHASE 1: Technique Mapping 3. PHASE 2: Execute Build 4. PHASE 2b: Regression Gate + Diagnostics 5. PHASE 3A: Project Sync 6. PHASE 3B: Scoped Commit ### PHASE 0: Context Loading > **Todo**: Call `ToolSearch query="select:TaskCreate,TaskUpdate"` — both tools are deferred and unusable without their schemas. Then `TaskCreate` with the 6 phase items above (status `pending`); use `TaskUpdate` to flip each PHASE to `in_progress` at start and `completed` at end (task list survives context compaction). Mark PHASE 0 → `in_progress`. Read `.claude/skills/dev-build/references/context-loading.md` and follow all steps in order. ### PHASE 1: Technique Mapping > **Todo**: mark PHASE 0 → `completed`, PHASE 1 → `in_progress`. **REMOVED filter**: Requirements with `deltaOp === "REMOVED"` — skip, don't assign technique, don't show in technique map table.