speckit-sync-backfill

To generate documentation from existing code, this Skill analyzes your implementation, tests, and docs to infer user stories, acceptance criteria, and requirements, producing a structured spec outline with traceability to the current codebase.

Yes, you can backfill user stories and acceptance criteria directly from source code and tests. The process derives scope and requirements deterministically from Commands, Services, Tests, and Docs to create a complete feature spec.

Yes, you need a .specify/ directory structure in your codebase. The backfill process relies on this specific structure to generate spec outlines and artifacts with proper end-to-end extraction and documentation scaffolding.

The best way to align undocumented implementation with formal feature requirements is running a deterministic backfill process that extracts scope and architecture plans from existing code, ensuring documentation matches current implementation.

A backfilled spec generated from existing code includes sections for backfill notice, inferred requirements, user stories, acceptance criteria, and an architecture plan, providing complete documentation scaffolding for your feature.

You should avoid automated code-to-spec backfill when your codebase lacks a .specify/ structure, or when implementation logic is too ambiguous to deterministically infer accurate user stories and requirements from existing tests and documentation.