archie-sync

Reconcile completed code changes into Living Blueprint and per-folder intent snapshots.

16|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/BitRaptors/Archie --skill archie-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archie-sync
Source: https://github.com/BitRaptors/Archie/tree/main/archie/assets/workflow/sync
Command: npx skills add https://github.com/BitRaptors/Archie --skill archie-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents architectural documentation from drifting away from the code by reconciling completed session changes into Archie's Living Blueprint and per-folder intent snapshots.

Core Features & Use Cases

  • Change Reconciliation: Records code changes as descriptive statements and folds verified updates into the appropriate blueprint sections.
  • Intent Layer Maintenance: Updates touched folders' CLAUDE.md snapshots while preserving unrelated architectural guidance.
  • Governed Workflow: Separates descriptive mirror updates from deliberate contract amendments, incorporates plans and churn signals, and regenerates versioned task stories for review.
  • Use Case: After implementing a new API flow, use this Skill to capture the resulting behavior, update the relevant architectural and folder context, review the task story, and leave all changes ready for the user to commit.

Quick Start

Use the Archie sync skill to reconcile the current session's code changes into the Living Blueprint and affected per-folder intent files, then review the generated task story.

Frequently Asked Questions about archie-sync

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

FAQPage Schema
How do I keep architecture documentation aligned with code changes?

You prevent documentation drift by reconciling completed session code changes into a Living Blueprint and per-folder intent snapshots, folding verified updates into the relevant architectural documentation sections.

How do coding agents update repository documentation after implementation?

Coding agents update repository documentation by capturing implementation changes, churn signals, and captured plans, then regenerating versioned task stories that reflect the new code behaviors for user review and commit.

Do I need an installed Archie workspace to synchronize code and blueprints?

Yes, an installed Archie workspace with its sync utility is required to reconcile code changes, as the process depends on this environment to stage advisory amendments and preserve deliberate architectural rules.

How are per-folder architectural intent snapshots maintained during code synchronization?

Per-folder architectural intent snapshots are maintained by updating CLAUDE.md files for touched folders while strictly preserving unrelated architectural guidance, keeping localized context accurate without overwriting broader rules.

How to separate descriptive documentation updates from deliberate architectural contract amendments?

Descriptive updates are separated from deliberate contract amendments by staging advisory amendments independently, ensuring mirror updates reflect actual code while deliberate architectural rule changes remain isolated for review.