Reference

Commands and configuration.

Everything runs through Bun from the repository root. AGENTS.md in your project is the authoritative operating map.

Wizard flags

FlagEffect
--name / --display / --dir / --ownerAnswer the first questions up front
--public / --privateRepository visibility (default private)
--no-github / --no-drive / --no-review-appSkip the repository, the drive or the review gate
--no-runCreate everything but do not start the app
--yesAccept every default (never makes code public)
--dry-runShow every step; change nothing

Everyday commands

CommandWhat it does
bun slot:upStart the shared Postgres and Redis and this checkout's own databases; worktrees and clones each get their own slot
bun devRun the web app and realtime service
bun checkFormat, lint, boundaries, policy, dead code, duplication, invariants, evidence, types, tests, coverage floors, build
bun test:integrationDatabase, Redis and web tests against real services
bun test:e2ePlaywright against the production build
bun verifycheck + integration + browser tests + migrations applied twice
bun db:generateGenerate a forward migration from the schema
bun doctorDiagnose tools, services, identity and configuration

Agent and drive commands

CommandWhat it does
bun drive:bootstrap [--check] [--dry-run] [--github]Create or repair the PageSpace drive; idempotent; --check verifies every page and the agent key
bun plan:review <id> [--runner codex|claude|opencode] [--model m]Independent read-only plan review
bun board:read|status|create|relate|replaceHash-checked board edits
bun board:staleTasks whose status disagrees with git
bun decision:record "<decision>" --context <page> --why "…"Record a decision made on the owner's behalf
bun adr:nextThe next free decision-record number
bun review:check <recordId> --pr NSelf-check a review record before posting
bun github:review-appCreate and install the review-record GitHub App (two clicks)
bun github:rules [--apply]Diff or apply the repository's merge rules

project.config.json

The one place for non-secret project identity and drive layout; scripts read every id from it, and secrets stay in .env and GitHub.

{
  "name": "widget-app",
  "displayName": "Widget App",
  "repo": "you/widget-app",
  "gates": { "integrationCommand": "bun test:integration", "requiredChecks": ["CI gate", "Playwright E2E"] },
  "planReview": { "runner": "claude" },
  "pagespace": { "driveId": "…", "pages": { "roadmap": "…", "reviews": "…" }, "channels": { "epicUpdates": "…" } }
}

Your drive

PageHolds
RoadmapEpic → Phase → Leaf tasks with criteria and prerequisites
IssuesBugs, Test coverage, Agent tooling, Doc drift, User feedback, Backlog, Pending decisions
Plans / Prompts / ReviewsOne folder per epic: plans, handoffs, delivery logs, agent prompts, review records
LibraryBuilder and Reviewer contracts, the orchestrator loop, reusable skills
ChannelsStandup, Sprint Room, Epic Updates, Incidents (CI posts here)
AgentsScrum Master, Builder, Reviewer, Documentation Agent, Agent Memory
Running two projects on one machine? Each project's Docker stack, database names and ports are its own; set the <APP>_*_PORT variables when defaults collide.