Agent skill
comprehensive-context-handover
Forensic, high-fidelity context handover for seamless continuation in a new chat. Produces a single Markdown transfer artifact plus reusable templates, preserving decisions, requirements, non-negotiables, and open loops without truncation by judgment. Not for code continuation unless explicitly stated.
Install this agent skill to your Project
npx add-skill https://github.com/ogprotege/Skills/tree/main/Categories/Context/comprehensive-context-handover
Metadata
Additional technical details for this skill
- color
- slate
- model
- opus
- version
- 2.1
SKILL.md
Comprehensive Context Handover Protocol (CCHP) v2.1
Part 1: Operational Logic
Name: comprehensive-context-handover
Profile: Forensic Context Specialist
Objective: Synthesize non-coding sessions into high-fidelity artifacts for near-perfect session resumption.
Core Directives
-
Forensic Specificity
- Preserve exact wording for load-bearing constraints (“must”, “never”, “only”).
- Do not truncate by judgment.
-
Epistemological Tracking
- Use [G/C/P/K] tags to label maturity of key insights:
- [G] Genesis (novel discovery)
- [C] Custom (emerging pattern)
- [P] Product (proven approach)
- [K] Commodity (standard knowledge)
- Use [G/C/P/K] tags to label maturity of key insights:
-
Ledger Rigor
- Maintain:
- Decision Log (the why)
- Requirements Ledger (the what)
- Maintain:
-
Antifragile Ordering
- Structure by priority so critical data survives truncation:
- Orientation → Non-Negotiables → Decisions → Requirements → Open Loops → Context
- Structure by priority so critical data survives truncation:
Trigger Instructions
When invoked via “handover”, “checkpoint”, or “save context”:
- Scan the full conversation for unique terminology (e.g., Syriac, Latin, Intel codes).
- Identify 3–10 “Stop Re-Asking” points.
- Generate the artifact using the structured templates in Parts 2 and 3.
Deliverables
- Deliverable Format (Mandatory):
- All outputs produced by this skill MUST be delivered as a downloadable Markdown (.md) file.
- Inline summaries or partial outputs are not acceptable substitutes.
Part 2: Reusable Artifact Template
═══════════════════════════════════════════════════════════════════
CONTEXT TRANSFER ARTIFACT v2.1
═══════════════════════════════════════════════════════════════════
Generated: [ISO timestamp]
Session ID: [if available]
Transfer Type: [○ continuation | ◐ pivot | ● fresh start]
Domain: [context]
Code Continuation Required: [yes/no — default no unless explicit]
───────────────────────────────────────────────────────────────────
§ 1. IMMEDIATE ORIENTATION [SCAN FIRST]
───────────────────────────────────────────────────────────────────
MISSION
[One sentence: what is being done and why it matters]
STATUS
State: [✓ resolved | ⧗ in-progress | ⚠ blocked | ↻ iterating]
Progress: [where things stand]
Momentum: [↑ accelerating | → steady | ↓ stalled]
NEXT ACTION
[Exact next step when conversation resumes]
STOP RE-ASKING
- [Questions the receiver must NOT re-ask]
───────────────────────────────────────────────────────────────────
§ 2. USER NON-NEGOTIABLES [LOAD-BEARING]
───────────────────────────────────────────────────────────────────
- Format constraints:
- Scope constraints:
- Behavior/tone constraints:
- Explicit “must / never” rules:
───────────────────────────────────────────────────────────────────
§ 3. DECISION LOG [ANTI-REHASH]
───────────────────────────────────────────────────────────────────
| Decision | Rationale | Alternatives Rejected | Tradeoff Accepted | Type | Status |
|----------|-----------|-----------------------|------------------|------|--------|
Type: explicit | implicit | emergent
Status: final | tentative | pending
───────────────────────────────────────────────────────────────────
§ 4. REQUIREMENTS LEDGER [VERIFIABLE]
───────────────────────────────────────────────────────────────────
| Requirement | Scope | Priority | Acceptance Criteria | Status |
|-------------|-------|----------|---------------------|--------|
───────────────────────────────────────────────────────────────────
§ 5. ARTIFACTS & OUTPUTS [WHAT EXISTS]
───────────────────────────────────────────────────────────────────
Created:
- [Artifact]: [what it is + why it matters]
Referenced:
- [Resource]: [why it matters]
Tools Used:
- [Tool]: [how used + outcome]
───────────────────────────────────────────────────────────────────
§ 6. CRITICAL CONTEXT [INTERPRETIVE LAYER]
───────────────────────────────────────────────────────────────────
Key Insights [G/C/P/K]:
- [G] Genesis insight
- [C] Emerging pattern
- [P] Proven approach
- [K] Commodity knowledge
Constraints (Technical/Resource/Organizational/Ethical):
- Technical:
- Resource:
- Organizational:
- Ethical:
Uncertainty Map (Known unknowns/Fragile assumptions/Risks):
- Known unknowns:
- Fragile assumptions:
- Risks:
Values at Stake:
- [What matters beyond completion]
───────────────────────────────────────────────────────────────────
§ 7. OPEN LOOPS [FORWARD MOMENTUM]
───────────────────────────────────────────────────────────────────
Unresolved Questions:
- [ ]
Blockers:
- [ ]
Pending Inputs:
- [ ]
Hypotheses to Test:
- [ ]
───────────────────────────────────────────────────────────────────
§ 8. CONVERSATION HISTORY [OPTIONAL DEPTH]
───────────────────────────────────────────────────────────────────
<details>
<summary>Chronological narrative</summary>
Act I: Problem Formation
Act II: Exploration & Development
Act III: Current State
Notable Quotes:
- “…”
</details>
───────────────────────────────────────────────────────────────────
§ 9. TRANSFER METADATA [SYSTEM LEVEL]
───────────────────────────────────────────────────────────────────
Provenance:
Context Window Pressure: [○ | ◐ | ●]
Completeness: [% + what’s missing]
Verification: [✓ reviewed | ⚠ unverified | ⧗ partial]
Omissions (if any):
- [What was omitted and why]
───────────────────────────────────────────────────────────────────
§ 10. RECEIVER START PROMPT
───────────────────────────────────────────────────────────────────
Read this artifact fully.
Respond with:
1) Mission (in your words)
2) Current status
3) Immediate next action
Do not rehash decisions already logged.
═══════════════════════════════════════════════════════════════════
§ TRANSFER READY—Review for accuracy before sharing.
═══════════════════════════════════════════════════════════════════
---
## Part 3: Generator Prompt
Generate a CONTEXT TRANSFER ARTIFACT using the Comprehensive Context Handover Protocol (CCHP) v2.1.
Hard rules:
- Forensic detail. Do not omit “minor” constraints.
- No truncation by judgment. Only deduplicate exact repeats.
- Preserve exact wording when load-bearing.
- If anything is omitted, list it explicitly in an Omissions section.
- This is NOT for code continuation unless explicitly stated.
Use the Context Transfer Artifact v2.1 template exactly.
Fill every section. If something does not apply, write “N/A”.
Priority order if truncation occurs:
1) Immediate Orientation
2) User Non-Negotiables
3) Decision Log
4) Requirements Ledger
5) Open Loops
6) Critical Context
7) Artifacts & Outputs
8) Conversation History
9) Transfer Metadata
After generating, append:
“§ TRANSFER READY—Review for accuracy before sharing.”
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ogprotege/Skills
plan-reviewer
Review a development plan before implementation to identify risks, missing considerations, and better alternatives. Use for plans involving auth changes, migrations, integrations, or other high-impact work.
ogprotege/Skills
repo-doc-auditor
Perform a repo-wide, evidence-based audit of documentation against the current codebase and recent changes. Produces a proposed, fully rewritten documentation set in TempDoc-ForUserReview and asks for approval before any changes are applied to the existing docs.
ogprotege/Skills
documentation-architect
Create, update, and maintain clear, accurate, and well-organized technical documentation for complex codebases. This agent focuses on understanding the current state of the code and existing documentation before proposing or making changes, ensuring documentation remains up to date, discoverable, and trustworthy for developers.
ogprotege/Skills
code-architecture-reviewer
Review recently written code for best practices, architectural consistency, and correct system integration. Use for reviewing new endpoints, refactors, and UI components to ensure alignment with project standards and established patterns.
ogprotege/Skills
code-refactor-master
Refactor code for better organization, cleaner architecture, and improved maintainability. Use for reorganizing file structures, splitting large components, updating imports after moves, and enforcing consistent patterns across the codebase.
mattpocock/skills
edit-article
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
Didn't find tool you were looking for?