speckit-sync

Aggregate incremental specs from specs/ into a product-level current-spec.md.

15|5|Updated Feb 10, 2026

Search Tags:#automation #workflow #aggregation #specs #product-spec #living-document

Ready to run

npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill speckit-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-sync
Source: https://github.com/connor-git-yaml/cc-plugin-market/tree/main/plugins/spec-driver/skills/speckit-sync
Command: npx skills add https://github.com/connor-git-yaml/cc-plugin-market --skill speckit-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates incremental functional specifications from specs/ into a single, living product specification current-spec.md, ensuring a single source of truth for product teams.

Core Features & Use Cases

Scans specs/NNN-* directories under specs/ and merges their spec.md into a consolidated current-spec.md.
Outputs and maintains specs/products/<product>/current-spec.md, with a clear mapping to product scope.
Provides guardrails and guidance to ensure consistency and traceability across product specs.

Quick Start

Execute /spec-driver:speckit-sync to merge all incremental specs into the current product spec.

Frequently Asked Questions about speckit-sync

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

FAQPage Schema

How do I consolidate incremental product specs into a single living document?▼

To consolidate incremental product specs into a single living document, you can use an aggregation workflow that scans specs/NNN-* directories and merges them into a consolidated current-spec.md file. This ensures a single source of truth for product teams by automatically applying validation and product-mapping.

What is a Spec Driver workflow for aggregating functional specifications?▼

A Spec Driver workflow for aggregating functional specifications is a prompt-driven sync process that scans incremental specs and produces a product-level current-spec.md. It maintains traceability by mapping changes from individual spec.md files into a consolidated product scope document.

How do I merge multiple spec.md files from numbered directories into one current product spec?▼

You can merge multiple spec.md files by executing a sync command that scans your specs/NNN-* directories. The process aggregates these incremental functional specifications and outputs a unified current-spec.md file under specs/products/<product>/, including a summary of changes.

Does speckit-sync require any specific dependencies or components to aggregate specs?▼

No specific dependencies or components are required to aggregate specs. The tool operates independently using a fixed, prompt-driven sync process with built-in validation and product-mapping support to ensure consistency and traceability across your product specs.

Can I maintain traceability when merging incremental specs into a current product spec?▼

Yes, you can maintain traceability when merging incremental specs because the aggregation process includes built-in validation and product-mapping support. It generates a current-spec.md with a clear mapping to product scope and provides a summary of changes for consistency.

When should I use an automated spec aggregation workflow instead of manual merging?▼

You should use an automated spec aggregation workflow instead of manual merging when you need to maintain a single source of truth across many incremental functional specifications. It provides guardrails and validation to ensure consistency and traceability that manual merging often lacks.