Generate numbered Architecture Decision Records as Markdown files.
npx skills add https://github.com/peel/fiddle --skill adr-peel
Please help me install this Agent Skill. Skill: adr Source: https://github.com/peel/fiddle/tree/main/skills/adr Command: npx skills add https://github.com/peel/fiddle --skill adr-peel
This Skill streamlines the creation of Architecture Decision Records (ADRs), ensuring that critical design choices are formally documented with their context, decisions, and consequences.
Use the adr skill to create a new architecture decision record for using AlloyDB over CloudSQL.
High-intent search queries and answers about installing and using this skill.
An architecture decision record (ADR) documents critical design choices, capturing their context, decisions, and consequences. You need to create an ADR whenever your team makes a significant technical decision, such as switching database technologies, to ensure formal documentation of the rationale and implications.
To generate an ADR file, you use the skill to prompt for essential details like context, decision, and consequences. It automates the formatting of these inputs into a structured Markdown file, adhering to specific filename conventions and supporting the creation of the target directory if it does not exist.
Yes, you can automatically number architecture decision records sequentially. The skill assigns the next sequential number to new ADRs automatically, ensuring consistent ordering and tracking of technical decisions within your specified directory structure.
Yes, the ADR generation process supports creating a new directory structure if it does not exist. When you generate an architecture decision record, the skill will automatically create the target directory to ensure the Markdown file is saved in the correct location.
The best way to document a database technology switch is to generate an architecture decision record. This records the context, decision, and consequences of the change, ensuring your team has a formal, structured Markdown document outlining the reasons and implications for the technology migration.
OKHP3Automate creation and lifecycle management of Architecture Decision Records in Markdown.
Happy-Technologies-LLCSummarize Architecture Decision Records from ServiceNow into executive-ready narratives.
baasith6Document technical decisions using structured Architecture Decision Records with sequential numbering.
PriyanshKuniyalDocument and manage architectural decision records with templates and lifecycle statuses.
