Canonical Demo

This demo uses real commands and a generic project-management example. Replace paths and task IDs with ones from your repo.

1. A Repo Has Markdown Docs

Start with docs such as README.md, docs/product.md, or docs/architecture.md.

2. Initialize Jumpspace

npm install -D @jumpspace/cli
npx @jumpspace/cli init --auto
npx @jumpspace/cli add-skill --all

3. Bootstrap Source-Backed Task Blocks

npx @jumpspace/cli task bootstrap propose README.md docs/**/*.md --file jumpspace-bootstrap.json
npx @jumpspace/cli task bootstrap validate --file jumpspace-bootstrap.json
npx @jumpspace/cli task bootstrap apply --file jumpspace-bootstrap.json --dry-run

Review the proposal, then apply:

npx @jumpspace/cli task bootstrap apply --file jumpspace-bootstrap.json
npx @jumpspace/cli task scan

4. Ask Where A Behavior Is Implemented

npx @jumpspace/cli task ask "Where are project invites implemented?" --json

Treat the response as evidence. Inspect task IDs, paths, match reasons, linked code/tests, coverage, and unanswered terms.

5. Start Agent Work From A Task Packet

npx @jumpspace/cli task work DOC-PROJECT-001 --json

The agent should inspect the packet before editing code.

6. Complete A Plan Step

npx @jumpspace/cli task step complete DOC-PROJECT-001 design --evidence "Human approved the implementation plan."

7. Verify Work

npx @jumpspace/cli task verify DOC-PROJECT-001 --check "npm test" --criteria AC-1 --evidence "Focused tests passed."

verified is earned only when checks pass.

8. Detect Drift During PR Review

npx @jumpspace/cli changed --since main --json
npx @jumpspace/cli task drift --since main --json
npx @jumpspace/cli task pr comment --since main

The PR comment is review-only text; it does not post to GitHub.

9. Hand Off To The Next Agent

npx @jumpspace/cli task handoff --task DOC-PROJECT-001 --json

The next agent can resume from repo-local implementation memory instead of private chat history.