build

# zuvo:build — Scoped Feature Development A tiered workflow for implementing new features with bounded scope. Ceremony scales with risk: a 2-file utility addition runs LIGHT (no agents, no auditors), while a service touching auth runs DEEP (parallel analysis agents + independent auditors). **Scope:** Features affecting 1-5 production files. Test files, backlog entries, and run-log do not count toward the file limit. **Out of scope:** Bug investigation (`zuvo:debug`), structural reorganization (`zuvo:refactor`), code review (`zuvo:review`), multi-file features with unclear scope (`zuvo:brainstorm` pipeline). **Scope expansion:** If implementation reveals that the feature requires >5 production files, STOP. Ask the user: continue as build (with justification) or escalate to `zuvo:brainstorm`? Structural splits (extracting helpers to respect file-limits.md thresholds) may auto-expand up to +2 production files without asking. Beyond +2, ask the user. ## Argument Parsing Parse `$ARGUMENTS` for these flags: | Flag | Effect | |------|--------| | `--auto` | Auto-approve the implementation plan (skip Phase 2 user confirmation) | | `--auto-commit` | Commit staged changes without asking (skip Phase 4 confirmation) | | `--tag` | Create a `build-YYYY-MM-DD-slug` rollback tag after commit | | `--deep` | Force DEEP tier regardless of file count or risk signals | | _(remaining text)_ | The feature description | Flags can be combined: `zuvo:build add CSV export --auto --auto-commit --t...