ddoc

Generate metadata for the ddoc skill unit from SKILL.md frontmatter and repository contents.

4|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/ssdiwu/diwu-workflow --skill ddoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddoc
Source: https://github.com/ssdiwu/diwu-workflow/tree/main/skills/ddoc
Command: npx skills add https://github.com/ssdiwu/diwu-workflow --skill ddoc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

ddoc provides a structured approach to product documentation by converting codebase signals and design notes into consistent, navigable docs, reducing manual toil and drift.

Core Features & Use Cases

  • Forward-mode: generate documentation from requirements to accelerate drafting and alignment.
  • Reverse-mode: reconstruct and gap-analyze codebase to restore documentation, enabling quick onboarding.
  • Reference-driven routing: leverages references and templates to standardize outputs for new projects.

Quick Start

Run the ddoc workflow to generate a ready-to-use product document from the current repository state.

Frequently Asked Questions about ddoc

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

FAQPage Schema
How do I generate product documentation from an existing codebase?

Generate product documentation from a codebase using reverse-mode to reconstruct and gap-analyze existing code signals into structured, navigable docs, reducing manual toil and drift.

What is forward-mode documentation generation?

Forward-mode documentation generation creates product docs directly from requirements to accelerate drafting and alignment before implementation begins.

How do I perform a gap analysis on my product documentation?

Perform a documentation gap analysis using reverse-mode to reconstruct codebase signals and detect missing or outdated product docs against the current repository structure.

Can I use templates to standardize product docs across new projects?

Yes, you can standardize product docs across new projects using reference-driven routing, which leverages templates to ensure consistent and navigable documentation outputs.

Do I need any dependencies or external libraries to run the ddoc workflow?

No, you do not need external dependencies to run the documentation workflow; it operates standalone by reading repository contents and checking for optional directories like scripts, references, and assets.