Analyze existing codebases to generate DLD decision records and annotations.
npx skills add https://github.com/jimutt/dld-kit --skill dld-retrofit
Please help me install this Agent Skill. Skill: dld-retrofit Source: https://github.com/jimutt/dld-kit/tree/main/.claude/skills/dld-retrofit Command: npx skills add https://github.com/jimutt/dld-kit --skill dld-retrofit
This Skill helps you integrate Decision-Linked Development (DLD) into an existing codebase by automatically inferring and documenting the rationale behind the code's current structure and behavior.
@decision annotations to relevant code sections for traceability./dld-retrofit will analyze the code, generate initial decision records explaining why certain architectural choices were made, and add annotations, providing a starting point for understanding and maintaining the system.Use the dld-retrofit skill to analyze the current codebase and generate initial decision records.
High-intent search queries and answers about installing and using this skill.
To document design decisions in a legacy codebase, you can automatically infer architectural rationale by analyzing existing code structure and generating decision records with traceable code annotations.
Decision-Linked Development for existing code involves analyzing project structure to identify core domain models and implementation choices, then generating structured decision records and code annotations for traceability.
You can generate decision records automatically by analyzing project files via a configuration file, which infers foundational system aspects and implementation details to create structured Markdown files with YAML frontmatter.
Yes, you can add traceability annotations to code by analyzing the codebase to infer architectural rationale and automatically inserting decision annotations into relevant code sections.
Yes, analyzing project structure for refactoring requires a configuration file to define the scope, allowing the tool to parse existing code files and infer the rationale behind implementation-level choices.
Inferring rationale from legacy code relies on analyzing existing structural patterns and implementation choices, meaning the generated decision records serve as a starting point rather than a definitive historical account of architectural decisions.
AesopScottEstablish the MAPS lifecycle structure by agreeing on phase names, order, and scope.
OmexITCreate and maintain Architecture Decision Records using the adr.md template.
Sir-chawakornAnalyze codebases to map file relationships, architectural patterns, and data flows.
cin12211Refactor legacy code incrementally with tests and version control.