duet

Design test strategy using Beck's Test Desiderata — which properties matter, which tradeoffs to make. Use when the user asks "how should I test this", "what tests do I need", "review my test strategy", "is this well-tested", or when planning tests for a new feature or refactor.

Survey the project and choose what to play next

Turn a PR, branch, commit, or git diff into a structured visual recap so a reviewer scans the shape of the change before reading raw lines. Use when asked to "recap this PR/branch", "show me what changed", or to summarize a large multi-file diff at a higher altitude than line-by-line review.

Audit whether someone dropped into an arbitrary file can tell where they are and where to go next. Use when the user says "onboarding is painful", "agents get lost in this repo", "nobody can find their way around", "add breadcrumbs", or when an /ia pass fixed the structure but readers still stall.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable. Reach for it when authoring, pruning, or debugging a skill.

Step up a layer of abstraction to map how unfamiliar code fits into the larger system. Use when the user says "zoom out", "bigger picture", "I don't know this area", "give me a map", "where does this fit", is reading code and feels lost, or is about to change unfamiliar code.