Implements proposed software decisions by modifying code and adding @decision annotations.
npx skills add https://github.com/jimutt/dld-kit --skill dld-implement
Please help me install this Agent Skill. Skill: dld-implement Source: https://github.com/jimutt/dld-kit/tree/main/.claude/skills/dld-implement Command: npx skills add https://github.com/jimutt/dld-kit --skill dld-implement
This Skill automates the process of translating proposed decisions into tangible code changes, ensuring that the reasoning behind software development is directly linked to the implementation.
@decision annotations to relevant code sections./dld-plan session generates a proposed decision DL-007 to optimize a database query, running /dld-implement DL-007 will modify the query in the code, add the @decision(DL-007) annotation, and mark the decision as accepted.Use the dld-implement skill to implement the proposed decision DL-005.
High-intent search queries and answers about installing and using this skill.
To implement proposed development decisions and update code, you can use an automated approach that parses decision records, applies code changes, inserts `@decision` annotations, and transitions the decision status to accepted.
Linking documented reasoning into a codebase involves inserting `@decision` annotations into relevant code sections, ensuring the reasoning behind software development is directly connected to the implementation for enhanced maintainability.
Yes, you can transition a proposed decision record to an accepted status by running an implementation process that modifies the code according to the decision and subsequently updates the decision status.
Code annotation for decision implementation works by parsing decision records and adding `@decision` tags to relevant code sections, integrating documented reasoning into the codebase while adhering to project practices and version control.
Yes, you need a proposed decision record generated from a planning session, as the implementation process requires parsing the decision record to apply the corresponding code changes and insert the correct annotations.
Verifying annotation presence is required to ensure that the documented reasoning has been successfully integrated into the codebase, confirming that the code modifications include the necessary `@decision` tags for maintainability.
abdullah1854Generate Markdown Architectural Decision Records from structured inputs.
IliyaBrookReview and simplify recently modified code for clarity and maintainability.
rajitsahaRun quality gates, review diffs, update docs, and create structured commits.
saolalabTrack statuses, log decisions, and coordinate departments with YAML templates.