Skip to content
Back to skills

917 Resume Checklist Bd64d36b

ASecurity

Follow this checklist when resuming work from a handoff document to ensure zero-ambiguity continuation.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
code-qualitygobashgit

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 917-resume-checklist_bd64d36b --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 917 Resume Checklist Bd64d36b?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 917 Resume Checklist Bd64d36b
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-917-resume-checklist-bd64d36b/badge)](https://www.skillsdirectory.com/skills/tools-only-917-resume-checklist-bd64d36b)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Resume Checklist

Follow this checklist when resuming work from a handoff document to ensure zero-ambiguity continuation.

## Pre-Resume Verification

- [ ] Read the entire handoff document before taking any action
- [ ] Verify you are in the correct project directory
- [ ] Confirm the git branch matches (or understand why it might differ)
- [ ] Check the handoff timestamp - how stale is this context?

## Context Validation

- [ ] Review "Important Context" section thoroughly
- [ ] Understand all assumptions listed - are they still valid?
- [ ] Check if any blockers have been resolved since handoff
- [ ] Review "Potential Gotchas" to avoid known pitfalls

## State Verification

- [ ] Run `git status` to see current file state
- [ ] Compare modified files list in handoff vs current state
- [ ] Check if any environment variables need to be set
- [ ] Verify any required services/processes are running

## Resume Execution

- [ ] Start with "Immediate Next Steps" item #1
- [ ] Reference "Files Modified" table for context on recent changes
- [ ] Apply patterns documented in "Key Patterns Discovered"
- [ ] Follow architectural insights from "Architecture Overview"

## During Work

- [ ] Update handoff document if major new context is discovered
- [ ] Mark completed items in "Pending Work" as you finish them
- [ ] Add new blockers/questions as they arise
- [ ] Consider creating a new handoff if session becomes long

## Red Flags - Stop and Verify

If you encounter any of these, pause and verify context before proceeding:

1. **Files mentioned in handoff don't exist** - codebase may have changed significantly
2. **Branch has diverged substantially** - check git log for recent commits
3. **Assumptions are clearly invalid** - reassess the approach
4. **Blockers marked as unresolved are now blocking you** - escalate to user
5. **Architecture has changed** - re-explore before continuing

## Quick Start Commands

After reading the handoff, these commands help verify state:

```bash
# Check current branch and status
git branch --show-current
git status

# See recent commits (compare with handoff)
git log --oneline -10

# Check for any running processes mentioned
ps aux | grep [process-name]

# Verify environment
env | grep [relevant-var]
```

## Handoff Quality Assessment

Rate the handoff quality to identify if more exploration is needed:

| Aspect | Good | Needs Exploration |
|--------|------|-------------------|
| Next steps | Clear, actionable | Vague or missing |
| File references | Specific paths/lines | General descriptions |
| Decisions | Rationale included | Just outcomes |
| Context | Complete picture | Gaps or assumptions |

If multiple aspects "Need Exploration", spend time re-exploring the codebase before continuing implementation.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.