adapt-to-project

# Skill: adapt-to-project > **Status:** v1. Class-1 substitution shells out to the CLI; classes > 2–4 are LLM-judgment writes the skill performs directly under the > per-scope path-jail. ## When to invoke Invoke this skill **inside an adopter's repository** after they have installed one or more packs (the install verb writes `.adapt-install-marker.toml` at the install's scope root; the session-start hook surfaces the nudge on the next session open). Re-invoke any time: - A new pack is installed at either scope. - An adopter sees the session-start nudge naming a pack pending adaptation. - Companion files (`*.upstream.*`) appear on disk at either scope. - The adopter asks "adapt this template to my project". Idempotent on re-invocation: when every pack-declared marker is in the repo-scope `[markers]` table, every companion has been resolved, every finding is recorded in either `[[findings.accepted]]` or `[[findings.declined]]` at the scope it was observed in, and both scopes' `.adapt-install-marker.toml` files are absent, the skill emits zero filesystem diff and no new proposals. ## Pre-flight Before any proposal, read **both** scopes' state files and surface divergence: 1. **State files.** Read `<repo>/.agentbundle-state.toml` (if present) and `~/.agentbundle/state.toml` (if present). These carry `schema-version = "0.2"` and an explicit `scope` column. If either file declares `schema-version = "0.1"`, emit one stderr-style message naming `agentbundle i...