Promote a drover ticket's Projected fields into an Actual verified record.
npx skills add https://github.com/cosmicdreams/claude-plugins --skill verify-cosmicdreams
Please help me install this Agent Skill. Skill: verify Source: https://github.com/cosmicdreams/claude-plugins/tree/main/drover/skills/verify Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill verify-cosmicdreams
This Skill removes the extra work of re-entering fields when a drover implementer’s Projected fix turned out to be correct, letting you quickly mark the ticket as verified and close it.
### Projected block into a new ### Actual block.none, effectiveness to verified, and tracks verified_at and captured_by.lane-done, and sets status to closed.Use case: After running implementer work, you find the ticket’s ### Projected section matches what actually happened—use this Skill to confirm and close without rerunning the full solution-capture prompt.
Run /drover:verify <ticket-id> to promote the ticket’s Projected fields into Actual, mark it verified, and close the ticket.
High-intent search queries and answers about installing and using this skill.
To promote a projected fix to verified, this automation reads the drover ticket database, extracts the Projected block fields, writes an Actual block with divergence=none, and closes the ticket automatically.
Workflow automation for ticket verification copies the hypothesis, proposed fix summary, and commit SHA from the Projected block into an Actual block, sets effectiveness to verified, and updates the ticket labels.
Closing a drover ticket and updating kanban labels removes the review, implementing, and lane labels, adds the lane-done label, and sets the ticket status to closed upon successful verification.
Verifying a drover ticket does not require running the full solution-capture prompt again if the projected hypothesis was correct; the workflow directly promotes the existing fields to the Actual block.
Marking a ticket's projected fix as verified records metadata by setting divergence to none, effectiveness to verified, and tracking the verified_at timestamp and captured_by user fields.
This ticket verification workflow is designed for cases where divergence is none; if the projected fields do not match the actual fix, you should not use this promotion path and must document the differences manually.
cosmicdreamsDocument verified drover ticket solutions with root cause, fix summary, and commit SHA.
sparkline-venturesCollect and normalize product evidence from connected sources into weighted items.
cosmicdreamsClaim highest-priority Drover tickets, create worktrees, and run quality checks.
cosmicdreamsSearch drover project boards for verified ticket solutions by keyword or error fingerprint.