Runs stage D after a requirement is delivered, or over a span of time. Gathers what the sessions, the MR and the delivery records show, has a model from another family mine them for lasting gaps too, routes each gap to where it gets fixed, records it in the…
One owner implements a requirement and delivers a mergeable MR/PR. Use after spec.md and verify.md are confirmed and frozen.
Design rules and a change process for prompts written for agents, multi-agent pipelines and SKILL.md files, based on official sources. Use when writing, changing or reviewing any of them.
Explains a topic in plain, literal language for someone who knows nothing about it. Use when someone new to a topic asks for an explanation from the basics.
Turns existing requirements, design discussions and technical materials into a self-contained technical review document. Use when a technical design goes to people for review.
Draws hand-drawn style technical diagrams (architecture with trust zones, request and data flows, sequences, lifecycles) as an editable HTML source and a layout-checked PNG for design docs, PR descriptions, reviews and slides. Use when asked to draw, redraw…
Applies five review criteria (correctness, minimal change, proportionate complexity, extensibility, clear ownership) to code and designs. Use when reviewing code or a design, rechecking review findings, or judging a proposed fix.
Converges a conversation and its materials into spec.md, the core decisions; when delivery will be automated, also writes verify.md, the acceptance requirements. Use after discussion and clarification are finished, including when the user confirms…