Generate ADR files in wiki/adrs/ with context, decision, and consequences.
npx skills add https://github.com/ImLp/claude-caide --skill adr-imlp
Please help me install this Agent Skill. Skill: adr Source: https://github.com/ImLp/claude-caide/tree/main/.claude/skills/adr Command: npx skills add https://github.com/ImLp/claude-caide --skill adr-imlp
Architectural decisions shape the long-term health of a codebase, but are often poorly documented or scattered across ad-hoc notes. This skill provides an interactive workflow to create, update, and reference Architectural Decision Records (ADRs) stored in wiki/adrs/, preserving reasoning, context, and consequences for future developers.
Trigger the adr workflow with /adr [title] to begin a new ADR in wiki/adrs/ and respond to prompts to capture context, decision, consequences, and files to modify.
High-intent search queries and answers about installing and using this skill.
You document architectural decisions by interactively generating ADR files in wiki/adrs/ with context, decision, and consequences. This skill guides you through prompts to capture essential fields and ensures ADR status tracking for future reference.
Tracking architectural decision status during a refactor involves updating ADR states like proposed, accepted, superseded, or deprecated. This skill enables status tracking and cross-referencing with related wiki modules to maintain consistency across decisions.
To create an ADR for codebase change planning, trigger the workflow with /adr [title] and respond to interactive prompts. You will capture context, decision, consequences, and files to modify to document rationale and expected impact before changes occur.
Yes, you can cross-reference architectural decision records with wiki modules. When generating ADRs in wiki/adrs/, the skill automatically links to related wiki modules and allows cross-referencing with related decisions for comprehensive codebase governance.
Before generating an ADR file, prepare the architectural context, the decision rationale, expected consequences, and a list of files to modify. The interactive interviewing process will prompt you to supply these essential fields to ensure consistency across records.
Use an interactive ADR workflow instead of ad-hoc documentation when planning major refactors, codebase change scenarios, or deprecations. It preserves reasoning, context, and consequences in structured wiki/adrs/ files rather than scattering notes across disparate locations.
mamu7211Analyze .NET codebase structure and dependency patterns for architectural reviews.
xloxn69Convert discussed architectural decisions into MADR-formatted ADR files.
MartinNevlahaAnalyze codebases to detect patterns and generate governance proposals.
pythoninthegrassesDocument architectural decision context, options, and rationale in standardized ADR format.
