← ClaudeAtlas

astra-implement-with-tddlisted

Build one ticket test-first in a Builder pane: one failing test per criterion before the code that passes it, at the seams the spec agreed, mocks only at system boundaries, the diff judged against the ticket before handback. Opens a Builder brief as its first line.
thientranhung/astragentic · ★ 4 · Testing & QA · score 73
Install: claude install-skill thientranhung/astragentic
# Implement, test-first The brief's first line is `/astra-implement-with-tdd <ticket>`. Fetch the ticket from the tracker, state its title, and read **What to build, Criteria, Must not change**, and for a UI ticket **Glance and States**, before any file is opened. The ticket distills the spec; open the spec only for a seam or FR the ticket cites. Ambiguous ticket: hand back, do not guess. ## Seams A **seam** is the public boundary a test observes behaviour through. Test at the seams the spec's Testing decisions agreed. A behaviour no agreed seam can see is a finding for the handback (the module's shape, not a workaround); test it at the nearest public interface and say so. Never at a private method, an internal collaborator, or a side channel (a `SELECT` after `createUser` instead of `getUser`). ## The loop, one criterion at a time Work in **vertical slices**: one criterion → one test → the least code that passes it → next. Never all tests first, never all code first. 1. **Red.** Write the one smallest assertion that defines the criterion and **must fail now**. Run it and watch it fail; the test-run log is how the harness knows red happened. A red test that passes means the behaviour already exists: say so in the handback, do not invent a failing assertion. 2. **Green.** Only the code that makes that assertion pass. No speculative feature, no second criterion's code. 3. **Commit the slice.** Refactoring is **not** in the loop; `simplify` runs once at the end