菜单
Execute the per-wave implementation loop: implement against spec, run verification, fix failures, repeat until green — then stop and request human checkpoint. Use during active wave development. Stops at human checkpoint; does not advance to the next wave.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | loop-spec |
| description | Execute the per-wave implementation loop: implement against spec, run verification, fix failures, repeat until green — then stop and request human checkpoint. Use during active wave development. Stops at human checkpoint; does not advance to the next wave. |
| disable-model-invocation | true |
| paths | AGENTS.md, docs/specification/**, src/** |
| metadata | {"background_eligible":true,"background_trigger":"wave issue moved to In Progress on board"} |
Execute the per-wave loop:
implement → verify → fix → repeat → human checkpoint
{check_command} and {test_command} from the
harness profile (or tests_readme). Both must pass before committing./ground-spec. Do not self-approve./ground-spec or the wave PR review.docs/specification/reports/Implementation-Plan-{initiative}.md W{N})/pre-implement for this wave{check_command} — static checks (from harness profile or AGENTS.md){test_command} — unit verification (from harness profile or tests_readme){ground_command} — spec ground check (optional; from harness profile if defined){check_command} — zero warnings/errors required.{test_command} — all tests pass required.{ground_command} if defined./ground-spec.{check_command} exits 0{test_command} exits 0{ground_command} exits 0 (if defined)/ground-spec runs → as-built status updated/pre-implement (checklist produced)
↓
/loop-spec ← YOU ARE HERE
implement task → verify → fix → repeat
human never sees intermediate failures
↓
all green
↓
/ground-spec (validates wave against spec FRs, produces §Contracts produced)
/loop 15m loop-spec: implement W{N} tasks in order per plan,
run {check_command} and {test_command} after each task,
fix failures before moving on, stop when all tasks green.
After the dev team has written their spec slice from the PRD, review it against the current codebase — baseline, gaps, impact, test harness, architecture governance (ADR + MDC), risks, and 4-lane triage. Use when the dev has drafted the spec and wants to check buildability before technical review and planning. Runs while the spec PR is open.
Before implementing one wave slice, produce a pre-flight checklist: verify the prior wave's human gate is satisfied, confirm contracts consumed from prior Ground Reports match what was actually built, then read specs/ADRs/rules. Use when starting implementation, opening a branch, or asked what to read before coding.
After feasibility (and technical review when applicable), produce a wave-level implementation plan with REQ/TASK/FILE/TEST tables and a WorkManifest YAML seed section (§9). Runs while the spec PR is open, before spec merge. Board seeding (gh issue create) happens after spec PR merge — not before.
After feasibility, produce a principal-engineer design document: resolve all engineering decisions (ADRs, interface contracts, test policy, module boundaries), draft any required ADRs, and route only true product questions back to PM on the meta PRD PR. Use before /spec-implementation-plan when the feasibility report contains NEW-ADR findings, Critical/Should-fix engineering items, or unclear module boundaries. TDD commits on the spec PR branch; PE gives GitHub Approve on the same spec PR.
Translate the PRD into a spec slice for this repo. Reads the PRD from the meta PRD PR branch or merged develop, extracts capabilities relevant to this repo, and drafts docs/specification/product/INIT-*.md. Use after engineering opens the spec PR and before /initiative-feasibility.
Map a PRD to affected repos using the service catalog. Reads the PRD and config/service-catalog.yaml from <client>-meta, matches PRD capabilities to service descriptions, and posts an impact map as a PR comment on the meta PRD PR for tech lead confirmation. Run in <client>-meta Cursor session after PRD is validated and before engineering opens spec PRs in app repos.