bootstraplisted

Adapt the feature-flow kit to THIS project — the front door for setting it up. Run on the FIRST install after dropping the kit into a project's .claude/ folder: detects the stack, writes the project profile (.claude/PROJECT.md), installs and reconciles stack rule packs against the real codebase, wires settings/hooks/commands, and writes the kit manifest. Backs up before writing and asks keep-or-rollback before cleaning up build-time files. On a project that's ALREADY adapted (profile_status: ACTIVE) it hands off to /update-kit instead of re-installing, so any later update or re-adapt goes through the safe staging + 3-way merge. Trigger when the user says "bootstrap", "adapt the kit", "set up .claude for this project", or when PROJECT.md is missing / still a TEMPLATE. DO NOT TRIGGER to remove or roll back the kit (that's /teardown). For a plain kit update or re-adapt you can go straight to /update-kit — running /bootstrap on an already-adapted (profile_status: ACTIVE) project is still safe: it detects that and
mik2win/foureyes · ★ 2 · AI & Automation · score 76

Install: claude install-skill mik2win/foureyes

# /bootstrap — adapt the kit to this project You turn the portable feature-flow kit into a project-specific `.claude/`. You are interactive: detect what you can, **ask the user about anything ambiguous or where rules diverge from the real code**, then generate the project layer. Read `_kit/KIT.md` and `_kit/rules-library/PACKS.md` once at the start — they define the kit and the pack format. Work top-to-bottom, naming each phase as you enter it — the phase headings below **are** the checklist, and none is optional. Do not skip or reorder: this run is interactive and long, and a run that loses its place re-asks the user questions they already answered. --- ## Phase 0 — Preconditions 1. **Dispatch on entry (this skill is the front door) — check this FIRST.** If `.claude/PROJECT.md` already exists with `profile_status: ACTIVE` **and** you were entered directly (the user ran `/bootstrap` — not `/update-kit` calling the reconcile phases 3–6), this is **not** a first install: the project is already adapted. **Hand off to `/update-kit`** and stop — it stages the new/current kit, 3-way merges so local adaptations survive, then re-adapts. Re-copying the kit over `.claude/` and re-installing would clobber local edits — never do that. (Re-adapting after structural changes also goes through `/update-kit`.) Check this *before* the kit-present precondition below, because an adapted project has already removed `_kit/` at cleanup. 2. Confirm the current directory is