Generate structured handoff summaries between workflow phases.
Scanned 2/12/2026
Install to Claude Code
npx -y skills add vneseyoungster/ChocoVine --skill context-preservation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Context Preservation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vneseyoungster-context-preservation)More formats (shields.io, HTML) on the badges page.
---
name: context-preservation
description: Generate structured handoff summaries between workflow phases.
Use when transitioning between RQPIV phases.
---
# Context Preservation Skill
## Purpose
Maintain context continuity across phases and sessions.
## When to Use
- Transitioning between RQPIV phases
- Handing off between sub-agents
- Pausing work for later resumption
- Creating progress reports
## Templates
### Phase Handoff
Reference: [templates/handoff-template.md](templates/handoff-template.md)
Use when transitioning from one phase to another. Captures:
- Summary of completed work
- Key findings and decisions
- Artifacts created
- Recommendations for next phase
### Progress Summary
Reference: [templates/progress-summary.md](templates/progress-summary.md)
Use for tracking ongoing work:
- Completed tasks
- In-progress items
- Blocked items
- Next steps
### Session Resume
Reference: [templates/session-resume.md](templates/session-resume.md)
Use when resuming interrupted work:
- Last known state
- Files to reload
- Continue point
## Context Preservation Process
### At Phase Start
1. Read previous phase handoff
2. Load relevant artifacts
3. Note key constraints/decisions
4. Begin phase work
### During Phase
1. Update progress summary as work progresses
2. Document significant decisions
3. Note any blockers or issues
### At Phase End
1. Create comprehensive handoff
2. List all artifacts created
3. Provide recommendations
4. Clear next actions
## Artifact Naming Convention
```
{type}-{session}-{timestamp}.md
```
Examples:
- `handoff-auth-feature-20251215.md`
- `progress-auth-feature-20251215-1430.md`
- `session-resume-auth-feature.md`
## Storage Locations
| Artifact Type | Location |
|---------------|----------|
| Handoffs | `plans/sessions/{session}/` |
| Progress | `plans/sessions/{session}/` |
| Resume | `plans/sessions/{session}/` |
## Best Practices
### For Handoffs
- Be concise but complete
- Include file paths for referenced artifacts
- Highlight decisions that affect future phases
- Note any assumptions made
### For Progress
- Update frequently (after each significant action)
- Be honest about blockers
- Include time context
### For Resume
- Capture exact stopping point
- List files to re-read
- Include any temporary notes
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!