# Spec Sync Routing

> Route shared Spec Sync guidance to each repository's generated local Spec Sync skill and configuration.

- Skill: `corvidlabs/spec-sync-routing` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add corvidlabs/spec-sync-routing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/corvidlabs/spec-sync-routing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: CorvidLabs (https://skillmd.com/u/corvidlabs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/corvidlabs/spec-sync-routing

---


# Spec Sync Routing

This is routing guidance, not a replacement for a project's Spec Sync contract.

## Install

Use the repository's Fledge integration where it covers the operation; use the
independent `specsync` binary for the remaining lifecycle commands. See
`spec-sync` for release selection and the shipped 6.0 workflow. Refresh generated
host skills with the selected binary's documented generator, commonly
`specsync agents install`.

## Find local truth first

When a repository uses Spec Sync, locate its generated local skill, configuration, and
canonical specs before choosing commands or editing lifecycle files:

1. Confirm the CLI: `specsync --version` (binary name is **`specsync`**, not `spec-sync`).
2. Find project config (often `.specsync/config.toml`; also `.specsync/config.json` or
   `.specsync.toml` in some repos) and `specs/`.
3. Read the existing generated host skill before refreshing it. Host paths may include:
   - `.codex/skills/spec-sync`
   - `.claude/skills/spec-sync`
   - `.cursor/skills/spec-sync`
   - `.gemini/skills/spec-sync`
4. Use the shared catalog `spec-sync` skill for **principles only**.

The local generated skill and configuration are authoritative for that repository's
command syntax, paths, policy, and validation. Check that they match the selected
binary and supported workflow; stale generated guidance is a reason to inspect the
documented migration path, not to prefer a legacy release. Never overwrite an existing
change ledger to force a newer workflow.

If the repository can generate or refresh its local Spec Sync skill, do that after
installing this non-colliding routing entry. Do not install the shared `spec-sync` catalog
entry over a generated local skill path. Do not overwrite or silently replace generated
local material with shared text.

## Route workflow questions

For change lifecycle, approval boundaries, evidence, finalization, and archive behavior,
read the shared `spec-sync` skill first and then follow the generated repository-local
skill and configuration. They define the workflow; this skill only tells you where to
find it.

For code↔spec graph inspection, see `atlas`. For deterministic change risk, see `augur`.