🎯

openspec-archiving

🎯Skill

from forztf/open-skilled-sdd

VibeIndex|
What it does

openspec-archiving skill from forztf/open-skilled-sdd

openspec-archiving

Installation

Install skill:
npx skills add https://github.com/forztf/open-skilled-sdd --skill openspec-archiving
7
-
Last UpdatedNov 28, 2025

Skill Details

SKILL.md

Overview

# Open Spec-Driven Development Skills (open-skilled-sdd)

[中文文档](./readme-zh.md)

Enhancing AI coding assistants through open Spec-driven development (Spec-driven development for AI coding assistants), adopting the Claude Code Skills approach, compatible with various CLI and IDE AI coding assistants that support AGENTS.md.

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

Why?

When the code or documentation generated by an AI coding assistant is disappointing, it's unclear whether it's because:

  1. The large model's capabilities are problematic.
  2. The AI coding assistant is problematic: providing inappropriate context (including system prompts).
  3. The prompts I wrote are problematic.

The focus is on breaking through "2. The AI coding assistant is problematic", but because the built-in spec-driven development methods (context engineering, system prompts, etc.) of various CLI and IDE AI coding assistants are not public, they are basically black boxes, making it impossible to analyze or optimize them yourself. I looked for various open spec-driven development solutions, such as the 6A workflow, PRPs, Spec Kit, OpenSpec, spec-workflow-mcp, BMad-Method, etc., to see which one is the most suitable, and then proceed to optimize it myself. I roughly used these solutions and found that they each have their pros and cons. My first thought was to create a comprehensive solution, integrating the advantages of each solution and removing the parts I thought were unsuitable. I soon discovered that this path was a dead end; this idea is exactly the channel that various AI coding assistants are currently working on. I cannot do better than these vendors. Moreover, from a philosophical point of view, a comprehensive solution (limited capabilities) cannot adapt to all types of scenarios (infinite scenarios). At this time, Claude Code Skills came out. I found this approach good; wouldn't infinite skills be able to adapt to infinite scenarios? At the same time, I found [skilled-spec](https://github.com/mahidalhan/skilled-spec).

My idea is to convert OpenSpec, PRPs, Spec Kit, spec-workflow-mcp, BMad-Method, 6A workflow, etc., including good spec-driven development methods that appear in the future, into individual composable Skills, which are open and can be optimized by yourself.

Skills

| Methodology | Skill | Trigger Words | Purpose |

| :----------------- | :-------------------------------- | :----------------------------------------------------------------------- | :--------------------------------------------------- |

| openspec | openspec-proposal-creation | "openspec proposal", "openspec plan" | Generate structured proposals with EARS requirements |

| | openspec-implementation | "openspec implement", "openspec build" | Execute tasks with testing and progress tracking |

| | openspec-archiving | "openspec archive" | Merge spec differences and create archives |

| | openspec-context-loading | "openspec context", "openspec what specs exist", "openspec show changes" | Discover specs, search requirements, show dashboard |

| openspec (Chinese) | openspec-proposal-creation-cn | "openspec提案", "openspec需求" | Generate structured proposals with EARS requirements |

| | openspec-implementation-cn | "openspec开发" | Execute tasks with testing and progress tracking |

| | openspec-archiving-cn | "openspec归档"