sdd-close

Automates verification, archiving, and review-gating of completed SDD changes in a repository.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/Akiyama-sama/SDD-WorkSpace --skill sdd-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-close
Source: https://github.com/Akiyama-sama/SDD-WorkSpace/tree/main/.agents/skills/sdd-close
Command: npx skills add https://github.com/Akiyama-sama/SDD-WorkSpace --skill sdd-close

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of verifying, archiving, and review-gating completed SDD changes, ensuring a structured and organized workflow.

Core Features & Use Cases

  • Verification: Automated checks for consistency and completeness of SDD changes.
  • Archiving: Securely storing completed changes for future reference.
  • Review-Gating: Facilitating a review process for quality assurance.
  • Use Case: When a user has completed an SDD change and wants to ensure it meets all requirements before moving on to the next stage.

Quick Start

To initiate the close process for an SDD change, use the command: /sdd close <change_id>

Frequently Asked Questions about sdd-close

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

FAQPage Schema
How do I verify and archive completed SDD changes in a repository?

To verify and archive completed SDD changes, you can automate the process using a structured workflow command that checks consistency, securely stores the changes, and enforces a review gate for quality assurance.

What is the best way to enforce a review gate for completed repository changes?

The best way to enforce a review gate for repository changes is to use an automated change management workflow that validates compliance with SDD standards before archiving and closing the change request.

How do I initiate the close process for an SDD change?

To initiate the close process for an SDD change, execute the close command with your specific change identifier to trigger automated verification, archiving, and review-gating.

Does this SDD change verification process require specific repository access?

Yes, the SDD change verification process requires direct access to the repository's SDD change files and commands to accurately validate consistency and archive the completed modifications.

When do I need to use an automated SDD change management workflow?

You need an automated SDD change management workflow when you have completed a repository modification and want to ensure it meets all SDD compliance requirements before moving on to the next project stage.

What does the SDD change verification process check for before archiving?

The SDD change verification process checks for consistency and completeness of the modifications, ensuring the repository changes meet all structured standards before securely archiving them for future reference.