skills.rest
NSEvteev
NSEvteevCOMMUNITY
Explore all skills by this author →
GitHub

docs-sync

Synchronize specs and docs by orchestrating service, technology, and system agents.

31|5|Updated Jan 14, 2026
Search Tags:#documentation#analysis#spec#workflow-automation#ssot#team-collaboration#docs-sync
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill docs-sync-nsevteev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-sync
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/docs-sync
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill docs-sync-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronizes specs/docs after the analytics chain, orchestrating service-agent, technology-agent, and system-agent with review. Use after Plan Dev (all four documents in WAITING) to create per-service docs, per-tech standards, and update overview.md.

Core Features & Use Cases

  • Orchestrates the three roles (service-agent, technology-agent, system-agent) to generate and align documentation.
  • Creates per-service documentation and per-tech standards, and refreshes the project overview.
  • Applicable whenever the analytics-to-docs handoff finishes, ensuring consistency across specs/docs.

Quick Start

Run /docs-sync <design-path> to initiate the synchronization process for the given WAITING design path.

Frequently Asked Questions about docs-sync

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

FAQPage Schema
How do I automate documentation synchronization after analysis?▼

Documentation synchronization automates spec and doc updates by orchestrating service-agent, technology-agent, and system-agent workflows against a single source of truth to ensure alignment.

What's the best way to generate per-service docs and per-tech standards?▼

Generating per-service docs and per-tech standards is handled by orchestrating role-based agents to create aligned documentation and refresh the project overview after the analytics chain finishes.

When do I need to trigger spec synchronization for my workflow?▼

Spec synchronization is needed after Plan Dev when four documents sit in WAITING, allowing the workflow to process the design path and update all related documentation.

Can I use a single source of truth to align multiple project specs?▼

A single source of truth aligns multiple project specs by driving the service-agent, technology-agent, and system-agent workflows to ensure consistency across all generated documentation.

How do I update overview.md after the analytics-to-docs handoff?▼

Updating overview.md happens automatically after the analytics-to-docs handoff by running the synchronization process on the WAITING design path to refresh the project overview.

Does documentation synchronization require specific dependencies to run?▼

Documentation synchronization requires no external dependencies, relying solely on the four WAITING documents from Plan Dev to orchestrate the agent workflows and generate aligned specs.

Related Skills

Explore More Content & Communication Skills→
oogDZoogDZ

plan-test-modify

Update test case IDs and statuses in test plan documents.

Community
Intermediate
oogDZoogDZ

docs-sync

Orchestrates post-analysis generation of per-service docs and per-tech standards.

Community
Advanced
DemonDamonDemonDamon
207

agenticx-agent-builder

Design, configure, and deploy AgenticX agents with roles, goals, tools, and LLM providers for scalable multi-agent systems.

Community
Advanced
villetakanenvilletakanen
29

spec-engineer

Create, reverse-engineer, or update living feature specs from code.

Community
Advanced