← ClaudeAtlas

devlisted

Ticket-driven DEV pipeline, end-to-end — preflight (tracker/design-source/git/DB pinged for real) → fetch the ticket → read spec + schema (the ticket is a claim, the spec is the spec) → UI tickets pull the design from the ticket's design link (design source = visual oracle; exact colors/spacing/text from node data) → implement on a feature branch → /verify gate + evidence → self-review with machine-measured design fidelity → 2 fresh review agents must approve (+1 on high-stakes diffs; committed review trail enforced at pre-push) → push + PR → mandatory 7-part plain-language report comment on the ticket, then transition to In Review (Done belongs to /qa). Runs the machine DoR gate and claims the ticket before coding.
connorpham/vteam-harness · ★ 6 · Code & Development · score 81
Install: claude install-skill connorpham/vteam-harness
> **Model routing for this tool** (from `model-routing.data.yaml`, snapshot 2026-08-17): > `frontier` → **fable** · `workhorse` → **opus** · `standard` → **sonnet** · `utility` → **haiku** > Roles → tiers: ba-challenger: standard · ba-draft: standard · dev-r1: workhorse · dev-r2: standard (high-stakes: workhorse) · dev-r3: workhorse · explore: utility · qa-challenger: standard · sa-background: workhorse · sa-challenger: workhorse · sa-writer: workhorse > Resolve at runtime: `python3 .vteam/scripts/model_route.py <role> --tool claude-code [--high-stakes]` — high-stakes diffs (review.high_stakes_*) bump dev-r2 to the workhorse tier. > Spawning a subagent: pass the resolved name as the Agent tool's `model` parameter. # /dev — implement a ticket, prove it before delivering **Immutable principles** (violation = the task is not done): 1. **The spec is the spec, the ticket is a claim.** Expected behavior comes from the spec shard (`docs/specs/<feature>.md`) and the schema — never from ticket prose alone. Ticket contradicts spec/schema → STOP and ask before coding. 2. **No code before understanding.** T1's task-sheet (requirement, acceptance criteria, touched models/routes, cited sources) must exist before the first edit. Ambiguous ticket → ask, do not guess. 3. **Minimal, surgical change** (the `guidelines` workflow is the method authority — load it). No drive-by refactors, no scope expansion; a side finding gets its own note/ticket (T5), never smuggled into thi