Doctor

Use doctor when local state looks wrong:

bgng doctor
bgng doctor --json

It reports:

• Broken symlinks
• Stale downstream skill links
• MCP drift between registry and generated config
• Missing generated config files
• Project config issues

It does not mutate local state.

Safety Model

The safety model is intentionally simple:

• Preview first with --dry-run
• Inspect machine state with status
• Diagnose drift with doctor
• Curate skills explicitly before applying them downstream
• Available, not exposed — package-backed bundles are available content, not automatically active behavior
• Report-only cleanup until a command explicitly supports repair or pruning

Usage Modes

Baseline CLI usage does not require external tools beyond Bun, Node.js, and npm.

Packaged harness

npm install -g beginning-harness
bgng apply --dry-run

Editable harness source

export AGENTS_REPO_ROOT=/path/to/beginning-harness
bgng status

In checkout mode, edit:

• config.json for target and optional-server toggles
• mcp-servers.json for MCP server definitions
• skills/ for built-in skill content

Optional Extensions

Optional extensions include:

• Beads — project issue tracking through bd
• Parallel — CLI-backed skills and optional MCP overlay
• Markdownify — optional local MCP dependency

Each can be enabled independently. See the Extensions page for setup details.