Decision-Linked Development (DLD) — a workflow for recording, linking, and maintaining development decisions alongside code. Skills for planning, recording, implementing, auditing, and documenting decisions via @decision annotations.
68
Quality
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
This project uses Decision-Linked Development. Decision records (DL-*.md) live in decisions/records/. High-level docs (INDEX.md, OVERVIEW.md, SNAPSHOT.md) live in decisions/.
@decision(DL-XXX) annotations in code, use /dld-lookup DL-XXX to read the referenced decision BEFORE modifying the annotated code./dld-decide) that explicitly supersedes the old one./dld-decide to record new decisions/dld-plan to break down a feature into multiple grouped decisions/dld-implement to implement proposed decisions/dld-lookup to query decisions by ID, tag, or code path/dld-audit to scan for drift between decisions and code/dld-snapshot to regenerate SNAPSHOT.md and OVERVIEW.md from the decision log/dld-status for a quick overview of the decision log state/dld-retrofit to generate decisions from an existing codebaseInstall with Tessl CLI
npx tessl i dld-kit/dld