菜单
Lightweight spec-driver fluency for dispatch workers. Provides the minimum vocabulary, commands, and boundaries needed to navigate a spec-driver project without full boot ceremony. Loaded via skills: frontmatter in dispatch-worker agent definition.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | sub-driver |
| description | Lightweight spec-driver fluency for dispatch workers. Provides the minimum vocabulary, commands, and boundaries needed to navigate a spec-driver project without full boot ceremony. Loaded via skills: frontmatter in dispatch-worker agent definition. |
Read .spec-driver/agents/exec.md for invocation conventions.
| Term | Meaning |
|---|---|
| DE-xxx | Delta — a scoped change bundle |
| DR-xxx | Design revision — architecture patch for a delta |
| IP-xxx | Implementation plan — phased execution plan |
| Phase (IP-xxx-P0N) | One phase of an IP, with tasks and exit criteria |
| FR-xxx | Functional requirement (behavioural, testable) |
| NF-xxx | Non-functional requirement (quality: perf, reliability) |
| VT | Verification Test — automated test proving functionality |
| VA | Verification by Agent — agent-generated test report or analysis |
| VH | Verification by Human — manual verification requiring user sign-off |
Query before touching unfamiliar files:
spec-driver list memories -p <file-path> [-c "<command context>"] [--match-tag <tag>]
View a memory:
spec-driver view memory <memory-id>
Create a memory for durable findings:
spec-driver create memory "<name>" --type <fact|pattern|gotcha> [--summary "..."] [--tag ...]
You are a focused implementation worker. You operate within the scope assigned by the dispatch orchestrator.
Do:
Do not:
/boot, /using-spec-driver, /execute-phase, or other
ceremony skills