AgentSkillsCN

handoff

在验证 JIRA 工单是否符合组织关于英雄关系与描述质量的标准时，可优先选用此技能。它会检查英雄父级关系，并为编码助手、开发者与利益相关者验证描述的完整性。

SKILL.md
--- frontmatter
name: handoff
description: "Manages workflow transitions and completion reports in 2-Agent workflow. Use when user mentions '/handoff', completion report, handoff to Cursor/OpenCode, auto-fix, or reporting to PM. Do NOT load for: casual completion statements, progress chat, informal status updates."
allowed-tools: ["Read", "Write", "Edit", "Bash", "Grep", "Glob"]
argument-hint: "[cursor|opencode|auto-fix]"

Handoff Skill

PM-実装役間のハンドオフとワークフロー遷移を管理するスキル。

機能詳細

機能詳細
PM→実装役See references/handoff-to-impl.md
実装役→PMSee references/handoff-to-pm.md
レビュー指摘自動修正See references/auto-fixing.md
コミット実行See references/execute-commit.md

Quick Reference

  • •"Cursor に完了報告を書いて" → /handoff cursor
  • •"OpenCode にハンドオフ" → /handoff opencode
  • •"レビュー指摘を自動修正" → /handoff auto-fix
  • •"変更内容とテスト結果を含めて" → Includes git diff and test results

Prerequisites

This command should only run after harness-review APPROVE

ConditionRequiredCheck Method
harness-review completedYesReview result is APPROVE
No Critical/High issuesYesAll fixed
Implementation completeYesPlans.md tasks completed

Why handoff requires review approval:

  • •PM receives unreviewed changes otherwise
  • •Quality not assured
  • •Breaks /work flow (implement → review → fix → OK → handoff)

Usage

bash
/handoff cursor     # Handoff to Cursor
/handoff opencode   # Handoff to OpenCode

Execution Flow

Step 1: Identify Completed Tasks

  • •Check Plans.md checkboxes
  • •Summarize work done

Step 2: Update Plans.md

markdown
# Before
- [ ] Task name `pm:依頼中`

# After
- [x] Task name `cc:完了` (YYYY-MM-DD)

Step 3: Gather Changes

bash
git status -sb
git diff --stat

Step 4: Check CI/CD (if applicable)

bash
gh run list --limit 3

Step 5: Generate Report

Output Format

markdown
## Completion Report

### Summary
- (1-3 lines describing what was done)

### Completed Tasks
- **Task Name**: [Task description]

### Changed Files
| File | Changes |
|------|---------|
| `path/to/file1` | [Summary] |
| `path/to/file2` | [Summary] |

### Verification Results
- [x] Build success
- [x] Tests passed
- [x] Manual verification complete

### Risks / Notes
- (If any)

### Next Actions (for PM)
1. [ ] [What PM should do next]
2. [ ] [Optional items]

/work Integration Flow

code
/work execution
    ↓
Phase 1: Parallel implementation
    ↓
Phase 2: harness-review loop
    ├── NG (Critical/High) → Fix → Re-review
    └── OK (APPROVE) → Phase 3
    ↓
Phase 3: Auto-commit (if configured)
    ↓
Phase 4: This skill runs ← First time handoff happens

/work automatically calls this skill in Phase 4. When running manually, always do so after harness-review APPROVE.

Target-Specific Notes

Handoff to Cursor

  • •Plans.md markers use cc:完了 (Japanese)
  • •Report format optimized for Cursor PM workflow
  • •Includes context for /review-cc-work command

Handoff to OpenCode

  • •Similar format to Cursor
  • •Compatible with OpenCode's command structure
  • •Works with multi-LLM development workflow

Related Skills

  • •work - Main implementation workflow
  • •harness-review - Code review
  • •2agent - 2-Agent workflow setup