project-complete

Automating project completion involves validating prerequisites like passed code reviews and security scans, then executing OpenSpec proposal archival, changelog generation, and git push sequentially to ensure consistent end-of-project workflows.

Prerequisites for archiving OpenSpec proposals include completing code reviews, passing security scans, and ensuring all proposals have an accepted status before the workflow automation can execute the archival process.

AI-signed commits are not allowed during the project completion push; the workflow enforces standard git workflows and safety rules that prohibit AI-signed commits while executing archival and changelog operations.

Changelog generation workflows maintain auditability by updating memory and records with complete operation traces during archival and git push, allowing for straightforward project governance and rollback.

No manual intervention is required after triggering; the workflow automatically validates completion prerequisites, archives accepted OpenSpec proposals, generates the changelog, and pushes the updates via standard git workflows.

You should not use automated project completion workflows if your proposals are not fully accepted, security scans have failed, or code reviews are incomplete, as the validation step will block the archival and push process.