analyze-codebase

Automating codebase discovery involves running a structured script to analyze existing specs and code, generating stage discovery documents that map dependencies and identify reusable components. This validates spec-code alignment and ensures governance for the workflow stage.

Validating spec-code alignment requires analyzing the codebase against existing specifications to map dependencies and side effects. This process identifies reusable components to reduce duplication and generates a structured discovery document for stage readiness.

Mapping dependencies and side effects is done by executing a codebase analysis script that evaluates existing specifications and code. The output is a discovery document detailing these relationships and highlighting reusable components across the project.

A Stage B discovery document is needed when applying a docs-first workflow to your project. It enforces a structured process to validate stage readiness, map dependencies, and identify reusable components before proceeding further in the workflow.

No, this specific codebase analysis enforces the structured process of the VibeFlow docs-first workflow. It relies on existing specs and code within that framework to generate the required discovery documents and validate spec-code alignment.

Identifying reusable components is achieved by running a codebase discovery script that analyzes existing specs and code. This process maps dependencies, validates alignment, and outputs a document highlighting components available for reuse across the project.