# Drive It

> Run the complete engineering workflow from an idea to a merged pull request. Use only when the user explicitly invokes this orchestrator, not for isolated planning, implementation, or review.

- Skill: `typeweaver/drive-it` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add typeweaver/drive-it`
- Raw SKILL.md: https://api.skillmd.com/api/skills/typeweaver/drive-it/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: typeweaver (https://skillmd.com/u/typeweaver)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/typeweaver/drive-it

---


# Drive It

The user wants one idea taken to a merged pull request. Coordinate the focused
skills without restating their rules, keep `aurelius` as the mindset, and
resume at the earliest incomplete phase.

1. **Understand** — use `challenge-me` until outcome and boundaries are
   confirmed; skip when they are already clear.
2. **Plan** — use `plan-it`; the result may be one milestone or a roadmap of
   several. Present it with `brief-me` and ask once for approval to execute
   the whole plan autonomously — default one pull request per milestone, and
   settle deviations in this same question so no further input is needed
   before delivery.
3. **Build** — derive the goal with `define-goal`, set it as the active
   objective in the harness when it supports one, branch from the remote
   default branch, and implement with `craft-it`.
4. **Ship** — before each commit: run `review-it`, fix the justified findings,
   record Follow-ups with `to-issues`, and commit with `conventional-commit`.
   Open the pull request with `create-pull-request` and run `review-it` once
   over the complete diff before it leaves draft. Expert lenses
   (`ask-rich-hickey`, `ask-martin-fowler`, `ask-kent-beck`,
   `ask-john-ousterhout`, `ask-barbara-liskov`, `ask-linus-torvalds`,
   `ask-donald-knuth`) are never required for a review: add one — or several —
   only when you are confident the perspective materially sharpens it. Repeat
   Build and Ship for each approved milestone.
5. **Deliver** — summarize with `brief-me`, ask one bundled question covering
   tracker synchronization and reviewer requests, then run `pr-review-loop`,
   implementing justified review feedback autonomously, until every pull
   request is merged by a human or genuinely blocked.

Work autonomously: research, decide, and resolve what you can yourself instead
of interrupting the user. Interrupt only when new evidence invalidates the
approved outcome, required authority is unavailable, or a step risks serious
irreversible damage. Never merge yourself, and never publish external issues,
deploy, or release without the matching explicit authorization.