adversarial-squad
Deploy a bounded, profile-loaded adversarial review squad at a mission point-cut so independent doctrine lenses converge on…
Operate pre-spec or in-mission research workflows while keeping findings tied to mission decisions.
Claude Code
$ npx -y skills add spec-kitty/spec-kitty --skill spk-mission-research --agent claude-code
Codex
$ npx skills add spec-kitty/spec-kitty --skill spk-mission-research -a codex -y
Cursor
$ npx skills add spec-kitty/spec-kitty --skill spk-mission-research -a cursor -y
Gemini CLI
$ npx skills add spec-kitty/spec-kitty --skill spk-mission-research -a gemini-cli -y
GitHub Copilot
$ npx skills add spec-kitty/spec-kitty --skill spk-mission-research -a github-copilot -y
OpenCode
$ npx skills add spec-kitty/spec-kitty --skill spk-mission-research -a opencode -y
Windsurf
$ npx skills add spec-kitty/spec-kitty --skill spk-mission-research -a windsurf -y
name: spk-mission-research description: "Operate pre-spec or in-mission research workflows while keeping findings tied to mission decisions."
Use this skill when a mission needs discovery, external facts, design precedent, technical investigation, or decision support.
1. Use `/spec-kitty.research` for pre-spec discovery, before a spec or plan exists: capture decisions, evidence, and open questions directly in `research.md` (create or extend it; never truncate it). 2. On a mission type that ships research templates (today: the `research` mission type), once that mission's plan is filled in you can additionally run `spec-kitty research --mission <handle>` to scaffold `research.md`, `data-model.md`, and the CSV stubs from the shipped templates. Other mission types, including `software-dev`, have no such scaffold — the command creates nothing for them. 3. Write findings as decision-ready evidence, not a loose reading list. 4. Record assumptions, source quality, and unresolved questions. 5. Return findings to `spk-mission-specify` or `spk-mission-plan`.
Research is not a substitute for a spec. It should narrow uncertainty enough for the next mission phase.
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