11-DOCS-discover

A documentation discovery process scopes your current branch against main to identify affected features, functions, and tables. It produces a docs-outline.md blueprint detailing all required updates, preventing gaps across developer docs and client-facing guides.

A documentation blueprint is a structured outline file that maps all required documentation targets for code changes. It categorizes updates for developer docs, client guides, and inline comments by auditing modified functions and cross-feature flows.

Scoping documentation to modified code involves comparing the current branch against main. This isolates changed feature areas and functions, ensuring documentation efforts target only updated code rather than the entire repository.

Auditing cross-feature documentation requirements requires a progressive three-pass discovery approach. It builds a skeleton outline, expands it with specific function targets, and performs a final cross-feature audit to map interconnected flows comprehensively.

Yes, a documentation outline can target inline code comments, client-facing guides, and developer docs simultaneously. The discovery process identifies specific documentation categories required across all affected code changes on your branch.

You need a documentation discovery process after implementing new features or modifying code on a branch. It prevents documentation gaps by generating a comprehensive blueprint of required updates before any writing begins.