Documentation And Adrs

The repo's ADR and documentation STANDARD — capture the WHY (context, constraints, rejected alternatives), not just the what. Reach for this whenever you make a hard-to-reverse architectural decision, supersede an old one, change a public API, ship a user-facing feature, or record context a future engineer or agent will need. spec-grilling, codebase-design, api-design, and the Ship skills all defer to this format — do NOT hand-roll an ADR or invent your own doc layout.

celestialdust Updated 1 repo stars

File contents

celestialdust/achilles-skills commit 24ff7208ab

Frequently asked questions

npx get-skill add celestialdust/documentation-and-adrs