Create Architecture Decision Records with context, rationale, and impact analysis.
npx skills add https://github.com/macrat/markdown-board --skill create-adr-macrat
Please help me install this Agent Skill. Skill: create-adr Source: https://github.com/macrat/markdown-board/tree/main/.claude/skills/create-adr Command: npx skills add https://github.com/macrat/markdown-board --skill create-adr-macrat
This Skill helps you systematically document important technical and functional decisions made during development, ensuring clarity, preventing repeated discussions, and preserving institutional knowledge.
Use the create-adr skill to document a new Architecture Decision Record for the decision to not implement a real-time collaboration feature.
High-intent search queries and answers about installing and using this skill.
Document technical decisions by creating Architecture Decision Records (ADRs) that capture context, rationale, and impact analysis. This structured documentation prevents repeated discussions and ensures critical choices are recorded for future reference.
Record rejected features in architecture documentation by creating an ADR detailing the rejection, its justification, and impact on the product roadmap. This ensures the reasoning behind not implementing a feature is preserved.
Create an Architecture Decision Record by following a guided, structured process to document technical and functional decisions. This process ensures all critical choices, trade-offs, and context are systematically recorded.
Write an ADR when making significant technical or functional choices during development, especially decisions involving trade-offs or alignment with product philosophy. This prevents clarity loss and avoids rehashing settled discussions.
Yes, ADRs document trade-offs and impact analysis by guiding you through a structured process to record critical choices. This ensures that the context and consequences of architectural decisions are clearly maintained.
Creating architecture decision records requires no specific external dependencies or tools. The process is automated through structured scripts and references that guide the documentation of context and rationale.
sinositatoGather problem, user, scope, and success criteria into a markdown context file.
lucidlabs-hqPublish markdown documents to private Notion pages with block mapping.
felix-howardAnalyze codebase changes and generate or update project documentation files.
CygnusfearDocument engineering decisions as ADRs with rationale and decision logs.
