Cheatsheet

Loop

Pull -> (Inventory) -> Spec -> (Change Plan) -> Task -> Run -> Review -> Close

Files

Requirement

### AC-001 - Short name

The system must do one observable thing.

Verify with: `command`

Rules:

• one behavior
• one binding word
• one verify line
• uncertainty goes to Open questions

Results

Four core results:

Empty evidence means Unverified.

Three lifecycle markers (decorate a prior result, never a core value — advanced lifecycle):

Merge gate: every in-scope requirement is Pass or a live Waived, and none is Stale, Contradicted, Fail, Blocked, or Unverified. An empty scope does not pass.

Evidence

Valid:

• pasted command output
• CI link
• named manual observation

Invalid:

• tests passed
• worker summary alone
• unsupported screenshot

Review triggers

Route to Human attention:

• Fail, Unverified, Blocked
• out-of-scope edits
• Do not change touched
• risky files
• public interface changes
• migrations
• security-sensitive changes
• missing test output
• candidate findings
• blocked questions

Core checks

See checks.

Workspace names

Dedicated workspace repo:

<project>-works

Code repo pointer:

Suspec workspace: ../<project>-works. Read the task packet before coding.

CLI

Common commands:

suspec init
suspec update --check
suspec check
suspec new spec <slug>
suspec new task --from SPEC-id --scope AC-001
suspec worktree create TASK-id
suspec run TASK-id --agent codex
suspec review TASK-id
suspec status

CLI prepares and reconciles. It does not write code or decide correctness.