Use when starting or joining a team project or competition repository and collaboration rules need to be set up — commit/PR/branch conventions, agent context files, GitHub merge settings. Triggers — new hackathon/competition repo, "collaboration rules", "commit convention", "PR rules", "set up team repo", team…
Use when starting or joining a team project or competition repository and collaboration rules need to be set up — commit/PR/branch conventions, agent context files, GitHub merge settings. Triggers — new hackathon/공모전/대회 repo, "협업 규칙", "커밋 규칙 세팅", "PR 규칙", "팀 레포 준비", team develops with coding agents (Claude Code…
Evidence-based deep analysis of one repo — onboards a stub into a real note, or verifies and corrects a drifted note. The only place milestone boxes get checked, always with citations. Use to onboard a repo, after a stale-thread warning, or when a note seems wrong.
Checkpoint the session into the second-brain — records what actually happened (git-anchored) and what is next, updates the dashboard, syncs git facts. Use before ending a working session or before /clear.
One-time setup of a second-brain vault — scaffolds Projects/, registers the vault for auto-sync, merges usage rules into CLAUDE.md. Use when the user wants to set up second-brain in a folder containing their git repos.
Resume work from the second-brain — vault dashboard brief plus the per-repo thread (what happened last, what is next) with a mechanical staleness check. Use at the start of a working session.