docs-sync

You can orchestrate post-analysis documentation synchronization by aligning service-agent, technology-agent, and system-agent to a single source of truth. This process coordinates the generation of per-service docs, per-tech standards, and updates overview.md.

The best way to generate per-service docs and per-tech standards is by running an orchestration command against your design.md path. This coordinates multiple AI agents to extract specs from the design document and produce aligned technical standards.

You need to update overview.md when your project documentation enters a waiting state after the analysis phase. Orchestrating a documentation sync ensures the overview file reflects the latest design specs and per-service technical standards.

Yes, you can use AI agent orchestration to align multiple service documents to a single source of truth. By coordinating post-analysis tasks, the system synchronizes specs and ensures all service and technology documentation matches the core design.

Yes, the documentation synchronization process requires four documents to be in a waiting state. You execute the orchestration command by providing the path to the design.md file located within that waiting directory.

Documentation orchestration fails without a single source of truth because individual service and technology agents would generate inconsistent specs. The orchestration mechanism enforces a review process to ensure all downstream documentation remains synchronized with the design.