ss-archive

Generate an architectural knowledge artifact from design.md, plan.md, and tasks.md files.

2|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/CoyoteLeo/superspec --skill ss-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-archive
Source: https://github.com/CoyoteLeo/superspec/tree/main/skills/ss-archive
Command: npx skills add https://github.com/CoyoteLeo/superspec --skill ss-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distills and preserves architectural knowledge from completed changes by generating a reusable artifact that explains why decisions were made and how the change works.

Core Features & Use Cases

  • Generate an architectural knowledge artifact from the change artifacts (design.md, plan.md, tasks.md).
  • Archive and preserve rationale, decisions, and lessons learned for future maintenance.
  • Trigger project documentation updates to reflect the architectural context of completed work.

Quick Start

Provide a completed change directory path or let the skill automatically locate an active change, then run the ss-archive command to generate the knowledge artifact.

Frequently Asked Questions about ss-archive

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

FAQPage Schema
How do I archive completed architectural changes into a knowledge document?

To archive completed changes, the skill reads design.md, plan.md, and tasks.md from a change directory and synthesizes them into a concise architectural knowledge document saved as changes/archive/YYYY-MM-DD-<topic>.md.

What is the best way to preserve architectural decisions and rationale for future maintenance?

Preserving architectural decisions is done by generating a knowledge artifact from existing change documents, capturing why decisions were made and how the change works for future reference.

Can I automatically update project documentation after completing a code change?

Yes, you can trigger project documentation updates to reflect the architectural context of completed work immediately after generating the archive knowledge artifact.

Do I need to manually specify file paths to archive change management documents?

No, you can provide a completed change directory path manually, or let the skill automatically locate an active change directory to synthesize the knowledge document.

What file formats are required to generate an architectural knowledge artifact?

Generating the knowledge artifact requires reading three markdown files: design.md, plan.md, and tasks.md, which must exist within the targeted change directory.