skills.rest
lleontor705
lleontor705COMMUNITY
Explore all skills by this author →
WebsiteGitHub

finalize

Merge delta specs into main specs and archive completed changes.

1|Updated Mar 30, 2026
Search Tags:#retrospective#archive#sdd#openspec#contract#delta-specs#finalize
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill finalize-lleontor705
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/finalize
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill finalize-lleontor705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically closes the SDD cycle by merging delta specs into main specs, archiving the completed change, and generating a retrospective.

Core Features & Use Cases

  • Delta-merge: merge ADDED, MODIFIED, and REMOVED delta sections into the main specs while preserving structure.
  • Archiving: move the change folder into an ISO-date-prefixed archive directory and maintain a complete artifact lineage.
  • Retrospectives & Reports: generate a learning retrospective and an archive report that captures all observations for auditability.

Quick Start

Place your delta specs in openspec/changes/{change-name}/ and run the archiving workflow to finalize and archive the change.

Frequently Asked Questions about finalize

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

FAQPage Schema
How do I close an OpenSpec SDD cycle after verification passes?▼

To close an SDD cycle after a pass verification, this Skill merges delta specs into main specs, archives the change folder, and generates a retrospective. It preserves full artifact lineage for audits.

How does delta spec merging work when finalizing an OpenSpec change?▼

Delta spec merging integrates ADDED, MODIFIED, and REMOVED delta sections into the main specs during finalization. This preserves the main spec structure while applying the completed change.

What is the best way to archive OpenSpec changes with full artifact lineage?▼

The best way to archive OpenSpec changes is using an immutable archive directory prefixed with an ISO date. This approach maintains complete artifact lineage and produces an archive report detailing observations.

Can I generate a retrospective automatically after merging delta specs?▼

Yes, you can automatically generate a learning retrospective after merging delta specs. The Skill produces the retrospective alongside an archive report to close the SDD cycle and capture all observations.

Does the OpenSpec finalization process support Hybrid mode?▼

Yes, the finalization process supports both OpenSpec and Hybrid modes. It operates after the orchestrator dispatches a pass or pass_with_warnings verification to finalize and archive the change.

When do I need to archive delta specs in an SDD workflow?▼

You need to archive delta specs when a change has passed verification and the SDD cycle must close. Archiving moves the change folder into an ISO-date-prefixed directory to ensure auditability.

Related Skills

Explore More Software Engineering Skills→
cynkracynkra
1

openspec-archive-change

Archive completed OpenSpec changes with safety checks and optional spec synchronization.

Official
Intermediate
RamonsDkaRamonsDka
1

sdd-onboard

Guide users through a full Spec-Driven Development cycle on their codebase.

Community
Advanced
nobu007nobu007

spec-flow-auto

Automate PRD-to-SPEC workflows generating requirements.md, design.md, and tasks.md.

Community
Advanced
jacobcyjacobcy
6

openspec-sync-specs

Merge delta spec changes into main specs while preserving unrelated content.

Community
Advanced