lanternfyre/docs
The documentation standard: people-first pages, ADRs, glossary and objectives, with structure checks and reader walkthroughs.
Write, supersede, review or audit an architecture decision record in docs/decisions/. Use whenever an architectural decision is settled or reversed, and to check whether one is worth recording at all.
Audit a repo's documentation. Structural health, drift between docs, decisions and code, content problems, and the operator's own reader walkthrough, each reported separately. Run at milestones or when docs feel untrustworthy.
Build and maintain the project's ubiquitous language in docs/domain/glossary.md. Harvest candidate terms from docs, code and beads, settle synonyms and homonyms with the operator, write short entries agents can rely on, and check text against them.
Bring a repo onto the documentation standard. Inventory what exists, propose the smallest layout its real content and readers need, preserve established layouts unless reorganization is authorized, and seed the landing README and project instructions.
Capture business objectives in docs/product/objectives.md as measurable outcomes written in glossary terms and agreed with the operator, so every requirement, epic and bead can say which objective it serves.
Write, move or restructure a documentation page (docs/ or a README) so a person can use it. Pick the reader and their question, reuse what exists, choose the smallest useful form, then check structure and walk the reader route. Use before any docs page is created or substantially changed.