菜单
Implement exactly one OpenSpec task and produce a validation bundle. Use when a CLI or tool is assigned as the "code writer" role in an orchestra workflow. Defines strict permission boundaries so that validation, bookkeeping, and commits remain owned by the supervisor.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | openspec-implementer |
| description | Implement exactly one OpenSpec task and produce a validation bundle. Use when a CLI or tool is assigned as the "code writer" role in an orchestra workflow. Defines strict permission boundaries so that validation, bookkeeping, and commits remain owned by the supervisor. |
You are a Worker. Your responsibility is to implement one concrete task and produce a validation bundle.
tasks.md for context and select only the assigned task.proposal.md and design.md if present, for implementation guidance.logs/worker_startup.txt FIRST before any code changes.ACCEPT: criteria.BUNDLE (RUN #n): line under the selected task in tasks.md.[ ] to [x]).EVIDENCE, PASS, FAIL, or RESULT lines.feature_list.json.Create the bundle at the path specified in your task prompt.
See bundle-rules.md for required files and naming conventions.
After creating the bundle, write exactly one formal line under the selected task:
BUNDLE (RUN #n): MODEL=<model-id> | SCOPE: <CLI|GUI|MIXED> | VALIDATION_BUNDLE: <bundle-path> | HOW_TO_RUN: run.sh/run.bat
Output ONLY:
BLOCKED: <short factual excerpt of the error or missing information>
NEEDS: <next concrete unblock step>
Do not guess. Do not implement partial workarounds. Report the blocker precisely.
For the full permission boundary details, see worker-contract.md.
Perform pass confirmation bookkeeping after a task validates successfully. Use after a PASS evidence line has been written. Handles checkbox toggle, feature_list.json update, progress.txt append, and optional checkpoint commit.
Supervise one OpenSpec task at a time through any configured dispatcher while preserving strict role boundaries and auditable evidence. Use when a change is tracked in an OpenSpec tasks.md and a worker must implement exactly one eligible task, produce a validation bundle, and leave final validation and bookkeeping to the supervisor.
Validate an OpenSpec validation bundle and produce auditable evidence. Use when a worker has produced a BUNDLE and the supervisor needs to run validation and record a formal EVIDENCE line. Can be used standalone (after manual implementation) or as part of the supervisor workflow.
Dispatch a task via any generic CLI tool such as aider, cursor CLI, or other AI coding assistants. Use when the supervisor needs to delegate implementation to a non-Codex, non-Claude CLI tool.
Dispatch a task to Codex CLI for execution. Use when the supervisor needs to delegate implementation to Codex running in full-auto mode. Codex will run in a sandboxed environment and apply file changes via patch.
Hand off a task to a human for manual implementation. Use when no automated dispatcher is available, the task requires human judgment, or the supervisor wants explicit human confirmation before proceeding.