Architecture Decision Records
Capture architectural decisions as numbered ADRs with context, alternatives, and consequences.
- What
- Capture architectural decisions as numbered ADRs with context, alternatives, and consequences.
- Cost
- Free
- Needs
- Use "Architecture Decision Records" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a workflow for capturing architectural decisions as they happen, so they stop living only in chat threads, PR comments, or someone's memory. Uses the lightweight ADR format (context, decision, alternatives considered with pros/cons and explicit why-not, consequences split into positive, negative, and risks) stored as numbered markdown files in docs/adr/, with an index README and a blank template for manual use. The skill watches for decision moments in conversation, both explicit ("let's go with X", "record this as an ADR") and implicit (comparing two frameworks and reaching a conclusion, choosing an auth strategy), then gathers the context, documents the rejected alternatives, and presents a draft for your approval before writing anything. Covers the ADR lifecycle (proposed, accepted, deprecated, superseded by a newer ADR), what makes a good ADR (specific, readable in two minutes, honest about trade-offs, never an essay), and which decision categories deserve one: technology choices, architecture patterns, API design, data modeling, infrastructure, security, and testing. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; it asks for your confirmation before creating any files, and trivial decisions (naming, formatting) do not deserve an ADR. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Architecture Decision Records" with your Muse. Prerequisites: the Muse app (mobile or web). Pure guidance skill, nothing to install. A codebase where architectural decisions are being made. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/architecture-decision-records/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "We just decided [decision]. Record it as an ADR: context is [context], alternatives were [alternatives]." 3. Review the draft ADR Muse produces (context, decision, alternatives, consequences) and approve it before it writes the file to docs/adr/. Tip: when you are torn between two options, ask Muse to lay out the ADR with both alternatives first. Writing the trade-offs down often makes the decision obvious. Safety: a skill is plain-text instructions; it runs nothing by itself. Review every ADR draft before approving the file write, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
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.