ddd-doc-steward

Map code evidence to structured markdown documentation files.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/yongc2025/NovelFactory --skill ddd-doc-steward-yongc2025
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-doc-steward
Source: https://github.com/yongc2025/NovelFactory/tree/main/.skills/ddd-doc-steward
Command: npx skills add https://github.com/yongc2025/NovelFactory --skill ddd-doc-steward-yongc2025

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of documentation rot by ensuring that your project's documentation (docs/) remains perfectly synchronized with the actual codebase, configurations, and operational reality.

Core Features & Use Cases

  • Evidence-Based Documentation: Automatically generates or updates documentation based on real file paths, git diffs, and system configurations.
  • SSOT Maintenance: Enforces a strict Single Source of Truth (SSOT) workflow, ensuring every fact in your docs is backed by a verifiable source.
  • Use Case: When you add a new API feature, use this Skill to scan your changes, identify the impact on existing guides, and generate a patch that updates your PRD and integration specs without manual drafting.

Quick Start

Use the ddd-doc-steward skill to scan the current repository and generate a documentation update plan based on the latest git changes.

Frequently Asked Questions about ddd-doc-steward

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

FAQPage Schema
How do I automate documentation updates based on git changes?

Automating documentation updates based on git changes involves scanning the repository, mapping code evidence to structured markdown files, and generating incremental update patches across architecture, features, integrations, and guides.

What is a Single Source of Truth workflow for technical writing?

A Single Source of Truth workflow for technical writing enforces strict documentation accuracy by linking every claim in your markdown files to verifiable sources like specific file paths, configuration settings, or execution commands.

How do I prevent documentation rot in a rapidly changing codebase?

Preventing documentation rot means maintaining project documentation by automatically mapping real file paths, git diffs, and system configurations to structured markdown, keeping docs perfectly synchronized with the codebase.

Can I generate integration specs and PRDs directly from code evidence?

Generating integration specs and PRDs directly from code evidence is possible by scanning repository changes, identifying impacts on existing guides, and generating markdown patches without manual drafting.

Does evidence-based documentation work for updating existing architecture guides?

Evidence-based documentation works for updating existing architecture guides by scanning the current repository state and mapping verifiable file paths and configurations to the relevant sections of your structured markdown files.