Chachamaru127-handoff

Name: Chachamaru127-handoff
Availability: InStock
Author: anyekoutouming

Generate handoff instructions and completion reports for two-agent Claude Code workflows.

2|Updated Apr 28, 2026

Search Tags:#reports #handoff #claude-code #workflows #pm #harness-review #impl-claude

Ready to run

npx skills add https://github.com/anyekoutouming/anyekoutouming --skill chachamaru127-handoff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Chachamaru127-handoff
Source: https://github.com/anyekoutouming/anyekoutouming/tree/main/chachamaru127-handoff
Command: npx skills add https://github.com/anyekoutouming/anyekoutouming --skill chachamaru127-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill streamlines PM-to-Impl handoffs and completion reporting in two-agent Claude Code workflows, ensuring clear context, traceable decisions, and consistent artifacts.

Core Features & Use Cases

PM → Implementer handoffs: generate handoff briefs from Plans.md
Implementer → PM handoffs and completion reports: produce structured reports with acceptance criteria, scope, and test results
Auto-fix and commit guidance: includes steps for automated fixes and integration with version control
Consistent formats for Cursor/OpenCode workflows and easy sharing

Quick Start

After harness-review approval, run /handoff cursor or /handoff opencode to generate and paste the handoff report.

Frequently Asked Questions about Chachamaru127-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a structured PM to implementer handoff report in Claude Code?▼

To generate a PM to implementer handoff report in Claude Code, use the handoff skill after harness-review approval to automatically produce structured briefs from Plans.md, ensuring clear context and traceable decisions for the implementer agent.

What is a two-agent Claude Code workflow and when do I need a handoff format?▼

A two-agent Claude Code workflow separates project management and implementation tasks. You need a structured handoff format when transitioning context between the PM and Impl agents to maintain traceability of acceptance criteria, scope, and verification results.

Can I use this handoff report format with Cursor and OpenCode workflows?▼

Yes, the generated handoff reports and completion summaries are specifically formatted for Cursor and OpenCode integration, allowing you to easily paste structured context, changed files, and next actions into these platforms.

What's the best way to document completion reports for implementer to PM handoffs?▼

The best way to document implementer to PM completion reports is to generate a structured summary that explicitly includes background, acceptance criteria, changed files, verification results, risks, and next actions to ensure full project context.

What should a completion report include to pass the finalization checkpoint in Claude Code?▼

A completion report must include background, acceptance criteria, scope, changed files, verification results, risks, and next actions to pass the finalization checkpoint and ensure the PM Claude agent has all required traceable artifacts.

Why does my PM to implementer handoff lose context in two-agent workflows?▼

PM to implementer handoffs often lose context when reports lack standardized structure. Generating handoff briefs directly from Plans.md with explicit acceptance criteria and scope ensures the implementer receives consistent, traceable instructions.