From silver-bullet
Generates a project-level session handoff prompt summarizing state, milestone, docs, constraints, and verification status for resuming work later.
How this skill is triggered — by the user, by Claude, or both
Slash command
/silver-bullet:silver-handoff [optional focus area or 'include task details'][optional focus area or 'include task details']The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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").
$PWD until you find .silver-bullet.json or .git.$PWD as root.If any value is unavailable, include unknown rather than guessing.
Gather high-level status from available sources (in this order):
.planning/STATE.md — current phase/plan/progress markers.planning/ROADMAP.md — active milestone name and phase sequenceREADME.md — project purpose when planning artifacts are absentSummarize in 2-4 bullets:
none detected)Build a short prioritized list (3-6 paths max) from existing files, preferring:
README.mddocs/ARCHITECTURE.mddocs/TESTING.mddocs/CHANGELOG.mddocs/knowledge/INDEX.mddocs/knowledge/YYYY-MM*.md, docs/learnings/YYYY-MM*.md)docs/doc-scheme.md (if docs governance matters)Only include files that actually exist.
Collect stable constraints from project docs and planning artifacts:
Keep this section compact (3-8 bullets). Prefer durable rules over transient implementation notes.
Summarize recent quality/release state from what is available:
If no evidence is available, explicitly state verification status unknown.
Gather open work from whichever sources exist:
docs/issues/ISSUES.md and docs/issues/BACKLOG.mdReturn a short actionable list with stable references (issue numbers, file paths, or phase IDs).
Output exactly one reusable handoff prompt in Markdown.
Use this structure:
Project IdentityCurrent Goal and MilestoneRead FirstConstraints and InvariantsVerification and Release StateOpen Follow-upsFirst 3 Actions for Next SessionStyle requirements:
Only when user explicitly requests task-level detail, append:
When not requested, keep handoff project-level.
npx claudepluginhub alo-exp/silver-bullet --plugin silver-bulletGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.