archive-specs

To convert planning specs into project documentation, the workflow inventories spec.md, tasks.md, and checklist.md files, reconciles their claims with the current codebase, and generates standardized docs like README.md and categorized guides.

Project documentation disagrees with the codebase when planning artifacts are not reconciled against current code. This Skill applies evidence-first principles, reading SKILL.md frontmatter and aligning spec content with codebase evidence to ensure docs reflect the true state.

The best way to archive superseded spec files is to run a reconciliation workflow that converts them into durable documentation first, then safely archives the consumed source specs to keep the active repository clean and trustworthy.

The workflow generates a standardized documentation structure from planning artifacts, producing a README.md plus categorized outputs under docs/ including getting-started, configuration, architecture, features, and developer-guide sections.

Yes, you can clean up scattered planning files by standardizing spec.md, tasks.md, and checklist.md artifacts into centralized project documentation, then archiving the consumed planning sources to maintain a lean active repository.

You should not use automated spec archiving when planning artifacts are still actively being drafted and unconverted, as the workflow archives superseded spec sources only after a successful reconciliation and conversion into durable docs.