speckit-sync-backfill

Backfilling missing feature specifications from existing code involves extracting behaviors from method signatures, validations, business logic, and test scenarios to infer undocumented user stories and functional requirements. This process generates a full spec scaffold and review task from the discovered implementation.

Generating user stories from an undocumented codebase requires inferring requirements from discovered command and service behaviors, mapping extracted method signatures and test scenarios into functional requirements. This creates a structured specification scaffold with a backfill notice indicating the documentation was reverse-engineered.

Yes, extracting functional requirements from test scenarios and method signatures is possible by analyzing discovered validations and business logic. The extracted behaviors are mapped into functional requirements, CLI command implications, and success criteria to build a comprehensive backfilled specification.

Creating codebase documentation for unspecced features involves reverse-engineering the implementation to produce a spec scaffold and review task. It uses discovered tests and docs to infer the original intent, ensuring alignment and onboarding for future changes are faster and less risky.

Spec backfilling works for extracting requirements from CLI commands and services by discovering their behaviors and mapping them into functional requirements and CLI command implications. It infers user stories from the implementation and test scenarios to generate a complete specification.

You should not use codebase documentation extraction when the implementation lacks clear method signatures, validations, or test scenarios to infer behaviors from. Without discoverable commands or business logic, generating accurate functional requirements and user stories becomes unreliable.