bootstrap-projectlisted

One-command Codex project setup orchestrator. Detects the stack, then runs root AGENTS.md setup, scoped AGENTS.md placement, Codex permission/config review, automation proposals, CI setup, and optional Obsidian Vault creation with approval gates. Global and project-agnostic. Trigger when the user says "bootstrap project", "bootstrap-project", "set up this repo for Codex", "onboard this project", or "run the full project setup".
ada-ggf25/AI-Tools · ★ 2 · AI & Automation · score 66

Install: claude install-skill ada-ggf25/AI-Tools

# Bootstrap A Project For Codex Run the Codex-oriented new-repo setup workflow in one guided pass. This is a thin orchestrator: it owns sequencing and handoffs, and delegates detailed work to the focused skills. Sequence: `AGENTS.md` setup -> `where-agents-md` -> `setup-permissions` -> `propose-automation` -> `setup-ci` optional -> `obsidian-vault` optional -> durable memory suggestions. ## Operating Principles 1. Orchestrate, do not reimplement delegated skills. 2. Pause after each step and continue only after user approval. 3. Be idempotent: detect existing `AGENTS.md`, `.codex/`, `.agents/`, and repo config. 4. Prefer shared repo guidance only when it is useful to teammates; keep personal Codex config personal. ## Procedure ### 0. Orient - Confirm the working directory is the intended repo root. - Detect existing setup: root/nested `AGENTS.md`, `AGENTS.override.md`, `.codex/`, `.agents/`, `CLAUDE.md`, README, CI, and project manifests. - For a large repo, delegate broad exploration to a read-only subagent when available. - Show the planned sequence and let the user drop steps. ### 1. Root Codex Instructions - If no root `AGENTS.md` exists, propose creating one from observed repo facts. - If one exists, offer to review/update it instead of regenerating. - If `CLAUDE.md` exists, use it as source context but do not copy Claude-only commands, hook syntax, or permission syntax blindly. ### 2. Scoped Instruction Placement - Invoke `where-agents-md` to identify