lina-openspec-archive-consolidate

Aggregates fragmented archived OpenSpec change iterations into functionally grouped, compressed archives.

147|28|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/linaproai/linapro --skill lina-openspec-archive-consolidate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lina-openspec-archive-consolidate
Source: https://github.com/linaproai/linapro/tree/main/.agents/skills/lina-openspec-archive-consolidate
Command: npx skills add https://github.com/linaproai/linapro --skill lina-openspec-archive-consolidate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of fragmented, scattered archived OpenSpec change iterations that are difficult to navigate, maintain, and audit, eliminating redundant raw archive clutter while preserving all critical high-value context such as feedback loops, design evolution rationale, validation evidence, and governance impact.

Core Features & Use Cases

  • Semantic Aggregation & Classification: Groups archived OpenSpec iterations by functional responsibility, merging related iterations into coherent, complete change documents that read like originally designed specifications.
  • High-Value Summary Compression: Retains critical maintenance information (FB feedback, root causes, fix explanations, i18n, cache consistency, data permissions, DI, cross-platform and test strategy impacts) while trimming low-value repetitive task checklists and per-file move workflows.
  • Safe Automated Cleanup: Automatically removes successfully merged raw date-prefixed archive directories with strict guardrails to prevent accidental deletion of unmerged archives, non-raw grouped directories, or active OpenSpec changes.
  • Use Case: For development teams using OpenSpec for specification-driven development, this Skill turns dozens of scattered archived change iterations into organized, maintainable grouped archives without losing any context needed for future audits, design traceability, or further iteration.

Quick Start

Use the lina-openspec-archive-consolidate skill to aggregate all archived OpenSpec changes in the openspec/changes/archive/ directory into functional grouped archives, compress high-value summaries, and clean up successfully merged raw date-prefixed archive directories.

Frequently Asked Questions about lina-openspec-archive-consolidate

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

FAQPage Schema
How do I consolidate fragmented OpenSpec archives into grouped summaries?

To consolidate OpenSpec archives, this Skill aggregates scattered date-prefixed change iterations into functionally grouped archives, compressing repetitive records while preserving high-value context like design rationale and validation evidence for improved specification traceability.

What is the best way to clean up redundant raw OpenSpec change archives?

The best way to clean up raw OpenSpec archives is through automated removal of successfully merged date-prefixed directories, utilizing strict guardrails to prevent accidental deletion of unmerged archives, non-raw grouped directories, or active changes.

How does semantic merging work for archived specification-driven development changes?

Semantic merging groups archived OpenSpec iterations by functional responsibility, transforming fragmented changes into coherent documents that read like originally designed specifications while retaining critical feedback loops and governance impact data.

Does OpenSpec archive consolidation preserve maintenance context like feedback loops and design evolution?

Yes, OpenSpec archive consolidation preserves high-value maintenance context including feedback loops, root causes, fix explanations, i18n impacts, cache consistency, data permissions, and cross-platform test strategies while compressing low-value repetitive task checklists.

Can I normalize plugin-specific content when aggregating archived OpenSpec changes?

Yes, you can normalize plugin-specific content during OpenSpec archive aggregation by applying mandatory plugin-id prefix normalization to ensure consistent grouping and traceability across fragmented archived change iterations.

What are the limitations or risks when deleting raw date-prefixed OpenSpec archive directories?

The risk of deleting raw OpenSpec archives is mitigated by strict guardrails that prevent accidental deletion of unmerged archives, non-raw grouped directories, or active OpenSpec changes, ensuring only successfully merged raw archives are safely removed.