菜单
Implement a bounded code change from a request, spec, or implementation plan. Use when executing implementation work and choosing between quick, bounded, and tracked modes. Not for producing a spec (use to-spec) or an implementation plan (use to-plan) before coding.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Eckii24/dotfiles --skill implementation-workflow命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | implementation-workflow |
| description | Implement a bounded code change from a request, spec, or implementation plan. Use when executing implementation work and choosing between quick, bounded, and tracked modes. Not for producing a spec (use to-spec) or an implementation plan (use to-plan) before coding. |
Use for code delivery. Optimize for evidence and signal density, not ceremony.
| Mode | Use when | Default shape |
|---|---|---|
| Quick Task | Small/local, obvious scope | Direct work; no artifacts/subagents |
| Bounded Delivery | Clear change across ~1-3 areas | Direct work; delegate only at a real responsibility boundary |
| Tracked Project | Multi-session, expensive restart/handoff, or explicitly requested | Phase contracts + .ai/current-work.md pointer |
Default Quick/Bounded. Direct work is normal in both. Delegate only for independent evidence, a separately owned deliverable, isolated review, or a context boundary; file count, routine tests, and ordinary diagnosis are not enough. Do not inherit a stale/completed/unrelated anchor.
Before work, collect only: objective, acceptance criteria, exact paths/symbols, constraints/non-goals, and test commands. Extract this once into a handoff packet. Do not make every child reread full plan/spec/current-work files.
Use a scout only to answer a real uncertainty. Good output: exact paths, symbols, line ranges, tests, and one start point. Bad output: file dumps or generic architecture prose.
When a real boundary exists, give one worker a coherent vertical slice with owned acceptance tests. A plan bullet, file, type error, or local repair is not automatically a boundary. The worker implements, evaluates, and fixes in-scope failures before returning a compact status packet.
Parallelize only read-only or isolated work. Never share a mutable checkout between concurrent workers unless the caller explicitly provides safe isolation.
For each phase state: objective, acceptance evidence, child shape, and escalation condition.
/orchestrate mode owns delegation budgets and stop rules; do not copy them into workers or entrypoints.For tracked work, use project-memory as the authoritative anchor, handoff, resume, and archive contract. This workflow owns mode selection and phase delivery; update tracked state only at material boundaries.
Report: mode, phase/status, changed paths, eval/test results, one decision/blocker, exact next action, current-work path if used, and review result/recommendation.