Plans and project routines
Start with a conversation. Add a plan when work needs acceptance criteria, owners or verification. Ordinary SpecWithCode chat does not require a SpecWeave increment or CLI installation.
These features have been in every SpecWithCode build since 0.2.0. SpecWithCode is free for every developer and team (what stays free) and in early access (download for macOS, Windows or Linux); each machine that runs work needs the current version installed. See SpecWithCode projects for availability.
One plan authority
Open Plan → Add a plan to keep a short specification, acceptance criteria and tasks in SpecWithCode. Each task can record an owner and a verification command. Saving a command does not execute it. Reported completion is separate from a verified result.
| Task state | What it records |
|---|---|
| Planned | The work has been defined. |
| In progress | Work is underway. |
| Blocked | A dependency or decision prevents progress. |
| Reported done | Someone reports completion; verification remains separate. |
| Verified | The saved verification command actually completed successfully. |
Verification is an explicit human action that executes the saved command on the project host. Review the command and arguments before running it. A timeout, error or nonzero exit does not pass. Changing the task definition invalidates its current verified status while retaining historical evidence. A resolved chat alone does not change that evidence.
Expand Verification command and evidence to review the executable, literal arguments, workspace and timeout. Run verification needs both terminal and orchestration operation permission. This executes a local command with the host's permissions; it is not a sandbox.
If the response is uncertain, Recheck last request looks for the same receipt without starting another process. New verification attempt deliberately starts a separate execution. Receipts retain their command, outcome, exit code and bounded output even after the current command changes or is removed. Ask coordinator sends the saved task through the project conversation; it cannot grant verification permission.
If the project already uses SpecWeave, connect the existing increment as the authority. SpecWithCode's optional adapter reads its spec.md and ledger.jsonl; it does not install the CLI, claim tasks, invoke pickup or maintain a competing editable ledger. An external done entry remains externally reported evidence. Missing or invalid files produce an error rather than silently switching authorities. A native plan can be exported as Markdown; native session histories and caches are not part of that export.
Use Plan source to select or repair the binding. The increment folder must remain inside the registered project folder; register the umbrella folder when the increment belongs above a child repository. A broken source keeps its binding visible for repair and never silently becomes an empty native plan.
For work outside SpecWithCode, the SpecWeave CLI provides its own daily loop and explicit handoff. A thread and an increment are different units: one increment may involve several workers, and a worker may receive several related follow-ups.
Schedule work in the right project
Open Settings → Routines → Manage routines. Confirm the selected project and host before saving a schedule. A routine either continues its bound thread or starts a new thread, according to its configuration. An enabled schedule is not a completed task.
The project view lists its routines, next run, last error, Run now and pause controls. Project pause or archive blocks new routine runs, including manual runs. The host running the schedule must be available; SpecWithCode does not turn a local schedule into a cloud service when the computer sleeps.
A transport error may leave acceptance uncertain. Retry keeps the same request identity instead of blindly launching another run. If SpecWithCode reports an unknown outcome, inspect the previous thread first. Use I checked the previous run; start a new run only when you deliberately want a new attempt; the previous attempt may still be working.
Project deletion removes its routines. The optional usage-limit recovery setting arms supported native recovery for new stops; it does not switch accounts, enable paid overage or guarantee quota availability.
The separate SpecWeave CLI project hub stores routine definitions. Those definitions are not automatically active SpecWithCode schedules. Configure the actual schedule in the host that will execute it.
Video walkthroughs
Plan, verify and schedule
Narrated walkthrough with English captions and synthetic project data. On a phone, use fullscreen or the guide page for the dense desktop interface.
Steps and full transcript: Plan, verify and schedule