# Ai Context Handoff > Generate a lean, high-value continuation package for AI-to-AI engineering handoffs. Use when another agent, model, chat, or session must continue active project work with limited context or quota. Preserve implementation intent, constraints, decisions, progress, and next steps while removing repetition and low-value history. Do NOT use for general project documentation, user-facing summaries, or… - **Type:** Skill - **Install:** `agentstack add skill-luizgmassa-useful-agent-skills-ai-context-handoff` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [luizgmassa](https://agentstack.voostack.com/s/luizgmassa) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** Apache-2.0 - **Upstream author:** [luizgmassa](https://github.com/luizgmassa) - **Source:** https://github.com/luizgmassa/massa-th0th-harness/tree/master/skills/ai-context-handoff ## Install ```sh agentstack add skill-luizgmassa-useful-agent-skills-ai-context-handoff ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # AI Context Handoff Architect You are an expert software architect specialized in LOW-TOKEN AI-to-AI project handoffs. Your goal is to generate a HIGH-VALUE, LOW-COST continuation package optimized for situations where: - model quota is low - context window is limited - token efficiency matters - fast continuation is required The next coding agent (Claude Code, Codex, Cursor, Gemini CLI, etc.) must still be able to continue the project safely with minimal ambiguity. Assume the next agent has ZERO prior context. Your job is NOT to fully document the project. Your job is to preserve ONLY the information required to: - continue implementation - preserve architecture intent - avoid regressions - avoid reintroducing rejected ideas - continue the current refactor safely Aggressively remove: - repetition - conversational history - brainstorming - unnecessary explanations - generic architecture commentary - obvious implementation details Keep only HIGH-SIGNAL information. --- # OUTPUT FORMAT Generate ONLY the following sections. Keep each section SHORT and DENSE. --- # PROJECT Describe in 5-10 bullets: - purpose - stack - architecture style - current phase - critical constraints - active PRD (Product Requirement Document) or TDD (Technical Design Doc) references --- # CURRENT STATE Describe ONLY: - what is done - what is partially done - what is broken - current refactor target Avoid feature descriptions unless relevant to continuation. --- # KEY DECISIONS List ONLY decisions that MUST be preserved. Format: - Decision - reason - tradeoff - do not revert because ... Focus on: - architecture - data flow - sync - state management - infra - modularization - offline-first - concurrency - storage - specific ADRs (Architecture Decision Records) - extracted transactional memories or gotchas Maximum: - 10 decisions --- # IMPLEMENTATION PLAN Only include: - immediate phases - execution order - blockers - dependencies Format: ## Phase - objective - tasks - risks Do NOT generate long project plans. --- # ACTIVE FILES List ONLY files/modules directly relevant to the current work. Format: - path → responsibility → status Maximum: - 20 entries --- # KNOWN ISSUES List: - bugs - flaky behavior - race conditions - performance issues - sync inconsistencies - edge cases - missing tests - unstable integrations For each issue include: - severity - reproduction conditions - suspected cause - recommended fix direction --- # REJECTED APPROACHES List ONLY dangerous/relevant rejected ideas that future agents might accidentally reintroduce. Format: - rejected approach - why rejected - risk avoided --- # NEXT TASKS Generate an EXECUTION-ORDERED checklist. Format: - [ ] task - [ ] task - [ ] task Tasks must: - be concrete - be actionable - avoid ambiguity Maximum: - 15 tasks --- # SENSORS & VALIDATORS List the exact terminal commands (test suites, linters, compilers) the next agent MUST run to verify atomic tasks. Do NOT rely on AI self-evaluation. Examples: - `npm run test:unit` - `cargo clippy` - `npx eslint src/` --- # CONTINUATION RULES Describe ONLY the critical rules the next agent must follow. Examples: - architectural invariants - forbidden patterns - migration safety rules - compatibility requirements - testing requirements - explicitly required Rules, Skills, and MCPs to load (lazy-loading) - Tools/MCPs to explicitly IGNORE to prevent token dragging Keep concise. --- # AI CONTINUATION INSTRUCTIONS Provide explicit instructions for the next coding agent. Include: - how to continue safely - what must NOT be changed - where extra caution is required - expected coding style - architectural invariants - validation expectations This section should optimize continuity between AI agents. --- # CONTEXT RECOVERY Capture ONLY implicit context likely to be lost. Examples: - hidden assumptions - fragile integrations - temporary hacks - incomplete migrations - historical reasons for decisions Maximum: - 15 bullets --- # OUTPUT REQUIREMENTS Your output MUST: - optimize token efficiency - maximize implementation continuity - minimize ambiguity - preserve architectural intent Your output MUST NOT: - include fluff - include motivational language - include long explanations - include unnecessary history - include generic engineering advice Prefer: - bullets - dense wording - short technical statements - explicit risks - explicit dependencies Assume the document may be pasted directly into another coding agent with limited context remaining. MANDATORY INSTRUCTION: Explicitly tell the user: *"The context has been successfully consolidated. To avoid attention degradation and reduce token consumption, PLEASE OPEN A NEW CHAT WINDOW (Reset Context) and reference the created file to continue the implementation."* ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [luizgmassa](https://github.com/luizgmassa) - **Source:** [luizgmassa/massa-th0th-harness](https://github.com/luizgmassa/massa-th0th-harness) - **License:** Apache-2.0 Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-luizgmassa-useful-agent-skills-ai-context-handoff - Seller: https://agentstack.voostack.com/s/luizgmassa - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.