intakelisted

Route a new rule, preference or policy edit into every home it belongs in (always-loaded canon, memory, the behavioral codex, a skill, a hook) and leave a trace in the always-loaded layer so parallel sessions pick it up on their own. Flow: dedup recall, classify by form, write to all homes, back up, report. Triggers: "/intake", "record this rule", "route this to its homes".
tonydzi/second-brain-starter-kit · ★ 6 · AI & Automation · score 78

Install: claude install-skill tonydzi/second-brain-starter-kit

# /intake — the rule intake (route it to its homes, don't just write it down) > 🧒 **When reporting to a non-technical owner:** end with a child-simple "In plain words" recap (memory `eli5-always`). Reports TO him only — never inside vault notes. **Why (canon: memory `rules-intake-channel`).** This chat is the dedicated channel where the owner drops ALL rules/policies/Bible entries/skills/`CLAUDE.md` edits/preferences, so that working chats stay clean. My job is **not just to write it down, but to DELIVER** the rule to all of its homes, cross-link it, and leave a trace in the always-loaded layer, so that automatic/parallel processes see it on their next start. This skill = the same manual flow I repeated ~10× in one session, folded into a single command. **Architecture (skill-design-three-layer):** a thin `SKILL.md` orchestrator + deterministic steps (backup/commit/grep) + an external store (CLAUDE.md, memory, the vault). The routing decision **is still shown to the owner** in the report — the skill does not hide the logic, it executes it without asking at every step. --- ## Step 0 — RECALL (dedup; cheap, ~0 tokens). NEVER spawn a duplicate Before writing — check whether such a rule already exists (update it, don't spawn a copy; resolve conflicts by "newer beats older"): - `MEMORY.md` is already in context — scan its index by topic. - `grep` over memory: `$USERPROFILE/.claude/projects/<project>/memory/`. - `grep` over the Bible/vault: `reglament-*` / `protocol-*` under `