scope-initlisted

Create or refresh an agent-notepad — a per-objective working-memory git repo (one notepad per objective, grouped by name prefix) that survives context compaction and drives several code repos from one session. Runs a short interview (objective, code-repo paths, done-criteria), optionally `gh repo create`s the notepad under the prefix→org map (consent required), writes SCOPE.md + repos.manifest.json, validates each code repo, offers per-repo df-context-store bootstrap (consent), warm-starts NOTES.md from the repo stores, lays down the notepad template, and wires best-effort pull/push. Idempotent: re-running refreshes without clobbering NOTES.md or the journal. Use to start a new objective, spin up a notepad, "init a scope", or onboard an existing directory as a notepad. Triggers on "scope-init", "new notepad", "start a scope", "init working memory".
OneDro1d/dark-factory · ★ 0 · Data & Documents · score 70

Install: claude install-skill OneDro1d/dark-factory

# scope-init — stand up (or refresh) an agent-notepad A **notepad** is one standalone git repo per objective, named `<group>-<objective>` (e.g. `proj-arbbot`). The **group is the prefix** — the substring before the first hyphen (`proj-basket-tokens` → group `proj`). Code lives in *separate* repos referenced by `repos.manifest.json` and driven via absolute paths, never by `cd`-ing. This skill creates that notepad or refreshes an existing one. See the design in [DESIGN.md](../agent-notepad/DESIGN.md) (§5 topology, §6 file contracts, §7 hooks, §8 cross-repo bridge). **Consent is load-bearing.** Two actions in this procedure touch the outside world and MUST NOT run without an explicit yes from the operator, each time: 1. Creating a GitHub repo (`gh repo create`). 2. Bootstrapping a df-context-store into a code repo you don't own the substrate of. Everything else is local file writes and read-only repo validation. **Idempotent.** On a re-run in an existing notepad: refresh SCOPE.md / manifest / CLAUDE.md and re-validate repos, but **never** clobber `NOTES.md` or any journal file — merge/append only. A second `scope-init` is a safe no-harm refresh. **A re-run is not a shorter run.** Steps 6 and 6a are per-REPO offers, and the repo set moves: a repo added to the manifest last month was never offered anything, because it did not exist when the offers were made. So a re-run walks **every** repo in the manifest, not only the ones this run created. ⚠️ **First init is the one moment