solution-handoff

Convert completed investigations into clustered problem-describing handoff prompts for agent-quorum.

9|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/eventbalancer/agent-quorum --skill solution-handoff-eventbalancer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solution-handoff
Source: https://github.com/eventbalancer/agent-quorum/tree/main/.agents/skills/solution-handoff
Command: npx skills add https://github.com/eventbalancer/agent-quorum --skill solution-handoff-eventbalancer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a debugging, review, or audit investigation, turning findings into actionable work often means either proposing a quick inline fix or writing a vague ticket. This Skill bridges that gap by harvesting confirmed findings into self-contained, problem-describing prompts that a downstream planning agent can execute, without prescribing the implementation. ## Core Features & Use Cases - Investigation Harvesting: Collects symptoms, root causes with file:line references, evidence, hypotheses, and open questions already present in the conversation. - Defect Clustering: Groups related defects into the smallest sufficient number of clusters with per-cluster rationale, merging related issues and splitting only genuinely independent ones. - Prompt Delegation: Hands each cluster to /prompt-architect, which composes and saves prompts under .agents/prompts/ and owns the launch confirmation for agent-quorum runs. - Use Case: After tracing three related test failures to a shared root cause in the provider layer, invoke this Skill to produce one clustered handoff prompt that a downstream agent uses to design a systemic, compatibility-preserving fix. ## Quick Start Ask the agent to run /solution-handoff after your investigation is complete so it clusters the confirmed defects and delegates handoff prompts to /prompt-architect.

Frequently Asked Questions about solution-handoff

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

FAQPage Schema
How do I turn an investigation into an implementation plan?

Run /solution-handoff after your investigation is complete. It harvests confirmed findings, clusters related defects, and delegates one problem-describing prompt per cluster to /prompt-architect, which saves prompts and confirms the agent-quorum launch.

When should I use solution-handoff instead of fixing directly?

Use it when the investigation is complete, root causes are backed by code, log, or test references, and the problem is non-trivial enough to deserve systemic design. Skip it for one-line fixes, cosmetic tasks, or unconfirmed root causes.

Can solution-handoff work from a requirements document?

Yes. Pass an approved requirements document path as the argument, and it harvests scope, decisions, acceptance criteria, and the originating issue reference from the document instead of conversation context.

Does solution-handoff start the agent-quorum run itself?

No. It only generates prompt requests for /prompt-architect. The actual agent-quorum launch happens inside /prompt-architect after explicit operator confirmation, using run profiles with distinct workdirs.

What happens if defects are unrelated to each other?

Genuinely independent defects, such as those in different subsystems with no shared root cause or file overlap, are split into separate clusters and prompts. Related defects are merged into a single prompt by default.