What is Suspec?
Suspec is a skill-delivered method: agents get the mechanical work; humans get the decisions. Your harness writes code. Suspec puts explicit intent, evidence, and review around it.
Skills install independently. Use the one the work needs.
It provides:
- an inline path for work too small to need a file;
- specs with verifiable requirements;
- task packets for separately dispatchable slices;
- inventories and change plans for structural work;
drillto lock language, obligation, place, then slice before one write;- independent review on the native PR, via Revolver, Triple-check, or Bulletproof;
- durable-lesson routing to native memory or project records;
- deterministic checks over recorded structure.
It does not replace plan mode, project instructions, issue trackers, PRs, CI, tests, or human acceptance. It does not write a review file.
Proportional rigor
Use the least structure that changes execution or review:
- State a trivial fix and its verification inline.
- Write a spec when intent needs a working contract.
- Add inventory, change planning, task splitting, or
drillonly when the work demands them. - Escalate independent review with risk. The implementer cannot accept their own work.
The keys remain intent, review, and findings. Everything else must justify its cost.
The six-step sequence (intent -> spec -> implement -> review -> check -> findings) is the path for
spec-governed work, not the product.
Boundaries
Transient means transient. Suspec artifacts are working scaffold, not a second product database. Code, tests, decisions, issues, PRs, maintained documentation, and supported native memory hold durable truth. Suspec neither intercepts native plans nor creates a repository-local store.
The CLI checks shape, not truth. It does not prove recorded evidence or render a review decision. Independent review judges evidence; humans accept, waive, defer, or request changes.
Next: workflow.
Need a starting point? Install the skills