菜单
Implement one ready slice, bug fix, or PR follow-up from the configured issue tracker. Use when Codex needs to read a durable work item, make scoped code changes, use TDD where practical, run verification, prepare acceptance evidence, and hand off one completed unit of work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Shared vocabulary and decision process for designing module interfaces and test seams. Use when Codex needs to decide where a seam belongs, judge whether a module is deep or shallow, design an interface that serves slicing and acceptance, or make code easier to test and navigate.
Maintain a repository's domain vocabulary and architecture decision records. Use when Codex needs to sharpen terminology, resolve ambiguous domain concepts, update CONTEXT.md, create ADRs, or support grill-with-docs, triage, TDD, diagnosis, or architecture work with durable domain language.
Clarify a feature, refactor, architecture idea, or product plan against existing code and domain docs. Use when requirements, terminology, constraints, or success signals are unclear before to-prd, to-issues, triage, or implementation, and Codex should update CONTEXT.md or ADRs only when domain terms or decisions crystallize.
Scan a codebase for architecture friction and deepening opportunities. Use when Codex needs to audit old code, find shallow modules, improve testability, identify seams before implementation, or report architecture blockers without directly changing product code.
Move issues, external PRs, new ideas, manual test feedback, existing-codebase audits, and regression reports through workflow triage states. Use when Codex needs to classify work, verify claims, detect already-implemented behavior, ask for missing info, create agent-ready briefs, or route changes before implementation.
Lightweight acceptance gate for completed slices, bug fixes, PRs, or implementation branches. Use when Codex needs to verify that work matches the originating issue or PRD, prove acceptance criteria and regression checks, decide pass/fail/blocked before handoff, or record acceptance evidence in GitHub, a PR, or local markdown.
| name | implement |
| description | Implement one ready slice, bug fix, or PR follow-up from the configured issue tracker. Use when Codex needs to read a durable work item, make scoped code changes, use TDD where practical, run verification, prepare acceptance evidence, and hand off one completed unit of work. |
Implement exactly one ready work item. The input should be a slice issue, bug issue, agent brief, PR follow-up, or local markdown item.
Read docs/agents/issue-tracker.md, docs/agents/triage-labels.md, docs/agents/domain.md, and docs/agents/verification.md if they exist.
Resolve the user's link, title, branch, local path, or "next ready item" to a durable work item.
Extract:
If the item is not ready-for-agent and lacks a clear contract, route it back to triage instead of guessing.
Explore the current code fresh:
Identify the smallest vertical path that satisfies the work item. Do not pre-design broad future modules.
Write a short implementation plan:
Use tdd when there is a reasonable test seam. Use bug diagnosis when the task is a bug or a regression and there is not yet a red-capable feedback loop.
Keep changes scoped to the work item.
Prefer this loop:
When no automated seam exists, use a documented manual or command-based verification path and record the risk.
Run the smallest relevant checks during implementation and the broadest reasonable regression check before handoff.
Use docs/agents/verification.md when available. If a required command cannot run, record why and what evidence replaces it.
Collect:
Before declaring done, compare the final diff against the work item:
If the user asked for full acceptance in the same round, use acceptance after implementation. Otherwise leave the evidence ready for acceptance.
Return:
Update the issue, PR, or local work item when the tracker config and user request make that appropriate.
Do not merge, close, or mark complete when verification is missing, failing, or blocked.
