aoi-bootstrap

AOI Bootstrap

Bootstrap AOI through a gated workflow:

inspect -> draft -> validate -> preview -> approve -> apply -> doctor

Keep the target repository unchanged during inspection, drafting, validation, and preview. A candidate may be written only to an external scratch path. Never apply it until the user explicitly approves the exact candidate SHA-256.

1. Inspect

Confirm that the requested root is the exact root of an existing Git worktree. Read the repository's AGENTS.md, README.md, current runbooks, and existing aoi.toml when present. Then run:

python <skill-directory>/scripts/inspect_project.py --root <repository-root>

Treat the JSON as inventory, not as authority. It intentionally does not read source contents or infer the organization.

Treat truncated, filesystem errors, linked entries, an unreadable/invalid state marker, or git.tracked_changes_checked = false as incomplete evidence. The bounded inspector intentionally does not run a full-worktree git status. Resolve the affected boundary or present it as an explicit unknown before drafting.

Stop without writing when any of these are true:

• the path is not the exact Git worktree root;
• the root or candidate configuration is a symlink or junction;
• aoi.toml already exists and the user has not explicitly requested a review or interrupted-initialization recovery;
• AOI state already exists without the same valid installed profile, is linked, or records a different Windows/WSL lock domain;
• the user's goal, risk tolerance, or project boundary is materially unclear.

2. Draft

Read profile-schema.md and organization-heuristics.md. Combine:

• the user's stated goal and constraints;
• repository evidence from inspection and current docs;
• the smallest useful set of stable specialist lanes;
• model-agnostic capability tiers and evidence gates.

Write a candidate TOML to a scratch path outside the target repository. Keep hooks.codex.enabled = false and legacy.enabled = false unless the user explicitly requests otherwise. Do not create agents or tasks during bootstrap. If state_dir is customized, require that path to be absent or empty and include the exact directory prefix in policy.high_risk_paths.