Integrations
Integrations carry Suspec across tool boundaries. They do not become product owners. Skills carry the method; Markdown and explicit paths carry the work.
CLI
suspec-cli (opens in new tab) runs read-only deterministic checks over explicit paths. See its public contract (opens in new tab) and Suspec's check catalog.
MCP
suspec-mcp (opens in new tab) exposes the checker to shell-less MCP clients. Its repository owns the exact tools, schemas, envelope, and installation contract (opens in new tab).
Agents with shell access can call the CLI directly.
Harnesses
Give any worker:
- project instructions;
- the spec and optional task by absolute path;
- the repository or worktree.
The UI and provider are replaceable by design. Suspec ships no custom agents.
Project systems
Keep existing owners:
- issue trackers hold backlog and source IDs;
- PRs show diffs and discussion;
- CI runs commands;
- review maps those results to requirements;
- project policy decides which CLI exit codes block;
- project records hold durable decisions and lessons.
The checker verifies coverage, evidence presence, references, and command matches for structured
verify blocks. Free-form evidence receives advisory human review. Suspec never owns credentials,
model settings, editor UI, tracker state, CI configuration, or merge authority.
Adopter repositories receive no Suspec configuration, directories, or gitignore entries. Their own agent guides remain project policy.
Previous: findings and memory. Start: what Suspec is.
Need a starting point? Install the skills