devbooks-archiver

Coordinate end-to-end archival with backwrite, spec merging, and sync checks.

84|6|Updated Jan 12, 2026

Search Tags:#automation #workflow #archiving #spec-merging #truth-root #change-pack

Ready to run

npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-archiver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devbooks-archiver
Source: https://github.com/Darkbluelr/dev-playbooks-cn/tree/main/skills/devbooks-archiver
Command: npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-archiver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Archival closure is complex and error-prone; this skill provides an end-to-end automation to ensure a complete archival loop including automatic backwrite, specs/architecture merge, document synchronization, and moving archived change packages, preventing incomplete archiving.

Core Features & Use Cases

Automatic backwrite of unbackwritten deviations to design/docs
Merge specs into truth-root and Architecture Impact into c4.md
Document synchronization checks and archive relocation
Optional controls for scope, reports, and templates

Quick Start

Trigger the Archiver on a ready change package to perform the automated archival closure.

Frequently Asked Questions about devbooks-archiver

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

FAQPage Schema

How do I automate the archival closure for ready change packages?▼

Automating archival closure involves applying automatic backwrite, merging specs into the truth-root, and running document synchronization checks to finalize change packages. This ensures a complete archival loop with auditable closure.

What is spec-merging in the context of archiving architecture changes?▼

Spec-merging during archival integrates updated specifications into the truth-root and maps architecture impact into c4.md. This synchronizes truth artifacts to prevent inconsistent documentation after a change package is archived.

How do I backwrite unbackwritten deviations to design docs automatically?▼

Automatic backwrite identifies unbackwritten deviations in a ready change package and writes them directly into the relevant design and documentation files. This enforces gate checks before finalizing the archival relocation.

Does the archival workflow enforce gate checks before moving change packages?▼

Yes, the archival workflow enforces gate checks to validate document synchronization and spec merging. These checks update relevant truth artifacts, ensuring only fully validated change packages are moved to the truth-root for auditable closure.

Can I use optional controls to limit the scope of an archiving workflow?▼

Yes, the archiving workflow provides optional controls for scope, reports, and templates. These controls let you define specific boundaries for the backwrite and spec-merging processes while still generating an auditable closure.