Analyze and refine Markdown Architecture Decision Records for clarity and maintainability.
npx skills add https://github.com/prisma/prisma --skill adr-review-prisma
Please help me install this Agent Skill. Skill: adr-review Source: https://github.com/prisma/prisma/tree/main/skills-contrib/adr-review Command: npx skills add https://github.com/prisma/prisma --skill adr-review-prisma
This skill addresses the common issue of Architecture Decision Records (ADRs) becoming stale, overly contextual, or difficult for new team members to understand by providing an objective, structural critique and rewrite.
Ask the agent to review the architecture decision record located at docs/adr/001-database-migration.md and rewrite it for clarity.
High-intent search queries and answers about installing and using this skill.
To improve Architecture Decision Records, analyze the Markdown files to identify context gaps, remove transient project metadata, and restructure the content into a decision-first format. This ensures long-term maintainability and readability for future engineers.
ADRs become stale when they contain buried decisions, missing context, or transient project-specific jargon. An objective structural critique and rewrite can remove outdated ticket references and enforce a clear narrative flow for future-proof readability.
The best way to rewrite technical documentation for maintainability is by enforcing a decision-first standard that prioritizes clear reasoning and alternative evaluation. This restructures content to remove transient metadata and clarify historical architectural decisions.
Yes, you can use this to prepare architecture documentation for onboarding by analyzing and refining ADRs. It ensures all historical architectural decisions are documented clearly and are free of outdated ticket references or project-specific jargon.
Yes, the ADR review process operates directly on Markdown-based ADR files. It analyzes the narrative flow and structural content to identify gaps and restructure the documentation without requiring additional file formats.
You should not use an automated ADR refactoring approach when your documentation requires subjective historical context that defies a decision-first standard. The process strictly prioritizes clear reasoning and alternative evaluation over retaining transient project metadata.
boomNDSCapture architectural decisions with ADR templates and rationale.
causify-aiGenerate structured README.md files documenting directory contents and executable tools.
nanorepublicaEnforce standardized test-writing guidelines within Claude Code workflows.
HellblazerCritique design artifacts against evidence and produce prioritized findings.
