jimutt/dld
Decision-Linked Development: record, link, and audit development decisions alongside code
Adjust or update existing decision records. Edits drafts freely, protects the prose of decisions already on the base branch per the project setting, and correctly interprets adjustment requests.
Scan for drift between decisions and code. Finds orphaned annotations, stale references, and undocumented changes.
Autonomous audit — detects drift, fixes issues, and opens a PR. Designed for scheduled/CI execution without human interaction.
The dld CLI shared by the DLD skills. Not intended for direct invocation — the other DLD skills run it.
Record a single development decision as a markdown file with YAML frontmatter. Collects context, rationale, and code references interactively.
Implement one or more proposed decisions. Makes code changes, adds @decision annotations, and updates decision status.
Bootstrap DLD (Decision-Linked Development) in a repository. Creates dld.config.yaml, the decisions/ directory, and INDEX.md. Run once per project.
Look up decisions by ID, tag, code path, or keyword. IMPORTANT — use this proactively whenever you encounter @decision annotations in code you are about to read or modify.
Break down a feature into multiple decisions interactively. Creates a set of decision records grouped by a shared tag.
Resolve decision ID collisions between a local branch and the base branch (and open PRs). Renames colliding local decisions with git mv, rewrites cross-references and annotations, and commits the renames on top of the branch. Squashes the branch only when the user asks.
Bootstrap DLD decisions from an existing codebase. Analyzes code to infer rationale, generates decision records, and adds @decision annotations.
Generate SNAPSHOT.md (detailed decision reference) and OVERVIEW.md (narrative synthesis with diagrams) from the decision log.
Quick overview of the decision log state — counts by status, recent decisions, and run tracking info.