specsafe-done

Mark a specification complete and archive it in the SpecSafe framework.

3|Updated Jan 27, 2026

Search Tags:#workflow #project management #qa #completion #archiving #specsafe

Ready to run

npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill specsafe-done

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specsafe-done
Source: https://github.com/Agentic-Engineering-Agency/specsafe/tree/main/.claude/skills/specsafe-done
Command: npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill specsafe-done

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of marking a specification as complete and archiving it, ensuring a clean and organized project state.

Core Features & Use Cases

Workflow Completion: Moves a spec from the QA stage to the COMPLETE stage.
Archiving: Organizes completed specs into the specs/completed/ directory.
Status Update: Automatically updates PROJECT_STATE.md with completion metrics.
Use Case: After a feature has passed all quality assurance checks and is deemed production-ready, use this Skill to formally close out its development cycle.

Quick Start

Use the specsafe-done skill to mark the spec with ID SPEC-20260211-004 as complete.

Frequently Asked Questions about specsafe-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I archive completed specifications after they pass QA?▼

To archive completed specifications, you validate the QA reports, confirm requirement satisfaction, and execute the completion command to move specs to the COMPLETE stage. This archives them into the completed directory for historical reference.

What is the workflow for moving a spec from QA to COMPLETE?▼

The workflow for moving a spec from QA to COMPLETE involves validating QA reports and confirming requirements are met. The process then executes a completion command, generates a summary, and updates project state documentation.

How do I update PROJECT_STATE.md when a feature is production-ready?▼

To update PROJECT_STATE.md when a feature is production-ready, you run the spec completion process. It automatically records completion metrics and updates the state documentation to reflect the newly archived specifications.

When should I formally close out a development cycle for a specification?▼

You should formally close out a development cycle for a specification after the feature has passed all quality assurance checks and is deemed production-ready. This ensures completed work is properly recorded and organized.

Do I need to manually organize completed specs into a directory?▼

You do not need to manually organize completed specs into a directory. The completion process automatically archives them into the specs/completed/ directory and generates a completion summary for historical reference.