Create standardized markdown templates for recording architecture decisions.
npx skills add https://github.com/Ermianr/meteor --skill adr-format-ermianr
Please help me install this Agent Skill. Skill: ADR Format Source: https://github.com/Ermianr/meteor/tree/main/.agents/skills/grill-with-docs Command: npx skills add https://github.com/Ermianr/meteor --skill adr-format-ermianr
This Skill simplifies the process of creating and maintaining Architecture Decision Records by providing a standard, lightweight markdown template and guidelines.
Use the ADR skill to generate a new ADR documenting a recent architectural decision efficiently.
High-intent search queries and answers about installing and using this skill.
An architecture decision record documents key technical trade-offs and design choices to maintain decision traceability across projects. You need an ADR when selecting new technologies or making structural design choices that require clear, consistent documentation.
To format architecture decisions in markdown, use a standardized template that structures the context, decision, and consequences. This lightweight format ensures consistent documentation and improves traceability across technical project files.
The best way to start documenting architectural decisions is applying a standardized markdown template to record trade-offs and design choices. This ensures team alignment and creates a traceable history of architectural decisions with minimal effort.
Yes, you can use this ADR template for documenting new technology choices. It guides technical teams to clearly record architectural decisions and design trade-offs, ensuring decisions are traceable and aligned with team documentation standards.
No dependencies are required to generate architecture decision records. This skill provides a lightweight markdown template and formatting guidelines directly, allowing you to document architectural decisions without external tool installations.
Your team needs a standardized template for architecture decision records to prevent fragmented documentation and lost context. Consistent markdown formatting ensures architectural decisions and trade-offs remain traceable and easily understandable across all projects.
vinvcnCreate architectural decision records using structured Markdown templates.
zzafergokConvert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.
TimoFreibergExplain code changes across Git and JJ diffs and pull requests.
Satcomx00-x00Create Architecture Decision Records in MADR 4 format with auto-numbering and commit links.
