reconcile-spec-to-project

To audit code against specifications, you need a reconciliation process that inventories your specs and codebase, cross-references them, and identifies missing features or undocumented implementations. This Skill automates that deep-dive comparison using OpenSpec directories and the beads CLI.

The best way to generate issues for unimplemented requirements is to run a systematic gap analysis between your specifications and actual code. This Skill automatically cross-references OpenSpec documents and creates beads issues for any documented features lacking implementation.

Creating documentation for undocumented features requires identifying implemented code that lacks corresponding specs. This Skill analyzes your codebase against OpenSpec specifications and automatically generates new spec documents for any features that are built but not yet documented.

You need to perform a specification and codebase reconciliation after a development sprint or before a major release. This ensures all documented features are fully implemented and all implemented features are properly documented, preventing discrepancies between your project specs and actual code.

Yes, you can use OpenSpec specifications with the beads CLI to track missing features. This Skill leverages subagents and the beads CLI to execute remediation steps, bridging the gap between your openspec/specs/ directory and your actual codebase implementation.

Automated gap analysis limitations depend on the thoroughness of your initial inventory and spec structure. While this Skill systematically cross-references OpenSpec documents and code, complex or highly abstracted feature implementations may require manual review to ensure accurate reconciliation.