speckit-docguard-generate

Generate canonical documentation from codebases using docguard-cli.

Updated May 18, 2026
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-docguard-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-docguard-generate
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-docguard-generate
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-docguard-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an existing codebase into standardized, authoritative documentation so teams can quickly understand architecture, data structures, tests, security posture, environment setup, and APIs without manual reverse engineering.

Core Features & Use Cases

  • Canonical documentation generation: Produces structured docs such as architecture, data model, test specifications, security, environment, and API reference.
  • Codebase-aware extraction: Reads routes, schemas, configs, dependencies, test files, and OpenAPI sources to document what actually exists.
  • Use Case: A developer or technical writer needs a reliable baseline for project docs after inheriting a repository and wants consistent, standards-aligned Markdown output.

Quick Start

Ask the skill to generate the canonical documentation for the current project or a specific document from the codebase.

Frequently Asked Questions about speckit-docguard-generate

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

FAQPage Schema
How do I generate API reference and architecture documentation from an existing codebase?

Canonical documentation is structured, authoritative technical documentation that standardizes architecture, data models, security posture, and API references. It eliminates manual reverse engineering by extracting actual codebase structures into consistent Markdown output.

Can I automatically extract security posture and data model details for project audits?

Yes, you can automatically extract security posture and data model details for project audits by scanning repository configurations, schemas, and test files. This generates structured documentation aligned with technical audit standards.

What is the best way to document an inherited repository for developer onboarding?

The best way to document an inherited repository for developer onboarding is to generate canonical docs directly from the codebase. Scanning source files and configs produces reliable, standards-aligned technical documentation for new team members.

Do I need a specific project structure to extract technical documentation from source files?

Yes, extracting technical documentation from source files requires a specific project structure. You need a spec-kit project structure and a docguard-cli tool to scan source files and configurations for accurate architecture and environment details.

How does codebase-aware extraction handle OpenAPI sources and test files?

Codebase-aware extraction reads OpenAPI sources and test files by scanning them directly from the repository. It documents what actually exists in the codebase, translating routes and schemas into structured API references and test specifications.

What are the limitations of generating canonical documentation from an existing codebase?

Generating canonical documentation from an existing codebase is limited by its dependency on the spec-kit project structure and docguard-cli. It requires existing source files and configs to extract data, preventing documentation generation for incomplete repositories.