Menú
Scope intentional change as a delta. Define applies-to specs/requirements, risks, and closure targets before implementation.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
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.
Reconcile DE/IP/phase/DR execution artefacts during delta work. Use this when implementation changes structured execution state, not just notes.
Basado en la clasificación ocupacional SOC
| name | scope-delta |
| description | Scope intentional change as a delta. Define applies-to specs/requirements, risks, and closure targets before implementation. |
You are converting intent into a concrete change bundle.
Inputs:
Process:
.spec-driver/agents/workflow.md.spec-driver/agents/policy.md.spec-driver/hooks/doctrine.md/shape-revision.uv run spec-driver create delta "<title>" --spec SPEC-XXX --requirement SPEC-XXX.FR-001uv run spec-driver create delta --from-backlog ISSUE-XXX--from-backlog auto-populates context_inputs and relations from the source item.--from-backlog), ensure:
context_inputs includes type: issue (or appropriate type) with the backlog item IDrelations includes type: relates_to (or more specific type) with the backlog item ID as targetapplies_to.requirements includes any requirement IDs from the backlog itemDE-XXX.mdDR-XXX.md (if non-trivial change)IP-XXX.mdDE-XXX.md to make scope explicit:
applies_to specs/requirements/draft-design-revision before /plan-phases unless explicitly instructed by the user to skip a DR./plan-phases comes after DR work, not instead of it./plan-phases to create/refine phase sheets before implementation.Outcomes:
DE-XXX is consistent with it.