{"enrichment":{"faq":[{"a":"writing-adrs guides you through creating Architecture Decision Records that capture load-bearing choices, their rationale, and trade-offs. Start with a sequential number in docs/adr/, use the simple template (Context, Decision, Consequences), and keep most ADRs to a single paragraph. Focus on decisions that are hard to reverse, surprising without context, or chosen among genuine alternatives.","q":"How to write architecture decision records?"},{"a":"writing-adrs recommends creating an ADR when a decision qualifies as load-bearing: it's hard to reverse, surprising without explanation, or the result of weighing real alternatives. Skip ADRs for routine choices or reversible experiments. If you're unsure whether a decision needs recording, the skill helps you apply these criteria to decide.","q":"When should I create an ADR?"},{"a":"writing-adrs teaches the standard ADR structure: sequential numbering in docs/adr/, a title, and core sections for Context (the problem), Decision (what you chose), and Consequences (trade-offs and impact). Optional sections like Status and examples are available. Most ADRs fit in a paragraph; the template keeps them concise and scannable.","q":"What is the ADR template and format?"},{"a":"writing-adrs covers ADR numbering and organization in docs/adr/. Each record gets a sequential number (0001, 0002, etc.) as its filename. The skill explains how to structure your docs/adr/ folder, maintain the sequence, and keep records discoverable and linked for teams reviewing architectural decisions.","q":"How does writing-adrs handle ADR numbering and organization?"},{"a":"writing-adrs teaches when to include optional sections like Status (Proposed, Accepted, Superseded) and Consequences in your Architecture Decision Records. These sections add context for decisions that need tracking or have complex downstream effects. The skill helps you decide which optional elements fit your decision's scope and audience.","q":"What optional ADR sections does writing-adrs include?"},{"a":"writing-adrs defines ADR-worthy decisions as those that are hard to reverse, surprising without context, or chosen among alternatives. Examples include tech stack choices, major refactors, and trade-off decisions. The skill helps you distinguish load-bearing architectural choices from routine implementation details that don't need formal recording.","q":"What qualifies as an architecture decision for an ADR?"}],"shadow_tags":["decision-documentation","architectural-governance","design-rationale","knowledge-capture","technical-decisions","reversibility-analysis","context-preservation","trade-off-recording","future-proofing"],"summary_rewrite":"This skill guides you through writing Architecture Decision Records\u2014concise documents that capture the shape of load-bearing choices, why you made them, and what trade-offs you considered. Use it when a decision is hard to reverse, surprising without context, or the result of genuine alternatives. ADRs live in docs/adr/ with sequential numbering and a simple template; most need just a paragraph."},"files":[{"bytes":3735,"path":"original/writing-adrs/SKILL.md","sha256":"5202eb61d967714168101f53163acbf9d598ec63b2fb763435d5376286136b96","url":"https://skillfed.io/files/frankify-app/skills/writing-adrs/ef4bf94b/SKILL.md"}],"id":"frankify-app/skills/writing-adrs","links":{"html":"https://skillfed.io/frankify-app/skills/writing-adrs","md":"https://skillfed.io/frankify-app/skills/writing-adrs.md","repo":"https://github.com/frankify-app/skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":0,"language":"Shell","last_updated":"2026-07-27","license":"MIT","name":"writing-adrs","publisher":"frankify-app","stars":0},"relations":{"categories":["architecture","documentation","decision-management"],"similar":[{"id":"frankify-app/skills/domain-modeling"},{"id":"frankify-app/skills/to-spec"},{"id":"rengwu/wayfinder-maps/domain-modeling"},{"id":"vinvcn/mattpocock-skills-zh-CN/domain-modeling"},{"id":"mattpocock/skills/domain-modeling"},{"id":"frankify-app/skills/to-tickets"},{"id":"mxyhi/ok-skills/domain-modeling"},{"id":"Tiberriver256/mcp-server-azure-devops/domain-modeling"},{"id":"dirnbauer/webconsulting-skills/grill-with-docs"},{"id":"ArcReel/ArcReel/domain-modeling"}]},"slug":{"owner":"frankify-app","repo":"skills","skill":"writing-adrs"},"version":"ef4bf94b"}
