Planning And Verification
Jumpspace separates implementation progress from verification.
A plan says what should happen next. A step completion records evidence that a step happened. Verification records prove that checks passed against acceptance criteria.
Durable Plans
Section titled “Durable Plans”Review a plan:
npx jumpspace plan review DOC-EXAMPLE-001 --jsonnpx jumpspace plan show DOC-EXAMPLE-001Save a plan:
npx jumpspace plan save DOC-EXAMPLE-001 --file plan.yml --jsonValidate it:
npx jumpspace plan validate DOC-EXAMPLE-001 --jsonPlan validation enforces unique step IDs, valid dependencies, acyclic dependencies, and evidence requirements for completed steps.
Next Steps
Section titled “Next Steps”npx jumpspace next DOC-EXAMPLE-001 --jsonnext only returns pending, unblocked steps. A blocked dependency means the step is not ready.
Step Completion
Section titled “Step Completion”npx jumpspace step complete DOC-EXAMPLE-001 implementation --evidence "Added approval service and tests."A step cannot be completed while dependencies are incomplete, and completed steps must have evidence.
Status
Section titled “Status”npx jumpspace status DOC-EXAMPLE-001 implementedverified is protected. This is rejected:
npx jumpspace status DOC-EXAMPLE-001 verifiedUse verify instead.
Verification
Section titled “Verification”npx jumpspace verify DOC-EXAMPLE-001 --check "npm test" --criteria AC-1 --evidence "Focused tests passed." --jsonVerification runs checks itself and records:
- verification ID
- timestamp
- commit SHA
- command text
- exit codes
- acceptance criteria covered
- evidence text
Failed checks do not write a verification record and do not set the task to verified.
Agent Start Packet
Section titled “Agent Start Packet”Use work when an agent should begin implementation:
npx jumpspace work DOC-EXAMPLE-001 --jsonnpx jumpspace work DOC-EXAMPLE-001 --since main --jsonWith --since, the packet also includes drift facts and warnings.