manual page/ Reference

Cheatsheet

sourceSource: suspec/docs/reference/cheatsheet.mdModified: 2026-08-19

Use the skill the work needs.

Spec-governed path:

example.txt

file

intent -> spec -> implement -> review -> check -> findings

Use the least structure that changes execution or reviewability. Everything else is rent. See proportional rigor.

Artifacts

Kind	Carries
spec	intent and verifiable requirements
task	one scoped source slice
inventory	observed structure, behavior, tests, constraints, unknowns
change plan	baseline, target, preservation, waves, rollback
audit	evidenced present-state risks
research	evidence for one decision-informing question
campaign	one restartable multi-pull-request goal
panel	independent alternatives and one recommendation

drill is a universal method, not an artifact. Evidence receipts and run notes are untyped sidecars. Findings are not a type. Independent review lives on the native PR. Exact shapes: artifact formats.

Requirement

example.md

file

### AC-001 - Short name
- When: one concrete condition holds
- Then: the system MUST do one observable thing
- Verify with: `command`

Use one condition, one behavior, exactly one binding word, one verification, and no unresolved uncertainty.

Review judgments

Judgment	Meaning
Supported	evidence demonstrates the requirement
Unsupported	evidence demonstrates failure
Unverified	evidence is missing or insufficient
Blocked	a dependency prevents judgment

A non-implementer records the verdict on the native PR. The implementer cannot accept. Reverify after requirement text, commands, or exercised code changes.

Evidence

Use pasted command output, a visible labeled CI URL, or a named manual observation. tests passed proves only that someone typed tests passed.

Review attention

Expose unsupported, unverified, or blocked requirements; scope drift; excluded-area edits; risky or public interfaces; migrations; security-sensitive changes; missing output; findings; and blocked questions.

Check

suspec check <artifact> [<artifact>...]
suspec check <task-path> --spec <spec-path>
suspec check --contract

Multi-path checks add C002 duplicate-ID reconciliation. Exit 0 is clean, 1 warning, and 2 blocking. Multi-report --json output is JSON Lines. The checker reports facts; humans decide.

Need a starting point? Install the skills