Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
git clone https://github.com/rohitg00/pro-workflow.git--- name: session-handoff description: Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off". user-invocable: true --- # Session Handoff Different from wrap-up. Wrap-up is a checklist for *you*. Handoff is a document written for the *next session*. ## Trigger Use when saying "handoff", "continue later", "pass to next session", "session transfer", or ending a session and wanting to resume smoothly. ## Workflow 1. Gather current state from git. 2. List completed, in-progress, and pending work. 3. Note key decisions made and their reasoning. 4. Capture any learnings from this session. 5. Generate a resume command for the next session. ## Commands ```bash git status git diff --stat git log --oneline -5 git branch --show-current ``` ## Output ```markdown # Session Handoff — [date] [time] ## Status - **Branch**: feature/xyz - **Commits this session**: 3 - **Uncommitted changes**: 2 files modified - **Tests**: passing / failing / not run ## What's Done - [completed task 1] - [completed task 2] ## What's In Progress - [current task with context on where you stopped] - [file:line that needs attention next] ## What's Pending - [next task that hasn't been started] - [blocked items with reason] ## Key Decisions Made - [decision 1 and why] - [decision 2 and why] ## Learnings Captured - [Category] Rule (from this session) ## Files Touched - `path/to/file1.ts` — [what changed] - `path/to/file2.ts` — [what changed] ## Gotchas for Next Session - [thing that tripped you up] - [non-obvious behavior discovered] ## Resume Command > Continue working on [branch]. [1-2 sentence context]. Next step: [specific action]. ``` ## Guardrails - Write for the reader (next session), not the writer. - Include specific file paths and line numbers where relevant. - The resume command should be copy-pasteable into the next session. - Keep it factual — describe changes functionally, don't infer motivation.
[{"step":"End your session with a clear handoff request","action":"Say or type: 'Generate a handoff document for [PROJECT_NAME] including progress, tasks, decisions, and context.'","tip":"Be specific about the project name and any critical details you want included."},{"step":"Review and refine the generated document","action":"Use the output as a starting point. Add any missing details, correct inaccuracies, or adjust formatting to match your team's standards.","tip":"Check for completeness—ensure all open tasks have owners, priorities, and due dates."},{"step":"Share the document with your team or client","action":"Export the document (as text, PDF, or Markdown) and share via your preferred communication tool (Slack, email, project management tool).","tip":"Include a brief message summarizing the key points or next actions required from the recipient."},{"step":"Save the document for future reference","action":"Store the handoff document in your project folder or knowledge base (e.g., Notion, Confluence, Google Drive) for easy access when resuming work.","tip":"Tag the document with relevant keywords (e.g., 'handoff', 'project-name', 'date') for quick retrieval."},{"step":"Use the document to resume work efficiently","action":"When you return to the project, review the handoff document first. Update it as you make progress or encounter new information.","tip":"Set a reminder to review the document before your next session to ensure continuity."}]
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/rohitg00/pro-workflow/tree/main/skills/session-handoffCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Generate a structured handoff document for [PROJECT_NAME] based on our work so far. Include: 1) Current progress summary (what's been accomplished), 2) Open tasks with priorities and owners, 3) Key decisions made and rationale, 4) Context needed to resume work (dependencies, assumptions, next steps), and 5) Any blockers or risks. Format as a clear, actionable document suitable for sharing with [TEAM_MEMBER/CLIENT].
## Handoff Document: Website Redesign Project (Phase 1) **Project Context:** - Client: Acme Corp (e-commerce division) - Goal: Redesign homepage and product pages to improve conversion rate by 15% (current: 2.3%) - Timeline: Phase 1 (homepage + 2 product pages) to launch in 6 weeks - Previous Session: Completed wireframes and initial design mockups for homepage hero section **Current Progress:** - Wireframes approved for homepage (Figma link: [REDACTED]) - Initial design mockups completed for hero section (3 variations) - User research insights compiled (see attached doc: 'acme_research_insights.pdf') - Competitor analysis finalized (5 key competitors reviewed) **Open Tasks:** | Task | Priority | Owner | Due Date | Status | |------|----------|-------|----------|--------| | Finalize hero section design (select variation) | High | [DESIGNER_NAME] | 2023-11-15 | In Progress | | Create product page templates (2 variations) | High | [DESIGNER_NAME] | 2023-11-20 | Not Started | | Write copy for hero section (3 versions) | Medium | [COPYWRITER] | 2023-11-18 | Not Started | | Set up A/B testing framework | Medium | [DEVELOPER] | 2023-11-22 | Not Started | | Review accessibility compliance | Low | [QA_TEAM] | 2023-11-25 | Not Started | **Key Decisions:** 1. **Hero Section Layout:** Chose variation B (split-screen with product image + value prop) based on user testing showing 22% higher engagement than other options. 2. **Color Palette:** Finalized palette with primary #2A5C8A (trust) and secondary #F5F5F5 (cleanliness) based on competitor analysis and brand guidelines. 3. **Typography:** Selected Inter for body text and Playfair Display for headings to balance readability and brand personality. **Context for Resuming Work:** - **Dependencies:** Need final hero section design before proceeding with product page templates. - **Assumptions:** Assumed mobile-first approach will be maintained throughout the project. - **Next Steps:** After hero section finalization, we’ll proceed with product page templates and then iterate based on stakeholder feedback. - **Blockers:** Waiting on client approval for hero section variations (sent 2023-11-10, no response yet). - **Risks:** Potential delay if client feedback requires major revisions to hero section. **Resources:** - Figma project: [REDACTED] - Research insights: 'acme_research_insights.pdf' - Competitor analysis: 'competitor_analysis_acme.xlsx' - Brand guidelines: 'acme_brand_guidelines_2023.pdf' **Contact Info:** - Project Lead: [YOUR_NAME] ([EMAIL]/[PHONE]) - Backup Contact: [COLLEAGUE_NAME] ([EMAIL]/[PHONE])
skills-collection
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan