cells-archive

Merge delta specifications into main specs and archive completed BBVA Cells changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cells-archive
Source: https://github.com/PixelDroid19/cells-agents/tree/main/skills/cells-archive
Command: npx skills add https://github.com/PixelDroid19/cells-agents --skill cells-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of properly closing out development changes in BBVA Cells projects, ensuring that delta specifications are merged into main specs without data loss or ambiguity, while archiving artifacts for full traceability and audit trails.

Core Features & Use Cases

  • Spec Merging: Carefully sync added, modified, or removed requirements from delta specs to main specs, preserving untouched content and handling edge cases like ambiguities.
  • Multi-Mode Archiving: Supports engram, openspec, hybrid, or no persistence modes to move change folders to dated archives and generate lineage reports with observation IDs.
  • Use Case: After verifying a new UI component in a Cells project, use this Skill to merge its spec updates and archive the entire change folder, maintaining compliance and readiness for the next iteration.

Quick Start

Archive the completed change named 'bbva-button-update' and sync its specs to the main source of truth.

Frequently Asked Questions about cells-archive

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

FAQPage Schema
How do I merge delta specifications into main specs without losing existing content?

To merge delta specifications without data loss, carefully sync added, modified, or removed requirements into main specs while preserving untouched content and handling ambiguities to maintain full traceability.

What is the best way to archive completed development changes in BBVA Cells projects?

The best way to archive completed changes in BBVA Cells projects is to relocate change folders to dated archives, generate lineage reports with observation IDs, and sync delta specs into main specs for audit compliance.

Does this archiving workflow support different persistence modes like engram and openspec?

Yes, this archiving workflow supports engram, openspec, hybrid, and no persistence modes, allowing you to move change folders to dated archives and generate lineage reports based on your specific project requirements.

How do I archive a verified UI component change folder while maintaining audit readiness?

To archive a verified UI component change folder while maintaining audit readiness, merge its spec updates into the main source of truth and relocate the entire folder to a dated archive with observation IDs.

Why should I avoid destructive operations when syncing requirements from delta specs?

You should avoid destructive operations when syncing requirements from delta specs to prevent data loss and ambiguity, ensuring untouched content is preserved and merged content maintains accurate requirement matching for traceability.