sync-guidelineslisted

Re-vendor EVERYTHING this repo deploys into a live tree — the universal guideline docs (task-writing.md, procedures.md), the /groom /design /ops /deploy /wrap /sync-guidelines /gate skill directories, the sanctioned route-client scripts, and the config-tree hook — via a Claude-led three-way merge, never a file overwrite. The repo copy is the upstream source; the live copy may carry local edits (a vendored skill refined in place, an emergency script hotfix) that must be preserved. Use when the user says "sync guidelines", "re-vendor the skills", "deploy the grooming skills", "integrate the guideline updates", "pull the procedures/task-writing changes into config", or after merging a PR that changed config-template/, skills/**, scripts/*.mjs, or packages/backend/scripts/*.mjs.
phahadek/claude-orchestrator · ★ 1 · Code & Development · score 74

Install: claude install-skill phahadek/claude-orchestrator

# Sync Guidelines Every artifact this repo vendors into a live tree — the guideline docs, the grooming/design/ops skill directories, and the sanctioned route-client scripts — is **not mechanically deployable**. Two copies exist with different jobs: - **Upstream source** (`<repo>/config-template/<doc>`, `<repo>/skills/<name>`, `<repo>/scripts/<name>.mjs`, `<repo>/packages/backend/scripts/<name>.mjs`): the version-controlled source of truth. Where changes are authored and reviewed. - **Live copy** (`<config-tree>/<doc>`, `~/.claude/skills/<name>`, `~/.claude/scripts/<name>.mjs`): what sessions actually read/run. It may carry content the upstream doesn't have — the guideline docs' filled-in **Project index** and concrete **project examples**, or a skill instruction that was refined directly on a live host before the change made it back into the repo. A `cp` fails both directions: overwrite clobbers local content; seed-only never propagates upstream updates. **There is no re-vendor path in this repo that force-overwrites a live copy.** (A previous mechanism, `scripts/deploy-grooming.mjs`, did exactly that — a blind `cpSync(..., { force: true })` — and it silently destroyed vendored-local content in the `/ops` skill with no backup and no way to detect it after the fact. It has been removed outright.) Deploying an update to any of these is an **integration**: take what changed upstream since the last integration and weave it into the live copy — preserving local conten