Skip to main content

Skip docs navigation
manual page/ Start here

Workflow

sourceSource: suspec/docs/02-basic-workflow.mdModified: 2026-08-19

Pick the skill the work needs

Campaigns own one durable multi-pull-request goal. Specs own verifiable intent. Drill locks one seam before write. Change plans own staged preservation and rollback. Independent review is a non-implementer on the native PR.

Trivial work

State the correction and proof inline:

example.txt

file
Fix: expired refresh tokens must redirect to /login, not 500.
Verify with: pnpm test:run auth-refresh-expired-token

Implement, run the command, and preserve the output. A non-implementer reviews the final diff and output in the project's native PR, CI, or conversation surface. Do not manufacture a file to prove a process happened.

Spec-governed work

example.txt

file
intent -> spec -> implement -> review -> check -> findings
  1. Spec: sus-spec writes intent and requirements with stable IDs and Verify with: lines. Set status: ready before dispatch or review.
  2. Implement: a native worker or human follows the spec by absolute path, runs every verification, and records real output under ## Execution.
  3. Review: a non-implementer judges the result on the native PR, via Revolver, Triple-check, or Bulletproof. No Suspec review file.
  4. Check: use suspec check when deterministic coverage of a spec, task, change plan, or campaign pays for itself.
  5. Findings: discard transient observations; route verified durable lessons through memory or project records.

Every step has a by-hand path. The implementer may not call self-review independent. Work that earns independent review stays blocked until a non-implementer can judge it. The CLI backs the method; it never gets custody of it.

Escalation

Escalate only when the signal earns the rigor.

A task narrows a source spec; it never adds requirements. A change plan adds transformation order and preservation context; it never replaces the spec. drill locks one seam; it never writes type: change-plan.

Proof, not claims

  • Preserve fresh output for every verification claim.
  • Treat empty evidence as unverified, never as proof.
  • Expose blocked and unverified work.
  • Keep acceptance human-owned. The implementer cannot accept.

Next: artifact location and close. Previous: what Suspec is.

Need a starting point? Install the skills