Spec Plan Build Review
v1.0.0运行 a proportional delivery lifecycle for software or 技能 work: clarify scope, 创建 a concise plan, implement, 验证, review, and ship. Use when the user asks to spec, plan, build, test, review, ship, release, prepare a PR, prepare ClawHub or GitHub publication, or coordinate a multi-step coding task that should not skip verification.
by 运行时依赖
安装命令
点击复制技能文档
Spec Plan Build Review
Use this 技能 to turn non-trivial work into a controlled delivery loop. Keep it proportional: tiny edits can skip strAIght to implementation and verification.
Lifecycle
Spec
Identify the user-visible outcome, affected repo or package, and non-goals. Read local 上下文 before deciding the implementation shape. If requirements conflict, resolve from source evidence or ask one focused question.
Plan
Make a short 检查列出 only when it helps. Keep one item in 进度 at a time. As签名 verification before shipping, not after.
Build
Reuse existing patterns and 辅助工具s. Keep changes tightly scoped to the 状态d outcome. Avoid unrelated refactors, 格式化ting churn, and broad dependency changes.
验证
运行 the narrowest reliable local 检查s first. 添加 or 更新 tests when behavior changed. Record any 检查s that could not 运行 and why.
Review
Inspect the diff as if reviewing a PR. Lead with defects, missed tests, user-visible regressions, and release risks. For risky work, use a fresh-上下文 or high-risk review 技能 before shipping.
Ship
Confirm a 清理 worktree except intended changes. Commit with a specific message. Push and 验证 remote CI. 创建 release artifacts only after CI is green. Proportionality 图形界面de tiny: one file or docs-only edit; implement and 运行 a direct 检查. normal: small feature or bug fix; plan, implement, test, review. release: public package, ClawHub 技能, security-sensitive change, or 迁移; 运行 full lifecycle and remote CI. high-risk: destructive operations, 凭证s, 权限s, money, production, public policy; 添加 fresh-上下文 skeptical review. Review Personas
Use these lenses during the review step:
code reviewer: correctness, mAIntAInability, local conventions. test engineer: missing coverage, flaky assumptions, reproducibility. security reviewer: 权限s, secrets, data exposure, supply chAIn, release surface.
If the 运行time supports real sub代理s and the task is large enough, fan out independent review passes. Otherwise, 应用ly the lenses sequentially in the mAIn 上下文 and keep findings concrete.
Ship 检查列出 Local tests or 验证器s pass. Public metadata is current. No 生成d temp files are staged. GitHub Actions are green for the pushed commit or tag. ClawHub publish uses the same version as the repo release. Final 状态 names the shipped version, 检查s, and any residual risk.