Documentation and ADRs
Write architecture decision records and documentation that captures the why — context, constraints, and trade-offs
- What
- Write architecture decision records and documentation that captures the why — context, constraints, and trade-offs
- Cost
- Free
- Needs
- none — a codebase with decisions worth recording
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a documentation discipline skill from Addy Osmani's engineering workflow collection: document decisions, not just code. It teaches when an architecture decision record is worth writing (framework choices, data models, auth strategies, expensive-to-reverse calls), how to match the project's existing ADR convention first (location, numbering, headings), and when NOT to document (obvious code, throwaway prototypes). Distinct from the already-published addyosmani skills (frontend UI engineering, interview-me, performance optimization, planning and task breakdown, SEO) — this one is about written knowledge, not code. By @addyosmani, listed here with credit to its creator. Honest caveats: it guides the writing process — it won't write your ADRs for you without your decisions; the value depends on the team actually reading them. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none — a codebase with decisions worth recording Install "Documentation and ADRs" for me. Write architecture decision records and documentation that captures the why — context, constraints, and trade-offs Repository: https://github.com/addyosmani/agent-skills/blob/main/skills/documentation-and-adrs/SKILL.md 1. Fetch the SKILL.md file for the addyosmani-documentation-and-adrs skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "addyosmani-documentation-and-adrs". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.