spec-end

Consolidate phase documents, capture lessons, and archive completed Specs.

140|20|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/HHU3637kr/skills --skill spec-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-end
Source: https://github.com/HHU3637kr/skills/tree/main/spec-end
Command: npx skills add https://github.com/HHU3637kr/skills --skill spec-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a Spec cycle completes, teams often struggle to consolidate learnings, archive artifacts, and formalize closure. This Skill guides and automates the finalization phase, ensuring lessons are captured, documents preserved, and the project moves cleanly into archived state.

Core Features & Use Cases

  • Collect and consolidate phase documents (plan.md, exploration-report.md, summary.md, test-plan.md, test-report.md, debug-*.md) from the current Spec directory.
  • Prompt active roles for retrospective input, extract lessons, and generate a formal conclusion package.
  • Archive the completed Spec by moving the directory to 06-已归档 and trigger the standard git submission workflow, with TeamLead notified upon completion.

Quick Start

Trigger the Spec end workflow to collect final documents, elicit team feedback, and archive the completed spec upon approval.

Frequently Asked Questions about spec-end

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

FAQPage Schema
How do I archive a completed spec and trigger the git workflow?

The spec-end workflow closes a spec lifecycle by collecting phase documents like plan.md and test-report.md, prompting team members for retrospective input, and generating a formal conclusion package for project archival.

What documents are collected during the spec finalization phase?

During spec finalization, the workflow collects and consolidates phase documents including plan.md, exploration-report.md, summary.md, test-plan.md, test-report.md, and debug-*.md files from the current spec directory.

When should I initiate the spec closure process for my team?

Initiate the spec closure process during the final phase after planning, implementation, and testing are complete, ensuring lessons are captured and the project moves cleanly into the archived state.

Can I use this workflow to collect retrospective feedback from active team roles?

Yes, the workflow prompts active team roles for retrospective input to extract lessons learned, which are then consolidated into a formal conclusion package before moving the spec into the archived folder.

Does spec-end require specific dependencies to manage documentation archival?

No, spec-end operates without specific dependencies to manage documentation archival, autonomously moving completed spec directories to the archived folder and triggering git submissions for team notification.