CtrlK
BlogDocsLog inGet started
Tessl Logo

dld-kit/dld

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

Overview
Skills
Evals
Files

dld-workflow.mdrules/

DLD (Decision-Linked Development)

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/.

Rules

  • When you encounter @decision(DL-XXX) annotations in code, use /dld-lookup DL-XXX to read the referenced decision BEFORE modifying the annotated code.
  • ALWAYS look up and verify related decisions before modifying annotated code. Do not skip this step.
  • NEVER modify code in a way that contradicts an existing decision without first confirming with the user. If the change requires breaking a previous decision, a new decision must be recorded (via /dld-decide) that explicitly supersedes the old one.
  • Use /dld-decide to record new decisions
  • Use /dld-plan to break down a feature into multiple grouped decisions
  • Use /dld-implement to implement proposed decisions
  • Use /dld-lookup to query decisions by ID, tag, or code path
  • Use /dld-audit to scan for drift between decisions and code
  • Use /dld-snapshot to regenerate SNAPSHOT.md and OVERVIEW.md from the decision log
  • Use /dld-status for a quick overview of the decision log state
  • Use /dld-retrofit to generate decisions from an existing codebase

Install with Tessl CLI

npx tessl i dld-kit/dld

rules

dld-workflow.md

tile.json