← ClaudeAtlas

silverhandofflisted

This skill should be used when ending a session and needing a reusable, project-level handoff prompt for the next session. It summarizes project state, active milestone, key docs, constraints, verification/release status, and open follow-ups without defaulting to task-specific detail unless explicitly requested.
alo-exp/silver-bullet · ★ 5 · AI & Automation · score 73
Install: claude install-skill alo-exp/silver-bullet
# /silver-handoff — Generate Project-Level Session Handoff Prompt Use this skill at session wrap-up when work will continue later on the same project. The output is a concise, reusable prompt that helps the next session resume safely without rereading the full repo. Default behavior is project-level. Include task-specific detail only if the user explicitly asks (for example: "include task details", "include current task", "include branch diff"). --- ## Step 1 — Locate project root and execution context 1. Walk up from `$PWD` until you find `.silver-bullet.json` or `.git`. 2. If both are absent, use `$PWD` as root. 3. Determine: - project/repo name - current branch (or detached HEAD) - clean/dirty working tree - origin URL if available If any value is unavailable, include `unknown` rather than guessing. --- ## Step 2 — Capture project goal and milestone status Gather high-level status from available sources (in this order): 1. `.planning/STATE.md` — current phase/plan/progress markers 2. `.planning/ROADMAP.md` — active milestone name and phase sequence 3. `README.md` — project purpose when planning artifacts are absent Summarize in 2-4 bullets: - current project goal - active milestone/phase (or `none detected`) - current execution posture (active, paused, release-prep, etc.) --- ## Step 3 — Identify "read first" documents Build a short prioritized list (3-6 paths max) from existing files, preferring: 1. `README.md` 2. `docs/ARCHITECTURE.md` 3. `docs/TESTING.md`