New Repo Use

This is the path for a repo that does not have Jumpspace yet.

You do not need to memorize every command. The fastest workflow is to install Jumpspace, add agent guidance, then ask your agent for the outcome. The installed guidance tells the agent to use Jumpspace as the workflow spine.

The Goal

By the end of first setup, your repo should have:

• .jumpspace/config.json
• repo-local Codex or Claude guidance
• a small source-backed task graph
• scanned task metadata
• clean audit output
• a repeatable way for agents to ask for context before coding

Install

npm install -D jumpspace

If you are testing a local Jumpspace checkout before npm publishing, link it from the Jumpspace repo first:

npm run build
npm link

Then link it in the target repo:

npm link jumpspace
jumpspace release install-doctor --json

release install-doctor tells you whether the target repo is using the expected local build or an older global binary.

Initialize The Repo

npx jumpspace init --auto

init --auto detects common documentation locations and writes a starter config. Use plain jumpspace init only when you want the conservative default.

Add agent guidance:

npx jumpspace add-skill --codex
npx jumpspace add-skill --claude

These commands are additive. They create missing guidance files or update clearly marked Jumpspace-managed blocks.

Let An Agent Bootstrap

Ask your agent for the outcome:

Bootstrap this repo. Run discovery first, inspect the docs, propose a small source-backed task graph, and do not apply changes until I approve the proposal.

The agent should use commands like:

npx jumpspace bootstrap discover --json
npx jumpspace bootstrap context README.md docs/**/*.md documentation/**/*.md --json
npx jumpspace bootstrap propose README.md docs/**/*.md documentation/**/*.md --file jumpspace-bootstrap.json --json
npx jumpspace bootstrap validate --file jumpspace-bootstrap.json --json
npx jumpspace bootstrap apply --file jumpspace-bootstrap.json --dry-run --json

After you approve the dry run:

npx jumpspace bootstrap apply --file jumpspace-bootstrap.json --json
npx jumpspace scan
npx jumpspace audit --json

Keep The First Graph Small

The first graph should not index every heading. Prefer task blocks for:

• core product workflows
• architectural decisions
• important runbooks
• specs that are likely to drive code changes
• behavior with obvious code or test owners

If the agent is unsure, it should add a gaps entry instead of inventing links.

After Bootstrap

Once the first graph exists, use plain-English requests:

Find the task for task approvals, gather context, and tell me what files and tests matter before coding.

For implementation:

Create or review the plan for PM-TASK-001. Show me the plan before making changes. After I approve it, execute the next step and record evidence.

The agent can translate that into context, plan, next, work, step complete, verify, scan, and audit calls.

Day-Two Habit

When new work changes docs or code, ask the agent to keep Jumpspace current:

Check drift and link suggestions for this branch. Tell me what task blocks or code/test links need updating.

That usually maps to:

npx jumpspace changed --since main --json
npx jumpspace drift --since main --json
npx jumpspace link suggest PM-TASK-001 --since main --json
npx jumpspace audit --json