dld-lookup

Look up design decision records by ID, tag, code path, or keyword.

4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/jimutt/dld-kit --skill dld-lookup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dld-lookup
Source: https://github.com/jimutt/dld-kit/tree/main/.claude/skills/dld-lookup
Command: npx skills add https://github.com/jimutt/dld-kit --skill dld-lookup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps AI agents and developers understand the reasoning behind code by looking up documented decisions, preventing unintended changes and ensuring adherence to design principles.

Core Features & Use Cases

  • Decision Lookup: Find decisions by ID, tag, code path, or keywords.
  • Proactive Consultation: Automatically consults decision records when encountering @decision annotations in code.
  • Conflict Resolution: Identifies and flags potential conflicts between proposed code changes and existing decisions.
  • Use Case: Before modifying a function related to payment processing, an AI agent uses /dld-lookup to find the decision record for that feature, ensuring any changes align with the established retry strategy.

Quick Start

Look up the decision with ID DL-047.

Frequently Asked Questions about dld-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I look up documented design decisions linked to specific code paths?

To look up documented design decisions, query decision records by ID, tags, code paths, or keywords. This retrieves the specific decision history linked to your target code, ensuring modifications align with the original design intent.

How does an AI agent automatically check decision compatibility before modifying code?

AI agents automatically check decision compatibility by detecting `@decision` annotations in the code and proactively consulting the linked decision records. This identifies and flags potential conflicts before applying any code changes, preventing regressions.

What is a decision log annotation and when do I need it for code understanding?

A decision log annotation is a code marker that links to a documented design decision record. You need it when modifying complex features to ensure AI agents and developers assess design compatibility and understand the reasoning behind existing code.

Can I find a decision record using just a feature keyword like payment processing?

Yes, you can find decision records using feature keywords like payment processing. The lookup mechanism searches by keywords to retrieve the relevant decision record, helping agents verify established strategies before altering the feature.

What's the best way to prevent regressions when an AI agent modifies existing code?

The best way to prevent regressions is to use proactive decision consultation to assess compatibility before altering code. By retrieving decision records via annotations, agents identify potential conflicts and maintain design integrity during modifications.