| name | pdm-sync |
| description | Use this skill for hook-safe incremental Reverse Sync after a project already has active project-doc-modes docs. This is the /pdm-sync entrypoint and the managed hook continuation target. |
PDM Sync
Use pdm-sync for non-interactive incremental Reverse Sync.
Primary references live in the sibling pdm skill package:
../pdm/SKILL.md
../pdm/references/rules.md
../pdm/references/sync.md
../pdm/references/sdd.md
../pdm/references/verify.md
Expected behavior:
- Treat hook payloads, transcript snippets,
git status --short, changed files, verification output, user decisions, and implementation discoveries as evidence.
- Do not ask setup questions.
- Do not rerun init, full migration, broad archive, or doc-tree rebuild.
- Do not edit code, tests, dependencies, runtime configuration, APIs, schemas, or product behavior.
- Update only active docs affected by the latest session: status, implementation records, reviews, decisions, release notes, indexes, or Reverse Sync targets.
- Update PRD, PHASE, or SPEC only when the session explicitly changed intended behavior, architecture, requirements, or acceptance criteria.
- Run
pdm-verify semantics after sync.
- Do not stage, commit, or push unless the user explicitly asks.
Do not write this skill name, /pdm-sync, local install paths, or SKILL.md into generated target-project docs.