菜单
Emit the Build Handoff Summary artifact in its fixed format. Use at the end of a build, immediately after /3p-review passes — invoked by the build-model workflow (dedicated build model) or by the main model after all build phases. Produces the exact handoff template the reviewing model consumes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Maintain and manage features and bugs on GitHub. Creates, updates, lists, and links GitHub issues and project cards.
Recommend what to work on next by reading the backlog (bugs.md, features.md, plans/) and considering what is already loaded in the current conversation context. Minimizes context thrash — prefers tasks aligned with current context. Recommends bugs when context is low, features when resources are plentiful.
Configure the Structured Agentic Development Workflow — set testing methodology (TDD/BDD), output style (caveman brevity), and persist preferences to agent memory.
Write a formal phased implementation plan to docs/plans/new/. Use after brainstorming is complete and a direction has been chosen. Creates a plan file that decouples the planning agent from the building agent.
Independent third-person code review. Use after ALL build phases are complete for a holistic review of the entire feature, or anytime the user wants a quality gate. Switches persona to a Senior Architect who did NOT write the code and now owns it — it must meet world-class standards.
The Structured Agentic Development Workflow — orchestrates brainstorm, write-plan, build-phase, 3p-review, handoff-summary, triage, test-driven-development, systematic-debugging, and verification-before-completion skills. Use when starting new work, switching between development phases, or when the user asks about the workflow. A dedicated build model uses the build-model workflow instead of this one.
| name | handoff-summary |
| description | Emit the Build Handoff Summary artifact in its fixed format. Use at the end of a build, immediately after /3p-review passes — invoked by the build-model workflow (dedicated build model) or by the main model after all build phases. Produces the exact handoff template the reviewing model consumes. |
| argument-hint | [plan-file-path] |
| allowed-tools | Read, Glob |
You are emitting the Build Handoff Summary — the single artifact that carries a completed, reviewed build to the next reader.
Output style: Check memory for
workflow-config:caveman-level. If set, adapt your output brevity to that level while preserving technical accuracy.
This skill is invoked after the build is complete and after /3p-review has passed. It does not build, test, or review — it only produces the handoff record. If /3p-review has not run yet, stop and run it first; the summary records the review result.
Reproduce the template below exactly — same headings, same order, same casing. Fill in the bracketed parts from what was actually built and reviewed. Do not rename sections, add sections, drop sections, or replace the template with your own prose. This is a fixed artifact format so the consuming model can parse it reliably.
## Build Handoff Summary
**Plan:** [plan file path]
**3p-review:** [PASS — zero open findings | the findings that were raised and how each was resolved]
### Deviations
- **Phase N: [Name]** — [what changed and why, one line]
- (Only list phases that deviated from the plan. If nothing deviated, write "None.")
### Concerns
- [Anything the next reviewer should specifically investigate or validate]
- (If none, write "None.")
3p-review line is mandatory. It is the evidence that review happened. If review surfaced findings, list them and how each was resolved — do not write "PASS" unless the review is genuinely clean./build-model): present the summary, then STOP. The user carries it to the main model./verification-before-completion → archive the plan.