dld-decide

Record development decisions with YAML frontmatter and markdown bodies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers meticulously record the reasoning behind their code changes, ensuring that critical decisions are not lost to time or team turnover.

Core Features & Use Cases

  • Decision Logging: Captures the 'what', 'why', and 'how' of development choices.
  • Contextual Linking: Connects decisions to specific code sections and existing related decisions.
  • Use Case: After refactoring a complex module, use this Skill to document the specific trade-offs made, the alternatives considered, and the rationale for the chosen approach, making future maintenance and understanding much easier.

Quick Start

Use the dld-decide skill to record a decision about optimizing database queries.

Frequently Asked Questions about dld-decide

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

FAQPage Schema
How do I record development decisions to prevent knowledge loss during team turnover?

You record development decisions by logging context, rationale, and affected code sections. This decision logging captures the 'what', 'why', and 'how' of choices to ensure critical reasoning is maintained over time.

What is the best way to document technical debt and trade-offs after refactoring a module?

Documenting technical debt and trade-offs is best handled by recording the specific alternatives considered and the rationale for the chosen approach. This ensures future maintainability and understanding of the complex module.

How do I structure code documentation to link decisions to specific code sections?

You structure code documentation using structured YAML frontmatter and a markdown body. This format facilitates contextual linking to connect specific decisions directly to affected code and related decisions.

Can I use namespaced projects to organize decision logging for multiple codebases?

Yes, you can use namespaced projects to organize decision logging for multiple codebases. The system supports namespaced projects and tag-based organization to manage decisions across different contexts.

Does decision logging work with existing markdown code documentation workflows?

Yes, decision logging integrates with existing markdown code documentation workflows. It records a single development decision with structured YAML frontmatter and a markdown body, fitting naturally into developer documentation.