Skip to main content

Plan, verify and schedule project work

You add a plan with one acceptance criterion, see a failed verification stay failed, record a passing attempt, and keep routines scoped to their project.

  • SpecWithCode
  • 1:35
  • Any agent
  • Captioned, no sound

Recorded on SpecWithCode 0.2.0, added 9 October 2026. The current release is SpecWithCode 1.0.44.

Before you start: SpecWithCode installed; A project open.

Length 1:35Captions

Steps

  1. Add a plan when acceptance needs evidence: a short spec, one acceptance criterion and a task. Ordinary chat does not need one.
  2. Review the executable and its literal arguments before saving the verification command. Saving does not run it.
  3. Run verification. A nonzero exit stays failed, and that receipt is kept unchanged.
  4. Fix the cause, then choose a new attempt. The new receipt records the successful exit; Recheck reads the same receipt without running it again.
  5. If the repository already has a SpecWeave ledger, it stays authoritative.
  6. Routines keep their project and host. Pause the project to refuse new work; a turn already running is not killed.
  7. Deleting a project needs its exact name and leaves its source folder intact.

Transcript

Built from the on-screen captions of this silent video.

0:00 Add a plan

Add a plan when acceptance needs evidence. Ordinary chat does not require the CLI. Write a short spec, one acceptance criterion and a task.

0:14 Save a verification command

Review the executable and literal arguments. Saving the command does not run it.

0:22 A failed run stays failed

Verification runs a real local process. A nonzero exit remains failed. We now create ready.txt in the synthetic source folder. The previous failed receipt stays unchanged.

0:36 A new attempt passes

Choose a new attempt deliberately. The new receipt records the successful exit. Recheck reads the same receipt. It cannot launch that verification again.

0:51 The specweave ledger stays authoritative

An existing SpecWeave ledger stays authoritative. Its done entry remains external, unverified evidence.

0:58 Routines and pausing

Routines keep their project and host scope. This demonstration routine is disabled. Pause the project to refuse new work. It does not kill an already running turn. New routine runs remain blocked while the project is paused.

1:20 Delete a project safely

Deletion requires the exact project name. This is a disposable synthetic project. Deleting project history leaves its source folder intact.

Read the plans guide

Learning path

Run SpecWithCode

Understand the setup, run a project through its coordinator, then add plans, memory and a second provider.

  1. See how SpecWithCode runs your agents

    2:54, SpecWithCode

  2. Run a project with a coordinator and workers

    1:29, SpecWithCode

  3. Plan, verify and schedule project work (this guide)

    1:35, SpecWithCode

  4. Keep project memory and read honest usage

    1:06, SpecWithCode

  5. Continue a thread on Codex at a usage limit

    1:01, SpecWithCode

5 more guides are planned for this path.

All tutorials