analyze

To identify documentation gaps in feature specs and design docs, scan current-state knowledge bases to surface missing domains, incomplete sub-capabilities, and broken references, then generate a structured gap report. This validates alignment with project vision and decision indexes.

Change impact analysis for architecture decision records evaluates completeness against domain READMEs, specs, and designs to ensure changes are documented and decisions are supported. It produces a prioritized gaps list with references and actionable next steps.

To audit a project knowledge base for missing feature specifications, read current-state documentation including vision, ADRs, and designs. Evaluate completeness against domain READMEs to surface missing domains and generate a prioritized gaps list with traceability.

Yes, you can use gap analysis to validate alignment with project vision and decision indexes. By reading current-state documents and evaluating completeness, it ensures changes are documented and decisions are supported, generating a structured gap report for improvement decisions.

The best way to generate a prioritized gaps list with traceability for design docs is to scan all project documentation to surface incomplete sub-capabilities and broken references. This produces a structured gap report with actionable next steps and references.

You need to run a gap analysis on software engineering documentation when assessing change impact across a project's knowledge base. It applies to auditing feature specs, design docs, ADRs, and vision documents to surface missing domains and guide improvement decisions.