Quickstart

This walkthrough assumes Cadre is installed and the client has been reloaded. Cadre commands are agent skills, not cadre-ai shell subcommands.

Codex, Claude Code, and native Zed Agent support is stable. The commands below use each client's native skill integration.

1. Create Project Context

Open the target repository in Codex, Claude Code, or Zed Agent:

$cadre:create

Cadre inspects the repository, establishes its exact root and Git disposition, and explicitly classifies the project as greenfield or brownfield. When the evidence is ambiguous, it asks before drafting.

Review the proposed product, engineering guidelines, technology stack, workflow, styleguides, patterns, project state, and Git disposition in one final authorization envelope. Cadre identifies unchanged bundled defaults concisely and asks separately only when a material choice is unresolved. After approval, it creates .cadre/, validates it, and records one setup/receipt commit without more approval prompts.

2. Create A Feature Or Bug Track

$cadre:track Add passwordless login as a feature

Cadre proposes specification, plan, learning, dependency context and state together when the request is clear. One approval covers the validated graph, commit groups, inherited constraints, pattern seed, lifecycle transition, generated state and one receipt-bearing commit. Ask for staged specification/plan review explicitly when desired.

The plan is an acyclic dependency graph:

• each regular phase declares phase dependencies;
• each regular task declares same-phase task dependencies;
• every delivery phase ends with a derived User Manual Verification barrier;
• the final phase contains only track-level manual verification and depends on every delivery phase.

The track becomes planned only after the plan graph and pattern seed are approved, validated, and committed.

3. Check Status

$cadre:status

Status is read-only. It reports project and track checkpoints, pending operations, dependencies, execution nodes, review/archive readiness, validation errors, and managed worktrees.

4. Implement The Plan

$cadre:implement passwordless-login

Parallel mode is the default. Request sequential execution explicitly:

$cadre:implement passwordless-login sequentially

Track approval is the default: Cadre verifies phases automatically and pauses at track verification, then ordinary review approval. Request phase for phase verification gates, governed for task gates, or autonomous to implement, verify, review, and fix in-scope findings until clean, with one final completion approval. Parallel/Sequential scheduling remains independent. Phase, Track, and Autonomous do not add a start-approval prompt.

Cadre starts an execution journal under the requested approval mode, derives a global queue from ready phases and phase-local tasks, and creates workers only when at least two safe nodes can run. A phase can move between sequential execution and task fan-out only at a clean checkpoint. Workers use isolated Git worktrees; main reviews every diff and presents it according to the persisted approval mode.

The main agent alone records state, directs commits, integrates branches, resolves conflicts, removes worktrees, and records manual verification. When all nodes, learning, provenance, and cleanup are complete, an approved finish transition moves the track to ready_for_review.

5. Review

$cadre:review passwordless-login

Review inspects the recorded implementation range and relevant context. If it finds actionable bugs, it presents the findings together with exact bug and remediation-plan artifacts. Approved remediation returns the track to implementation.

When evidence is clean, Cadre previews completion bound to the current execution, plan revision, graph digest and reviewed HEAD. Outside Autonomous mode, the human may explicitly reject findings and record accepted risks. Autonomous requires all findings resolved. Every mode requires explicit approval of the exact completion proposal; only review can mark the track completed.

6. Archive Completed Work

$cadre:archive passwordless-login

Archive can process one or more completed tracks in a single approved, resumable batch. It moves track history to the derived archive location, distills durable learning into project patterns, reseeds relevant active tracks, rebuilds tracks.md, and records Git provenance.

Supporting Commands

• Use revise when the approved desired behavior, scope, or plan changes.
• Use refresh when project product, workflow, stack, styleguides, or patterns drift from repository evidence or user intent.
• Use revert to prepare an additive Git-aware reversal.
• Use wisp for lightweight exploration that should not mutate Cadre state.

Continue with How Cadre Works or the complete Workflow Guide.