solution

Document verified drover ticket solutions with root cause, fix summary, and commit SHA.

Updated Feb 28, 2026

Search Tags:#root cause #verification #knowledge retention #commit sha #drover #ticket capture

Ready to run

npx skills add https://github.com/cosmicdreams/claude-plugins --skill solution-cosmicdreams

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: solution
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/drover/skills/solution
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill solution-cosmicdreams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It preserves the verified root cause and fix details for a drover ticket so the team can reuse the knowledge later instead of relearning the same solution.

Core Features & Use Cases

Manual solution capture: Prompts for root cause, fix summary, and the authoritative commit SHA to document the real outcome.
Ticket update with structured “Actual” block: Writes a formatted ## Solution > ### Actual section to the ticket, including verification metadata.
Optional divergence capture: When a ### Projected block exists, records whether the projected hypothesis matched reality and captures a brief divergence note.

Quick Start

Run the skill with the command /drover:solution <ticket-id> to write and verify the Actual solution into the specified drover ticket and close it.

Frequently Asked Questions about solution

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

FAQPage Schema

How do I document a verified root cause and fix for a resolved ticket?▼

To document a verified root cause and fix, capture the actual root cause, fix summary, and authoritative commit SHA. This records the real outcome without fabrication, ensuring durable knowledge stored for future recall and team reuse.

What is the best way to capture ticket solutions for future knowledge retention?▼

Capturing ticket solutions for future knowledge retention involves writing a structured Solution block with verification metadata to the ticket. This preserves the verified root cause and fix details so the team can reuse the knowledge later instead of relearning.

How do I record divergence when a projected fix hypothesis differs from the actual root cause?▼

To record divergence when a projected fix hypothesis differs from the actual root cause, capture a brief divergence note when a Projected block exists. This records whether the projected hypothesis matched reality alongside the verified actual solution.

Can I use manual post-fix workflows to close tickets with updated labels and status?▼

Yes, you can use manual post-fix workflows to close tickets with updated labels and status. After documenting the verified solution and reading the ticket from the drover Beads DB, the workflow updates the ticket labels and closes it.

Does solution capture require reading the ticket from the drover Beads DB first?▼

Yes, solution capture requires reading the ticket from the drover Beads DB first. The workflow then prompts the user for required fields without fabrication, writes the structured Actual block, and closes the ticket with updated labels.

Why does durable knowledge capture matter after resolving an error?▼

Durable knowledge capture matters after resolving an error because it preserves the verified root cause and fix details. This prevents the team from relearning the same solution and enables efficient future recall of the authoritative commit SHA.