菜单
Reconcile DE/IP/phase/DR execution artefacts during delta work. Use this when implementation changes structured execution state, not just notes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | update-delta-docs |
| description | Reconcile DE/IP/phase/DR execution artefacts during delta work. Use this when implementation changes structured execution state, not just notes. |
This skill is for structured delta execution documentation.
Do not use it as a replacement for /notes.
Use /notes for compact implementation journaling on the current card.
Use /update-delta-docs when execution changed the structured artefacts that
govern or describe the work.
Inputs:
DE-XXX.mdIP-XXX.mdIP-XXX.PHASE-XX)DR-XXX.md when design, risks, or execution assumptions changednotes.md for the companion execution logUse this skill when any of the following became true:
Process:
DE, IP, and phase sheet together.IP-XXX.md next:
DE-XXX.md if execution changed scope, dependencies, risks, or tracked open questions.DR-XXX.md if execution changed design intent, tradeoffs, or code-impact assumptions.notes.md remains consistent with the structured artefacts, but do not duplicate every detail.Run spec-driver validate file against each updated artefact (delta, DR, IP, phase) to confirm metadata consistency.
/consult.Outcomes:
/notes remains a lightweight execution log rather than a hidden structured-doc workflow.Canonical reconciliation runsheet for AUD artefacts. Create or update the audit, disposition every finding, reconcile specs/contracts, and hand off to closure only when audit state supports it.
Close a delta safely - satisfy coverage gates, complete the delta command, and verify owning-record lifecycle updates.
Orchestrate parallel implementation via sub-agents. Drives an entire delta to completion across all phases — planning, dispatching, merging, and continuing automatically. Batches tasks by token budget, routes to appropriate models (sonnet/opus), and dispatches workers in isolated worktrees. Use instead of /execute-phase when a phase has parallelizable work.
Mandatory execution skill for any delta/IP implementation phase. Use it before code changes, move the owning delta to in-progress, keep notes current, reconcile structured execution docs, and surface blockers early.
Whenever you complete a task or phase - record implementation notes.
Mandatory onboarding. Every agent MUST execute this on startup, or as soon as becoming aware of it.