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

2
docs/engineering/grill-with-docs.md
View file

@ -44,7 +44,7 @@ What makes this variant its own skill is where the answers go. As the grill runs
`grill-with-docs` is the opening step of the main build chain:
```txt
grill-with-docs → to-prd → to-issues → tdd
grill-with-docs → to-prd → to-issues → implement
```
It comes first, before anything is written down as a spec: it produces the shared understanding and settled vocabulary that [to-prd](https://aihero.dev/skills-to-prd) then synthesises into a PRD without re-interviewing you. Its close neighbours are [grilling](https://aihero.dev/skills-grilling), the same interview without the docs, and [domain-modeling](https://aihero.dev/skills-domain-modeling), the glossary-and-ADR discipline it drives. When you're unsure which skill or flow fits, [ask-matt](https://aihero.dev/skills-ask-matt) routes you.