菜单
Synchronize a work branch with its base or align ProdOps artifacts with the current implementation. Use when fetching remote changes, resolving conflicts, updating from main, or when BDD Features, Event Storming, architecture, or the Release Trail are stale.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Proactive drift-scan cycle. Reads all active OBCs and Issues, identifies divergences, and repairs what can be automated. Runs across the entire active backlog, not for a specific OBC.
Read all active OBCs and compare declared state with backlogs and external tools. Produces a divergence list. Does not repair — only identifies gaps.
Event-driven cycle triggered by a product decision. Captures the decision as an OBC, attaches a Work Item, promotes it through the backlog hierarchy, and closes it when the OBC reaches Operational. Runs for a specific OBC.
Create or update an OBC from the decision that triggered the Diligence Sync cycle. Use when an Assessment decision, Discovery experiment, or Operation signal requires canonical state to be recorded before Work Items are created.
Synchronize OBC state across backlogs and tools. Runs event-driven cycle (diligence-sync) or proactive drift-scan cycle (diligence-async). Never touches product code.
Classify divergences from Scan and register them as pending Diligence items with severity and corrective action. Does not repair — only signals.
| name | sync |
| description | Synchronize a work branch with its base or align ProdOps artifacts with the current implementation. Use when fetching remote changes, resolving conflicts, updating from main, or when BDD Features, Event Storming, architecture, or the Release Trail are stale. |
Use this skill to make the repository internally consistent with the current ProdOps context or to synchronize a work branch with its intended base.
The Sync phase has two independent steps, each guaranteeing a distinct integrity:
rebase — integridade do repositório git (pronto para merge, base incorporada, testes preservados)align — integridade dos artefatos ProdOps (BDD, Event Storming, arquitetura, OBC e Release Trail refletem o diff do branch)Os steps são complementares: nenhum substitui o outro. O Sync não abre PR
(Finish), não roda a pipeline completa (Ship) e não reescreve decisões
de produto upstream. Quando invocado com um argumento de step (/sync <step>),
execute apenas aquele step. Caso contrário, execute ambos em sequência.
| Step | File | When to use |
|---|---|---|
rebase | steps/rebase/SKILL.md | Branch is behind origin, has conflicts, or needs to incorporate upstream changes |
align | steps/align/SKILL.md | BDD Features, Event Storming, architecture, or Release Trail are stale relative to what was implemented |
If the requested step is not listed, run the full flow.
AGENTS.mdprodops/artifacts/product/prodops/framework/journeys/assessment/prodops/artifacts/trails/sessions/ (active session trail)When invoked without a step argument, execute both steps in sequence:
prodops/, update only impacted files, record in Release TrailFor detailed branch synchronization mechanics, read references/workflow.md.