Create and list Architecture Decision Records with automated numbering and markdown generation.
npx skills add https://github.com/Roxabi/roxabi-plugins --skill adr-roxabi
Please help me install this Agent Skill. Skill: adr Source: https://github.com/Roxabi/roxabi-plugins/tree/main/plugins/dev-core/skills/adr Command: npx skills add https://github.com/Roxabi/roxabi-plugins --skill adr-roxabi
This Skill streamlines the process of creating and managing Architecture Decision Records (ADRs), ensuring that the reasoning behind technical choices is clearly documented and easily accessible.
meta.json file for easy referencing and listing.Use the adr skill to create a new architecture decision record for "Using Bun as the runtime".
High-intent search queries and answers about installing and using this skill.
An architecture decision record (ADR) documents the context, options considered, final decision, and consequences of a technical choice. You should create an ADR whenever your team makes a significant technical decision to maintain clear knowledge management and mitigate technical debt.
To create an architecture decision record, the Skill guides you through interview-style questions to gather context, alternatives, and consequences, then automatically generates a structured markdown file with sequential numbering and updates a central meta.json file for tracking.
Yes, you can list existing architecture decision records to view a formatted table displaying each record's status and date, pulling metadata from the central meta.json file to provide a comprehensive overview of your technical decisions.
Yes, the ADR tool automatically determines the next sequential number for new architecture decision records, ensuring consistent ordering and preventing numbering conflicts when documenting technical choices across your software engineering projects.
The best way to document technical decisions is using structured architecture decision records that capture context, options, and consequences in markdown files with centralized metadata tracking, ensuring reasoning remains accessible and reducing future technical debt.
Managing architecture decision records via markdown files and a meta.json file provides lightweight, version-controllable documentation, but may lack advanced search or collaboration features found in dedicated knowledge management platforms for larger engineering teams.
salemazielDefine project directory structures, file naming conventions, and working standards.
OKHP3Automate creation and lifecycle management of Architecture Decision Records in Markdown.
Extremez-SuryaAutomate the release process for vercel-plugin with gates, version bump, artifacts, commit, and push.
BuiDommManage persistent markdown-based project wikis with CRUD operations and keyword search.