adversarial-squad
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so independent doctrine lenses converge on…
Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.
Claude Code
$ npx -y skills add spec-kitty/spec-kitty --skill spk-run-implement-review --agent claude-code
Codex
$ npx skills add spec-kitty/spec-kitty --skill spk-run-implement-review -a codex -y
Cursor
$ npx skills add spec-kitty/spec-kitty --skill spk-run-implement-review -a cursor -y
Gemini CLI
$ npx skills add spec-kitty/spec-kitty --skill spk-run-implement-review -a gemini-cli -y
GitHub Copilot
$ npx skills add spec-kitty/spec-kitty --skill spk-run-implement-review -a github-copilot -y
OpenCode
$ npx skills add spec-kitty/spec-kitty --skill spk-run-implement-review -a opencode -y
Windsurf
$ npx skills add spec-kitty/spec-kitty --skill spk-run-implement-review -a windsurf -y
name: spk-run-implement-review description: "Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected."
Use this skill when a mission is in implementation/review lanes or the user wants the agent to coordinate implementers and reviewers.
1. Use `spk-run-next` to identify the active WP and lane. 2. Dispatch implementation only from runtime-provided prompt context. 3. Review each WP independently with `spk-run-review-wp`. 4. On rejection, feed structured reviewer feedback back into the next implementation attempt. 5. Continue until runtime returns terminal or a blocker.
`move-task --to for_review` runs the pre-review regression gate synchronously as part of the transition (#2570/#2493/#2555): it derives the affected test scope for the Mission's changed files and runs it at head before the command returns. That scoped run is a real subprocess and can take from seconds to a few minutes depending on scope size.
completion** — treat the `move-task --to for_review` command as still in flight until it exits, not as a fire-and-forget hand-back. Do not assume control returns immediately, and do not kill or retry the command while it is still running.
To disable it process-wide, set `SPEC_KITTY_SKIP_PRE_REVIEW_GATE` — the gate's own opt-out name; it no longer reads the sync-disable vocabulary (#3980). Either opt-out skips the gate before it resolves a workspace or spawns the subprocess.
observing a sub-agent that appears to hang on a `for_review` transition should first check whether the gate's scoped test subprocess is still running before treating the sub-agent as stuck.
For detailed orchestration mechanics, use `spec-kitty-implement-review` when available.
Spec-Driven Development with organizational governance. Specs tell AI agents what to build; Charter governs how they build it. Git-native missions, enforceable workflows, and consistent engineering standards across AI coding agents and harnesses.
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so independent doctrine lenses converge on…
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree…
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state…
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift,…
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action…
Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers:…
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
Create a new Architecture Decision Record with sequential numbering and AgentDB registration