agent-branch-handoff

What problem does it solve?

This Skill solves inconsistent, incomplete agent-branch submissions by enforcing a clear handoff SOP so reviewers and maintainers can safely integrate only the intended Agent changes into the main system.

Core Features & Use Cases

• Branch-state aware guidance: Determines whether to create or switch to the correct feat/subagent-* branch and avoid duplicate creation.
• Strict submission scope enforcement: Limits commits to the relevant agents/<agent-name>/ path instead of allowing git add ..
• Mandatory README handover: Ensures the PR includes explicit main-backend integration details (including an agents.yaml snippet guidance) and clarifies whether main registration is changed.
• Review/Merge responsibility boundaries: Clarifies that developers deliver Agent code + README, while the audit/lead handles merge analysis, main-backend completion, and docs/Updates maintenance.
• Use Case: When building a new sub-agent or updating an existing one, it helps you generate an Agent PR plan that passes review faster and reduces integration mistakes.

Quick Start

Ask an AI to “Use the agent-branch-handoff SOP for my agent PR and tell me exactly how to prepare my branch, commit scope, and README handover fields.”