write-docs
Installation
SKILL.md
Capture an already-settled understanding into documentation. The decisions are made and the terms are agreed — write them down, do not re-litigate them. Take that understanding from the current conversation, a finished design discussion, or a merged decision, and record it:
- Write or update
CONTEXT.mdglossary terms using CONTEXT-FORMAT.md. - Offer ADRs sparingly using ADR-FORMAT.md.
No grilling. Do not run an interview loop, walk the design tree one question at a time, or invent edge cases to force precision — that work is out of scope here. If a fact can be checked in the codebase, check it instead of asking.