dd

Aligns code with design documents to maintain a single source of truth.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/zkywalker/doc-driven --skill dd-zkywalker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dd
Source: https://github.com/zkywalker/doc-driven/tree/main/dd
Command: npx skills add https://github.com/zkywalker/doc-driven --skill dd-zkywalker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and code drift are common in software projects. This approach makes design documents the single source of truth and guides engineers from planning through implementation, reducing misalignment and rework.

Core Features & Use Cases

  • Init and organize: Create a VitePress-like docs structure and ADR templates to support doc-driven development.
  • Design-first workflow: Write design documents before coding and use them as the authoritative spec for implementation.
  • Review and guardrails: Use reviews to verify code-doc consistency and detect doc rot, ensuring traceability.
  • Templates and standards: Provide templates for ADRs and frontmatter to standardize documentation.

Quick Start

Start with /dd help to detect project state and get the next recommended step.

Frequently Asked Questions about dd

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

FAQPage Schema
What is document-driven development and how does it prevent code drift?

Document-driven development makes design documents the single source of truth for implementation. By writing specs first and reviewing code against them, you minimize doc rot and prevent design-code misalignment.

How do I set up a design doc structure for a new software project?

Initialize a VitePress-like docs structure with ADR templates and strict frontmatter. Running /dd help detects your project state and recommends the next step to scaffold the design-first workflow.

How do you implement features from design documents while maintaining traceability?

Write the design document first, then use it as the authoritative spec for implementation. Quality checks and design reviews enforce traceability, verifying code-doc consistency to ensure upgrade safety.

When should I use ADR templates and design reviews in my workflow?

Use ADR templates and design reviews when progressively structuring docs from initial requirements through implementation. They standardize documentation and detect doc rot to enforce consistency.

Does this design-first workflow require specific dependencies or platforms?

No dependencies are required. The workflow applies to any software project needing strict frontmatter, design templates, and ADRs to create a single source of truth and minimize doc drift.