v2.3.x solo-first workflow

Start fast with KB, keep docs grounded to real code changes.

This landing focuses on what is executable now: initialize, bootstrap, scan, and move with the next best action. Team-scale and ecosystem features stay explicitly marked as future direction.

Start in 5 minutes Use kb next Need help?

What ships now

Solo core runtime is ready now: init, bootstrap, index, scan, verify, baseline, doctor, and kb next.

How to work daily

Use kb next to prioritize action in order: drift unresolved, review backlog, missing docs, then source mirror gaps.

Future direction, clearly gated

Cross-project registry, multi-agent orchestration, and ecosystem contract runtime are intentionally deferred, not claimed as current runtime.

Quick start

5-minute bootstrap

Run this in your target repository. This path is optimized for fast understanding and immediate execution. Full setup guide →

Step 1-2

Initialize and scaffold basic docs from source signals.

Terminal

cd <your-repo>
npx @williamduong/kb@latest init --yes
kb bootstrap --dry-run
kb bootstrap

Step 3-4

Build index, then let kb next tell you what to do next.

Terminal

kb index
kb next

# Optional for tool integration
kb next --json

Action center

Use kb next as daily navigator

The output is designed to be actionable and copy/paste friendly: run suggestion, rerun kb next, repeat.

Expected behavior

Priority orderdrift unresolved → review backlog → missing docs → source mirror coverage
Command looprun suggested command, then rerun kb next to move queue forward
Machine-readableuse kb next --json for scripts and automation hooks

CLI commands catalog Manual test catalog

Companion commands

kb scan --recursive --depth=2 Make drift explicit with impact evidence.

kb verify <doc> Close resolved review items with verification stamp.

kb doctor --strict Use as release-readiness gate for current workspace state.

Troubleshooting

If you get stuck, start here

Run diagnostics first, then follow docs by symptom. This reduces random trial-and-error.

First-response checklist

Terminal

kb doctor
kb status
kb help --advanced
kb next

If KB state looks partial or corrupted, use the documented recovery path before re-running init.

Where to find answers

How-to-use guide Revision state and drift baseline Metadata schema Review backlog source of truth

Direction

Now, next, later

Current runtime is optimized for solo execution and explicit downstream maintenance. Future phases remain explicit and deferred until command surface is shipped.

Now (v2.4.x reality)

Solo core plus supported Phase-2 subset: strict doctor gate, release notes/catalog, chaos score with cognitive drift signals (v2.3.3), intent workspace workflow, agent governance gates, v2.3.5 stabilization, and v2.4 intent schema maintenance: kb intent cleanup audits missing focus or wave metadata, while kb migrate --to=v2.4.0 upgrades legacy intent frontmatter on active/closed intents, removes renamed original fields after mapping to legacy_*, and keeps archive intents marker-only.

Next (when shipped)

PR gate integration and stronger team workflow controls become runtime features once command path is stable and testable.

Later (deferred)

Cross-project registry, multi-agent orchestrator, and ecosystem-level contract gating stay deferred and should be treated as design review only.