메뉴
Use when finishing an implementation — syncs documentation to the change by updating specs, catalogs, and design artifact status (finishing-a-development-branch Step 2b).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | doc-sync |
| description | Use when finishing an implementation — syncs documentation to the change by updating specs, catalogs, and design artifact status (finishing-a-development-branch Step 2b). |
代码落地后的文档对账。比较实现结果与文档现状，更新偏离部分。
启动时公告： "使用 doc-sync skill 进行文档对账。"
由调用方（finishing / brainstorm Abandoned）传入：
new-feature / bug-fix / abandoned不同 context 走不同 Step 组合，避免在无意义的 Step 上空转：
| context | Step 1 Capability Spec 对账 | Step 2 索引（FEATURE-CATALOG + CODEMAP） | Step 3 Design |
|---|---|---|---|
new-feature | 执行（spec 不存在则跳过） | CODEMAP 重扫；FEATURE-CATALOG Status=Implemented + Impl=Done | 存在则 → Implemented |
bug-fix | 执行（spec 不存在则跳过） | CODEMAP 重扫；不改 feature status | 跳过 |
abandoned | 跳过 | FEATURE-CATALOG Status=Abandoned（CODEMAP 不变） | 存在则 → Abandoned |
spec 是权威行为契约，代码 conform 它。本步把 change 的行为 delta apply 到 docs/specs/，并 fresh-eyes 校验。
前置判断：定位行为 delta
docs/changes/<feature>/specs.md（brainstorm / bug-fix Case B 写的 delta）Apply（specs.md 存在时）：
把 delta 落到对应 docs/specs/<capability>-spec.md：
+ 行（ADD / MODIFY）→ 并入 spec 的 Requirements / Scenarios- 行（REMOVE）→ 从 spec 删出+）→ 创建新 capability spec 文件按 context：
| context | 动作 |
|---|---|
new-feature | apply changes/<feature>/specs.md delta → specs/ |
bug-fix Case A（spec 对） | 无 delta；spec 不动，仅验代码 conform |
bug-fix Case B（spec 错 / 缺 / 歧义） | apply changes/<feature>/specs.md delta → specs/（delta 在 bug-fix 流程中写）+ 代码已修 |
abandoned | 跳过（Step 2 标 Abandoned） |
| refactor | 无 delta；spec 必须不动——若发现需改 spec = 该"refactor"偷改了行为，升级或上报 |
Fresh-eyes verify（apply 后，独立视角，非 apply 者 self-check）：
+ 是否进了 spec、每个 - 是否已删、MODIFY 是否替换到位git diff <base_SHA>..HEAD 的实际行为符合 apply 后的 spec 契约；代码偏离正确契约 = 实现 bug（Case A），标记不改 spec核心：spec 正文只在"契约本身变了"时改（经 delta apply），不为"代码变了"就抄。deviation-append 机制已废除。
调用 doc-ops skill（sync 模式，scope 同时覆盖 FEATURE-CATALOG 与 CODEMAP）：
new-feature / bug-fix，即代码有变更时）：重扫 changed_files 的目录与模块结构，更新「目录结构」与「关键模块」表new-feature → 该 feature 的 Status=Implemented 且 Implementation Status=Done（同时设两列，修复原仅设子列的不对称）bug-fix → 不改 feature status（仅 CODEMAP 反映修复）abandoned → 该 feature 的 Status=Abandoned检查 docs/designs/<feature>/ 是否存在；不存在 → 跳过本步
确定追加目标文件（按存在性 fallback）：
| 优先级 | 文件 | 出现场景 |
|---|---|---|
| 1 | docs/designs/<feature>/review-verdict.md | design-workflow V2 完整路径产物 |
| 2 | docs/designs/<feature>/intent.md | design-workflow L1 轻量路径产物（无 review-verdict.md） |
两个都不存在 → 跳过本步并向调用方报告。
context=new-feature → 在目标文件末尾追加：
## Implementation Status
**状态**：Implemented
**日期**：YYYY-MM-DD
context=abandoned → 在目标文件末尾追加：## Implementation Status
**状态**：Abandoned
**日期**：YYYY-MM-DD
**原因**：[由 finishing 传入]
changes/<feature>/specs.md delta apply 到具体 Requirements/ScenariosUse when starting any creative work — creating features, components, or functionality, modifying behavior, or solving ambiguous problems — before design or implementation. Covers product discovery, competitive research, feature analysis, technical design, and capability spec writing. Applies to every project; routes to writing-plans (non-UI) or design-workflow (UI).
Use when finishing an edit to source files — runs format, typecheck, and console.log detection before moving to the next task.
Use when implementation of a bug fix or feature task is complete — dispatches the appropriate language and global reviewers and returns a binary APPROVE/BLOCK verdict.
Use when about to git commit — validates commit message format, lints staged files, and scans staged content for secrets and debug artifacts.
Use when reaching the design-workflow V2-4 hard gate — adversarially reviews design artifacts (token coverage, contract completeness, artifact consistency, accessibility docs, responsive coverage, DESIGN.md compliance) against docs/designs/<feature>/ before development handoff.
Use when a task involves UI — new pages, components, visual interactions, or design tokens — including work in docs/designs/, *.pen files, or with Pencil MCP tools. Skip for backend-only, config-only, or refactoring without visual impact. Routes to writing-plans on completion.