context-preservation
Generate structured handoff summaries between workflow phases. Use when transitioning between RQPIV phases.
When & Why to Use This Skill
The Context Preservation skill is a specialized framework designed to maintain continuity and data integrity across complex, multi-phase AI workflows. By generating structured handoff summaries, progress reports, and session resumes, it ensures that critical context, key decisions, and technical artifacts are never lost when transitioning between project phases or handing off tasks between different sub-agents.
Use Cases
- Workflow Phase Transitions: Use structured handoffs to move seamlessly from research (RQPIV) to implementation, ensuring all requirements and constraints are preserved.
- Multi-Agent Orchestration: Facilitate clear communication and task delegation between specialized sub-agents by providing concise summaries of completed work and pending actions.
- Session Resumption: Quickly pick up where you left off after a break by utilizing session resume templates that identify the last known state and necessary files to reload.
- Project Milestone Reporting: Generate automated progress summaries that document completed tasks, identified blockers, and recommendations for future development stages.
| name | context-preservation |
|---|---|
| description | Generate structured handoff summaries between workflow 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
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
Use for tracking ongoing work:
- Completed tasks
- In-progress items
- Blocked items
- Next steps
Session Resume
Reference: templates/session-resume.md
Use when resuming interrupted work:
- Last known state
- Files to reload
- Continue point
Context Preservation Process
At Phase Start
- Read previous phase handoff
- Load relevant artifacts
- Note key constraints/decisions
- Begin phase work
During Phase
- Update progress summary as work progresses
- Document significant decisions
- Note any blockers or issues
At Phase End
- Create comprehensive handoff
- List all artifacts created
- Provide recommendations
- Clear next actions
Artifact Naming Convention
{type}-{session}-{timestamp}.md
Examples:
handoff-auth-feature-20251215.mdprogress-auth-feature-20251215-1430.mdsession-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