feature-doc

To keep technical documentation in sync with your codebase, this Skill detects recently modified code and incrementally updates only the impacted documentation sections, adding a timestamped update note. It generates overview, architecture, API, data model, and workflow docs directly from the current code.

A documentation coherence audit verifies that documented references still exist and that signatures, interfaces, and workflows still match the current code. It produces a structured audit report highlighting what is synchronized, what is desynchronized, and what is missing.

Yes, you can generate full domain documentation for a backend service. This Skill creates a consistent documentation set covering overviews, architecture, APIs, data models, workflows, and UI components when applicable, driven by YAML frontmatter identification and code scanning.

To audit existing API documentation for missing endpoints, run this Skill in Audit mode for your target domain. It scans code by domain and patterns, traces workflows, and generates a structured report verifying that all documented references and signatures match the current implementation.

Yes, this documentation tool requires YAML frontmatter-driven identification to locate and scope files within your codebase. It uses adaptive context loading via manifests and stack patterns to ensure deterministic doc file synthesis and accurate code scanning.

The best way to update affected workflow docs after changing an API controller is using incremental updates. This Skill detects the recently modified code, refreshes only the impacted endpoint and workflow documentation sections, and verifies no new services went undocumented through a coherence audit.