generic-spec-capture

Capture existing project information by consolidating code, documentation, and conversations into structured specification documents. It separates product definition, functional behavior, and technical approach into versioned `projectspecs/` directories to prevent detail loss.

Create a single source of truth by synthesizing design notes and Slack conversations into a formal `spec.md` file. The skill identifies product definition, functional behavior, and open questions, saving them into standardized versioned directories under `projectspecs/`.

Yes, you can generate structured documentation from inline descriptions and codebase files. The skill synthesizes diverse source materials into a coherent spec, strictly adhering to the provided source without inventing missing details.

Yes, the specification synthesis process explicitly flags ambiguities found in the source material. It requires strict adherence to existing information without invention, separating identified constraints and open questions to ensure no details are lost.

The best way to consolidate scattered project details is using a synthesis skill that extracts product definition, functional behavior, and technical approach. It organizes this information into versioned `projectspecs/` directories, creating a standardized specification document.