ad-hoc-profile-load
Legacy alias for resolver-backed profile loading. Use the canonical spk-doctrine-profile-load…
Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.
$ npx -y skills add spec-kitty/spec-kitty --skill spk-run-implement-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/spk-run-implement-reviewContext preview
The summary Claude sees to decide when to auto-load this skill.
Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.
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.
Legacy alias for resolver-backed profile loading. Use the canonical spk-doctrine-profile-load…
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so…
Recognize when a mission is a bulk edit and drive the occurrence-classification guardrail on…
Run charter interview, generation, context, and sync workflows for project governance in Spec…
Understand how Spec Kitty manages git: what git operations Python handles automatically, what…
Curate and apply canonical terminology across Spec Kitty missions. Triggers: "update the…