Creates Markdown decision records with YAML frontmatter documenting architectural choices, including scope, context, options, and consequences.
npx skills add https://github.com/nist0/CoDev --skill adr-nist0
Please help me install this Agent Skill. Skill: adr Source: https://github.com/nist0/CoDev/tree/main/.github/skills/adr Command: npx skills add https://github.com/nist0/CoDev --skill adr-nist0
This Skill provides a structured approach to making and documenting architectural decisions, ensuring clarity, collaboration, and traceability.
Invoke the adr skill with 'adr create [decision-title] [stakeholders]' to initiate the creation of an ADR for a new decision.
High-intent search queries and answers about installing and using this skill.
Architecture decision records provide structured documentation to track why specific architectural choices were made, ensuring clarity and traceability over time. This approach captures decision scope, context, options, and consequences in a standardized format.
Architecture decision records use YAML for frontmatter and Markdown for the body to structure architectural decisions. This standardized format captures decision scope, context, options, and consequences, encouraging involvement from all relevant stakeholders in the decision-making process.
To create an architecture decision record, invoke the skill with a decision title and stakeholder list. This initiates a structured template that documents the decision scope, context, available options, and resulting consequences for team alignment.
You need architecture decision records when working on large software projects that require structured decision-making and stakeholder collaboration. Documenting architectural decisions ensures all team members understand the context and remain aligned on system architecture choices.
Architecture decision records require YAML for frontmatter and Markdown for the body content. This format supports documenting decision scope, context, options, and consequences to ensure structured architectural decision-making and traceability.
Documenting architectural decisions with this approach requires no external dependencies. It relies solely on standard YAML for frontmatter and Markdown for body text to generate structured records that capture scope, context, options, and consequences.
boomNDSCapture architectural decisions with ADR templates and rationale.
abhishekdutta18Create structured architecture decision records in markdown files.
argenAppend customer events to a chronicle entry via script.
ulises-jeremiasConvert unstructured meeting notes into structured minutes with action items.
