一键导入
handover
Generate a comprehensive markdown summary of our conversation for seamless handoff to another AI agent. Use when ending a session or transferring work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate a comprehensive markdown summary of our conversation for seamless handoff to another AI agent. Use when ending a session or transferring work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | handover |
| description | Generate a comprehensive markdown summary of our conversation for seamless handoff to another AI agent. Use when ending a session or transferring work. |
This command generates and saves a markdown file. Always:
./handoff-summary-YYYYMMDD-HHMMSS.mdThe purpose is file creation, not just information display.
Generate comprehensive summary for AI agent handoff: $ARGUMENTS
This command creates a detailed markdown summary of our entire conversation, structured to enable another AI agent to seamlessly continue the work. The summary includes:
The command generates a markdown file with the following structure:
# Project Handoff Summary
Generated: [timestamp]
---
## Overview
Brief description of the project and main objectives
## User Context
- User's technical background and preferences
- Specific requirements and constraints
- Communication style preferences
## Original Requirements
- Initial problem statement
- Key goals and objectives
- Success criteria
## Completed Work
### Task 1: [Description]
- What was done
- Why this approach was chosen
- Key code changes
- Files affected
### Task 2: [Description]
...
## Project Structure
Current state of the codebase:
- Directory structure
- Key files and their purposes
- Dependencies added/modified
## Technical Decisions
### Decision 1: [Topic]
- Options considered
- Chosen approach
- Rationale
### Decision 2: [Topic]
...
## Code Examples
Key code snippets demonstrating important implementations
## Current State
- What's working
- What's being worked on
- Known issues or limitations
## Pending Tasks
- [ ] Task 1
- [ ] Task 2
- [ ] Task 3
## Important Warnings
- Critical information to avoid breaking changes
- Security considerations
- Performance implications
## Next Steps
Recommended actions for continuing the work
## Related Files
- File 1: Purpose and recent changes
- File 2: Purpose and recent changes
## Additional Context
Any other relevant information for smooth continuation
Basic usage:
/handover
With specific focus:
/handover focusing on authentication implementation
For specific date range:
/handover for work done today
Captures communication preferences, technical level, and any specific requirements mentioned during conversation
Documents why certain approaches were chosen over others, preventing future agents from undoing intentional choices
Includes actual code snippets for complex implementations, ensuring the next agent understands the implementation style
Highlights any critical information that could cause issues if not known (e.g., "Don't modify X because it will break Y")
Lists all files that were created or modified, with brief descriptions of their purpose and changes
The summary will include:
The command will:
handoff-summary-[timestamp].mdThis ensures perfect continuity when switching between AI agents or resuming work after a break.
Transform verbose natural language requests into structured bilingual documentation (Korean for review + English for AI prompts). Use when you need to clarify and structure a complex request before implementation.
Review current git changes or latest commit using code-reviewer and architect-reviewer agents. Use after completing code changes to get comprehensive quality feedback.
Review comments and suggest cleanup (identify unnecessary comments, recommend improvements). Use to aggressively clean up comment debt in code.
Identify and safely remove dead code, deprecated code, and unused exports from codebase. Use when you need to clean up unused or obsolete code.
Generate business rule documentation from domain knowledge and requirements. Use when you need to document complex business logic or domain rules.
Implement UI E2E tests sequentially using Playwright MCP, stop on bug discovery. Use after e2e-ui-research to implement the planned test scenarios.