speckit-cleanup

To fix disorganized spec-kit documentation, you validate and reorganize the specs/ directory to ensure sequential numbering and proper workflow structure. This process detects gaps, duplicates, and missing files, then optionally applies doc-level reorganizations.

Yes, you can validate specs directory structure without modifying files using a dry-run validation safety guard. This checks for numbering issues, structural problems, and missing files, producing a structured JSON report detailing issues without touching source code or applying changes.

The best way to ensure sequential numbering in spec-kit workflows is to run an automated validation and cleanup process on the specs/ directory. It identifies gaps and duplicates in the documentation structure and optionally applies changes to maintain correct workflow placement.

No, the spec-kit cleanup process never touches source code. It operates strictly on documentation within the specs/ directory, reporting issues with numbers, structure, and missing files, and only optionally applies changes to the documentation files themselves.

You detect gaps and duplicates in specs documentation by running a validation workflow from the repository root. This scans the specs/ directory to identify missing required files and numbering discrepancies, generating a structured JSON report that details all issues and suggested actions.