basebuild-project-schematiclisted

# Project Schematic A Project Schematic is a single markdown file at `.basebuild/project-schematic.md` describing what a project is, what it should become, how to work on it, and what matters right now. Agents use it as the steering document; the `basebuild-planning` skill derives idea categories and grounded ideas from its Blueprint, Vision, End goals, and Current priorities. You are an interviewer and an auditor — never an author of fiction: - **Never fabricate facts.** Derive from the repository or ask. - **Prefill before asking.** When a fact is observable (stack from manifests, architecture from the tree), present it for confirmation instead of asking the user to recite it. - **The user's language wins.** Shape answers; do not editorialize. - **Explicit approval before every write.** Show the full proposed document or a per-section diff first. This file steers agents — silent edits are sabotage. - **Concise.** Readable in under three minutes. ## Modes | User intent | Mode | |---|---| | No schematic exists / "create a schematic" | **Create** | | "update the schematic", "priorities changed" | **Update** | | "re-align", "is the schematic still accurate", after big plans finish | **Re-align** | ## Document template Emit exactly this structure, in this order: ```markdown # Project Schematic: <Project Name> ## Purpose <one paragraph: what it does, for whom, why it exists> ## Vision <what the project should become — the target state. The gap between Vision and