Agent skills
rd-retro
Score one finished build against the workflow using only what Radial and git already hold, and turn each finding into a wrapper you can paste.
rd-retro reconstructs what happened on one tree from the record it left,
scores the workflow rules with quoted evidence, and turns each finding into a
wrapper section you can install. It changes nothing, so it is safe to run on
anyone's tree.
Audit one finished build against the rd-* workflow using only what Radial, the keyboard-first issue tracker, and git already hold: the tree, its activity, its comments, the pull request and the commits.
When to use it
After a tree merges, or when a build felt worse than it should have and you want to know where it actually went. Not mid-build: the record is not there yet.
What it asks you
The parent id, and nothing else. It cannot ask you what happened, and that is deliberate: a retro built on recollection scores the story rather than the run. Everything it says cites a timestamp, an issue id or a commit.
What it writes
Nothing. Not to Radial, not to git, not to a file. It reports a scorecard, a list of where the time went, and up to three proposals, and it says so at the end.
What it scores
Whether the tree was filed before the first build commit. Whether each child went in progress and then in review rather than jumping. Whether each child has an implementation-notes comment, and whether that comment names the acceptance lines. Whether a prototype was attached where the plan had a UX line. Whether sibling ids were scrubbed in the pull request body. Whether the tree ended in review rather than being closed by the merge. Whether writes ran serially. Whether any child was skipped.
A rule it could not check is stated as "not checkable here", with the reason and what would make it checkable. It is never silently a pass.
Three proposals, no more
Each one is phrased as a wrapper section you can paste, which is how a lesson survives the session it was learned in. Twelve proposals change nothing, so it stops at three and says which file each goes in.
Extension points
| Hook | What a section here adds |
|---|---|
extra-rules | House rules to score alongside the built-in ones: a required reviewer, a branch convention, a cycle boundary, a deploy note |
score-bar | Raise the bar before the scorecard is shown: a minimum evidence standard, a required verdict sentence, a pass threshold |
after-retro | Where the retro goes: a comment on the parent, a team doc, a recurring agenda item |
A worked wrapper
---
name: eng-retro
description: Our extra retro rules on top of rd-retro.
extends: rd-retro
---
Read rd-retro first, then apply the sections below at their hooks.
## extra-rules
- Score whether the branch name carries the parent id.
- Score whether every child was pushed before the session that built it ended.
- Score whether the pull request body names a reviewer.
## score-bar
- Every row cites a timestamp or an id. A row citing only a title is a fail.
- The verdict is one sentence and must be consistent with the rows.
## after-retro
- Post the scorecard as a comment on the parent issue so it is findable from
the tree rather than from a chat log.What it never does
It never writes anything. It never scores a rule it could not check as a pass. It never states a cause it cannot evidence from the record: "a 90-minute gap with no events" is a finding; "the agent got stuck" is a guess. And it never produces a fourth proposal.