Bootstrap — minimal project setup

Bootstrap — minimal project setup

Bootstrap fills only explicitly requested, missing AgentOps entry documents and, when requested, the durable verdict directory. It does not initialize Git, install hooks, create tracker state, start runtimes, or impose a delivery workflow.

Never-overwrite is what makes bootstrap safe to run on any repository: a setup step that can only add is idempotent by construction, while one that can replace must first prove it understands what it is replacing.

Named failure mode — scaffold sprawl: creating files the caller never requested because a "complete" setup feels more helpful than a minimal one.

Anti-pattern: inferring product intent from directory names and READMEs to avoid asking the caller. Corrective: ask for the missing content; a wrong PRODUCT.md written confidently is worse than a question.

Prompt

Bootstrap missing AgentOps docs for fleet-router (ao is installed). Create only PRODUCT.md and GOALS.md since they're missing; AGENTS.md already exists, so leave it untouched. Also create .agents/ao/verdicts/sha256/. Report created, skipped, and failed paths.

It's working if

• The report lists PRODUCT.md and GOALS.md as created and AGENTS.md as skipped because it already exists.
• A path collision with an existing document, e.g. AGENTS.md already present, gets reported as skipped rather than overwritten.
• .agents/ao/verdicts/sha256/ gets created only when the caller explicitly requested durable verdict storage.
• The report ends with created, skipped, and failed paths only, carrying no next action and no git command.

Procedure

1. Inspect the target directory and report which canonical files already exist.
2. Ask the caller for missing product intent or goal content when it cannot be inferred safely.
3. Create only missing, explicitly requested files. Never overwrite an existing document.
4. Create .agents/ao/verdicts/sha256/ when durable local verdict storage is requested.