drive-approval

Automates user approval, revision, and abandonment workflows for drive ticket implementations.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/qmu/workaholic --skill drive-approval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drive-approval
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/drive-approval
Command: npx skills add https://github.com/qmu/workaholic --skill drive-approval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a controlled, user-approved drive workflow for implementing tickets, preventing unchecked changes by ensuring a formal approval, revision, and abandonment process.

Core Features & Use Cases

  • Approval dialog: Presents a deterministic decision using a selectable options prompt.
  • Revision flow: Records feedback and applies targeted changes before re-approval.
  • Abandonment flow: Safely discards changes with a failure analysis and ticket relocation.
  • Integration: Works with the existing archive/commit tooling to finalize tickets.

Quick Start

After implementing a ticket during a drive cycle, trigger the drive-approval flow to collect user selection and proceed accordingly.

Frequently Asked Questions about drive-approval

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

FAQPage Schema
How do I require user approval before finalizing ticket implementations?

To require user approval for ticket implementations, you need a guided workflow that gates changes using a selectable options prompt before finalizing. This enforces a deterministic decision process to prevent unchecked modifications during drive cycles.

What happens to ticket changes if an implementation needs revisions?

During the revision flow, user feedback is recorded and targeted changes are applied to the implementation before requesting re-approval. This ensures all modifications are reviewed before the ticket can proceed to archiving.

How do I safely abandon a ticket implementation in a drive workflow?

To safely abandon a ticket implementation, the workflow performs a failure analysis and relocates the ticket. This discards the applied changes securely while documenting the reason for abandonment.

Can I integrate approved ticket changes with existing commit and archiving tooling?

Yes, the approval flow integrates with existing archive and commit tooling to finalize tickets. Once a user selects approval, the process connects directly to these tools to commit the changes.

When do I need a formal abandonment process for ticket revisions?

You need a formal abandonment process when a ticket implementation fails and must be safely discarded. The workflow handles failure analysis and ticket relocation to maintain repository cleanliness without losing context.