← ClaudeAtlas

add-feature-readbacklisted

Use when a feature's docs are closed and you need a cold reader to say back what they understood before anyone builds — catches docs that pass every review and still make the reader build the wrong thing.
brabos-ai/code-addiction · ★ 8 · Code & Development · score 78
Install: claude install-skill brabos-ai/code-addiction
# add-feature-readback — Cold-Read Comprehension Readback <!-- uses: - skill: add-plan-review - mention: add-code-review - mention: add-doc-schemas - mention: add-qa - agent: consistency-agent - agent: plan-reviewer-agent - agent: readback-agent --> ## Overview A **readback** is the aviation protocol: the tower gives an instruction, the pilot repeats it back in their own words, and the tower listens for the mismatch. Nobody asks the pilot "was the instruction clear?" — the pilot's own restatement is the test. This skill applies that to feature documentation. You read a feature's docs cold, with nothing else, and report **what you understood is going to be built**. You do not grade the docs. You do not ask questions. You say it back. The signal lives in the parent's hands, not yours. The parent agent has the conversation that produced the docs; you do not. Where your readback diverges from what was actually decided, **the document is what failed** — you are the instrument, not the suspect. A doc can satisfy every rubric in this repo and still steer a reader into building something else; that class of failure is invisible to a reviewer that asks "is this well written?" and visible only to a reader who says what they'd go build. Your blindness is the whole mechanism. Reading the source code, the referenced features, or the originating conversation would let you repair a gap in your head and report a comprehension the document never actually delivered. That is the one way t