drive-plan

Orchestrate multi-phase software changes from planning through implementation and review.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/0xdeafcafe/skills --skill drive-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drive-plan
Source: https://github.com/0xdeafcafe/skills/tree/main/skills/drive-plan
Command: npx skills add https://github.com/0xdeafcafe/skills --skill drive-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you execute substantial software changes without skipping the planning and review discipline that prevents costly rework later. It turns a vague feature request into a structured workflow that produces design artifacts, implementation, and an audit pass before you open a PR.

Core Features & Use Cases

  • End-to-end change orchestration: Guides a feature through planning, implementation, and review in a fixed sequence.
  • Phase-boundary confirmations: Requires explicit user approval before moving from ADR and spec creation to coding, then from coding to audit.
  • Review-driven fix loop: Uses review findings to dispatch parallel fix work, then re-runs review until the change reaches a stable state.
  • Use Case: When you need to introduce a multi-file feature or architectural change, this Skill creates the ADR and Gherkin spec first, implements against that contract, audits the result, and leaves you ready to package the work into a PR.

Quick Start

Ask the assistant to use drive-plan to take a substantial feature from planning through implementation and review with confirmation at every phase.

Frequently Asked Questions about drive-plan

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

FAQPage Schema
How do I orchestrate a multi-file software change from planning to pull request?

Multi-file software changes are orchestrated using a gated multi-phase workflow that processes feature development through planning, implementation, and review. This enforces discipline by requiring explicit phase-boundary confirmations before advancing to subsequent steps.

What is the best way to introduce architectural updates without skipping code review?

Architectural updates can be introduced safely by composing plan-change, implement-change, and review-change skills sequentially. This ensures an audit pass is completed using review findings to dispatch parallel fix work before opening a pull request.

How does phase-boundary confirmation work during feature implementation?

Phase-boundary confirmation requires explicit user approval before moving from ADR and Gherkin spec creation to coding, and again before transitioning from coding to the audit phase. This preserves user judgment for decision findings throughout the workflow.

When do I need to create an ADR and Gherkin specifications for a pull request?

ADR and Gherkin specifications are needed when a change is substantial enough to require design artifacts and a contract before coding. This workflow generates them first, implements against that contract, and audits the result to prevent costly rework.

Can I run parallel fix packets during a review-driven audit loop?

Yes, the review-driven audit loop dispatches parallel fix packets based on review findings. It then re-runs the review process until the software change reaches a stable state, leaving you ready to package the work into a pull request.

What are the limitations of using workflow orchestration for minor code adjustments?

Workflow orchestration for minor code adjustments introduces unnecessary overhead by enforcing ADR creation, Gherkin specifications, and audit phases. This gated multi-phase workflow is designed for substantial multi-file changes that require strict planning and review discipline.