build

# /build — Rigorous Build Skill > Structure > Willpower. The pipeline won't let you skip the parts that matter. > ALL development happens in an isolated worktree — zero conflict with other work. **When to use**: Any task that's more than a quick fix. Multiple files, needs tests, or would benefit from a plan. **When NOT to use**: Single-file edits, config changes, quick lookups. **Suggest to user when**: They describe a substantial feature, say "build", "implement", "create", or scope a multi-step task. --- ## Step 1: Initialize Build (MANDATORY) ```bash python3 playbook-scripts/build-state.py init "TASK DESCRIPTION" --size SMALL|STANDARD|LARGE ``` Size determines protection level: - **SMALL** (light): 3 stop-hook reinforcements, basic observability - **STANDARD** (medium): 5 reinforcements, full observability + review - **LARGE** (heavy): 10 reinforcements, full observability + multi-agent review **Model routing**: Use **Opus** for all coding, testing, architecture, and verification. Haiku only for quick file searches. --- ## Step 2: Create Worktree (MANDATORY) ALL build work MUST happen in an isolated git worktree. This prevents conflicts with other development: ```bash python3 playbook-scripts/build-state.py worktree-create ``` This creates: - A new branch (`build/<task-slug>`) from your current branch - A worktree at `.instar/worktrees/build-<task-slug>/` - All subsequent work happens in that directory **CRITICAL**: After creating the worktree, `cd` into it: `...