arda/skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: end the build chain at implement, not tdd

Browse source 
The canonical build chain is grill-with-docs → to-prd → to-issues →
implement, with tdd as the red-green loop implement drives internally
rather than a chain step of its own.

- Update the chain diagram on grill-with-docs, to-prd, to-issues, and tdd.
- Reframe tdd's "Where it fits": it's the engine inside the implement
  step, still independently reachable, no longer the terminal.
- Point to-prd and to-issues at implement as the thing that builds the
  tickets, giving implement the inbound links it previously lacked.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Matt Pocock 2026-07-01 11:43:08 +01:00
parent b8c052f56e
commit f72b3d5bd4
4 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/engineering/tdd.md
View file

@ -38,10 +38,10 @@ Refactoring only happens once the suite is green; never while red.
## Where it fits
`tdd` is the final step of the main build chain:
`tdd` is the red-green loop the main build chain runs to write code:
```txt
grill-with-docs → to-prd → to-issues → tdd
grill-with-docs → to-prd → to-issues → implement
```
It implements the tickets the earlier steps produced. Its key neighbours are [to-issues](https://aihero.dev/skills-to-issues), which hands it an independently-grabbable issue to build, and [codebase-design](https://aihero.dev/skills-codebase-design), which it leans on to find deep-module seams worth testing at. When you're unsure which skill or flow fits, [ask-matt](https://aihero.dev/skills-ask-matt) routes you.
[implement](https://aihero.dev/skills-implement) is the chain's final step, and it drives `tdd` internally to build each ticket test-first — so `tdd` is the engine inside that step rather than a step of its own. You can also reach for it directly, whenever there's a concrete behaviour to build without a full spec. Its other neighbour is [codebase-design](https://aihero.dev/skills-codebase-design), which it leans on to find deep-module seams worth testing at. When you're unsure which skill or flow fits, [ask-matt](https://aihero.dev/skills-ask-matt) routes you.