Review surfaces a teammate actually reads, not a Markdown wall that gets skimmed. One self-contained HTML page per plan, review, or decision, enforced by a validated content contract.
npx skills add rhnfzl/human-html
A forward-looking work plan with scope, milestones, risks, and a rollback path.
reviewA critique of a code change or PR, with findings ranked by severity.
architectureAn explainer of how a system works, with diagrams and open questions.
understandingWhat the team learned tracing a flow end to end through the code.
researchExternal evidence synthesized into an options comparison and a recommendation.
decisionA locked choice laid out with options, trade-offs, and consequences.
prototypeA live, interactive demo that still reads with JavaScript disabled.
statusA snapshot of where work stands: progress, blockers, and next steps.
incidentA postmortem with a timeline, impact, root cause, and corrective actions.
Each of the nine comes with the sections its doc has to have, which is right until the shape is part of what you are saying. In dynamic mode the agent decides the structure and the floor still holds: a plain summary up top, a diagram in every comparison, readable on a phone with the scripts off. The shape is its call, the styling is not. These three share no structure on purpose.
What a proposal missed, banded by how badly each finding bites rather than by where it lives.
design directionsFour candidate designs judged against one identical replayed day, then a pick.
port correspondenceA port mapped region by region, with a behaviour ledger of what changed and what did not.