Documentation synchronization using Mem0 for tracking relationships between specs, architecture, ADRs, and roadmap
Documentation synchronization using Mem0 for tracking relationships between specs, architecture, ADRs, and roadmap
npx skills add https://github.com/vanman2024/planning-marketplace --skill doc-sync이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
Architecture design templates, mermaid diagrams, documentation patterns, and validation tools. Use when designing system architecture, creating architecture documentation, generating mermaid diagrams, documenting component relationships, designing data flows, planning deployments, creating API architectures, or when user mentions architecture diagrams, system design, mermaid, architecture documentation, or component design.
Templates and scripts for generating layered BUILD-GUIDE.json/md from Airtable plugin index - shows available commands organized by infrastructure layers
Templates, scripts, and examples for managing feature specifications in specs/ directory. Use when creating feature specs, listing specifications, validating spec completeness, updating spec status, searching spec content, organizing project requirements, tracking feature development, managing technical documentation, or when user mentions spec management, feature specifications, requirements docs, spec validation, or specification organization.
| name | doc-sync |
| description | Documentation synchronization using Mem0 for tracking relationships between specs, architecture, ADRs, and roadmap |
| tags | ["documentation","mem0","sync","relationships","tracking"] |
This skill provides tools and scripts for intelligently synchronizing documentation across the dev-lifecycle-marketplace using Mem0 for relationship tracking.
Purpose: Keep specs, architecture docs, ADRs, and roadmap interconnected and updated when dependencies change.
specs/{number}-{name}/spec.md) - Feature specifications derived from architecturedocs/architecture/*.md) - System design and component specificationsdocs/adr/*.md) - Architecture Decision Recordsdocs/ROADMAP.md) - Project timeline and milestonesUses Mem0 OSS (in-memory Qdrant) to store natural language relationships:
# Example memory
"Specification 001 (user-authentication) is derived from
architecture/security.md sections #authentication and #jwt-tokens,
and references ADR-0008 OAuth decision"
scripts/sync-to-mem0.pyScans documentation and populates Mem0 with relationships.
Usage:
python scripts/sync-to-mem0.py
What it does:
specs/*/spec.md files@docs/architecture/file.md#sectiondependencies: [001, 002]scripts/query-relationships.pyQuery Mem0 for documentation relationships.
Usage:
# Find specs that depend on a doc
python scripts/query-relationships.py "What specs depend on architecture/security.md?"
# Find all references to an ADR
python scripts/query-relationships.py "Which specs reference ADR-0008?"
# Get spec dependencies
python scripts/query-relationships.py "What does spec 001 depend on?"
scripts/validate-docs.pyValidate documentation consistency using Mem0.
Usage:
python scripts/validate-docs.py
Checks:
Spec Memory:
Specification {number} ({name}) is derived from architecture/{file}.md
sections {sections}, references ADR-{numbers}, and depends on specs {deps}.
Status: {status}. Last updated: {date}
Architecture Memory:
Architecture document {file}.md has sections: {sections}.
Section {section} is referenced by specs {spec_numbers}
Derivation Chain:
When architecture/{file}.md #{section} changes, these specs need review:
{spec_list}
# Navigate to project root
cd /path/to/dev-lifecycle-marketplace
# Run sync to populate Mem0
python plugins/planning/skills/doc-sync/scripts/sync-to-mem0.py
# Output:
# ✅ Scanned 15 specs
# ✅ Found 42 architecture references
# ✅ Created 57 memories in Mem0
# 📊 Project: dev-lifecycle-marketplace
# Check what's affected by changing security.md
python plugins/planning/skills/doc-sync/scripts/query-relationships.py \
"What specs are derived from architecture/security.md?"
# Output:
# Specs affected by architecture/security.md:
# - 001-user-authentication (sections: #authentication, #jwt-tokens)
# - 005-admin-panel (sections: #rls-policies)
# - 012-sso-integration (sections: #oauth)
# Check documentation consistency
python plugins/planning/skills/doc-sync/scripts/validate-docs.py
# Output:
# ✅ All architecture references valid
# ⚠️ Spec 003 references missing ADR-0015
# ⚠️ Circular dependency: 007 → 008 → 007
# ❌ Broken reference: @docs/architecture/deleted.md
The scripts use Mem0 OSS with in-memory Qdrant (no external dependencies):
config = {
"vector_store": {
"provider": "qdrant",
"config": {
"collection_name": "documentation",
"host": "memory", # in-memory mode
}
}
}
Uses user_id for multi-project support:
# Add memory for specific project
m.add(memory_text, user_id="dev-lifecycle-marketplace")
# Query specific project
m.search(query, user_id="dev-lifecycle-marketplace")
This skill powers these planning commands:
/planning:doc-sync - Populate Mem0 with current documentation/planning:impact-analysis <doc-path> - Show what's affected by changes/planning:validate-docs - Check documentation consistency/planning:update-docs - Interactive sync with user approvalRun sync after major changes:
# After updating architecture or ADRs
python scripts/sync-to-mem0.py
Check impact before modifying shared docs:
# Before editing architecture/security.md
python scripts/query-relationships.py "specs depending on security.md"
Validate before commits:
# Add to pre-commit hook
python scripts/validate-docs.py || exit 1
Use natural language queries:
# Install in virtual environment
python -m venv venv
source venv/bin/activate # or venv\Scripts\activate on Windows
pip install mem0ai
Ensure you're in the virtual environment where Mem0 is installed:
source /tmp/mem0-env/bin/activate
python scripts/sync-to-mem0.py
Run the sync script first to populate Mem0:
python scripts/sync-to-mem0.py
plugins/planning/README.mdplugins/planning/skills/spec-management/plugins/planning/skills/architecture-patterns/