メニュー
Close the Work Item when the OBC reaches Operational state and update management artifacts. Use when the Release Trail confirms the delivery is complete.
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 | diligence/close |
| description | Close the Work Item when the OBC reaches Operational state and update management artifacts. Use when the Release Trail confirms the delivery is complete. |
Execute only the Close step of the Diligence Sync flow.
Responsabilidade: fechar o Work Item quando o OBC atinge estado Operational, garantindo que os artefatos de gestão reflitam o estado final do trabalho entregue.
Verificar em prodops/artifacts/trails/sessions/ se a entrega foi registrada no Release Trail com:
No arquivo prodops/artifacts/obcs/<obc-id>.md:
OperationalFechar o Work Item no backlog externo com:
Se o item estava representado em Roadmap ou Product Backlog, atualizar para refletir estado Operational.
git add prodops/artifacts/obcs/<obc-id>.md
git commit -m "docs(diligence): close OBC <obc-id> — Operational"
Concluído quando:
Operational no arquivo Markdownclose não valida a entrega — isso é Validate (Delivery CI Async).close não cria Release Trail entries — isso é Promote (Delivery CI Async).close não detecta Work Items órfãos em outros OBCs — isso é Scan.