memory-onboardlisted

# /memory-onboard — repo-aware onboarding for memory This skill is **the** way to seed a repo with lore. It earns its keep by **reading the repo first** (README, ADRs, recent commits, deprecation markers, in-flight migrations) so the proposed drafts are specific to *this* codebase, with source citations — rather than inventing memory or mechanically chunking every bullet in the docs (which produces mostly noise and floods the review queue). Output: DRAFT records with source citations, plus optional absence markers and boundary edges. Everything lands in `memory review` for a human to ratify — the skill never promotes its own records. ## Hard rules 1. **Every lore record this skill produces is a DRAFT.** Call `suggest_lore` (or `report_conflict` for counter-claims — also drafts), never any approval path. The human reviews with `memory review`. Exception: `record_absence` does NOT create a draft — it records a self-expiring "we checked, no policy" marker. Different primitive, different gate (see rule 6). 2. **Every draft carries the tag `induction`** so it can be filtered later. Layer topic-specific extras as appropriate (`security`, `conventions`, `migrations`, `incident-lessons`, `invariants`, etc.). `report_conflict` counter-drafts are auto-tagged `conflict-report` by the server. 3. **Cite sources in the body.** When a draft comes from a file or commit, include a one-line reference at the top of the `body` — e.g. `Source: README.md L42–55` o