whip-plan

Plan a multi-agent workflow into a 6-phase whip plan saved to ~/.whip/plans.

10|1|Updated Feb 5, 2026

Search Tags:#workflow #planning #multi-agent #orchestration #execution #whip

Ready to run

npx skills add https://github.com/bang9/ai-tools --skill whip-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: whip-plan
Source: https://github.com/bang9/ai-tools/tree/main/whip/skills-codex/whip-plan
Command: npx skills add https://github.com/bang9/ai-tools --skill whip-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and coordinating multi-agent tasks can be error-prone and time-consuming; this Skill provides a structured 6-phase whip plan, captures decisions, and gates execution until approval.

Core Features & Use Cases

6-phase whip planning: convert a user intent into a concrete plan ready for review and execution.
Approval gating and plan persistence: saves to ~/.whip/plans and awaits user approval before starting execution with $whip-start.
Canvas for cross-workflow orchestration: helps teams align on task boundaries, backends, and ownership across tasks.

Quick Start

Describe your objective to whip-plan, and I will generate a 6-phase plan, save it to ~/.whip/plans, and await your approval to execute with $whip-start.

Frequently Asked Questions about whip-plan

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

FAQPage Schema

What is multi-agent workflow planning and when do I need a structured plan for it?▼

Multi-agent workflow planning converts a user intent into a concrete 6-phase plan ready for review and execution. You need it when coordinating cross-team tasks that require explicit backends, task boundaries, and ownership to ensure reproducible outcomes.

How do I generate a whip plan for cross-team orchestration?▼

To generate a whip plan, describe your objective to the planner. It will document a multi-agent workflow into a concrete 6-phase plan, save it to ~/.whip/plans, and await your approval before starting execution with $whip-start.

Does multi-agent execution require approval gating before starting tasks?▼

Yes, this multi-agent execution requires approval gating. The system captures decisions and gates execution until approval, saving the workflow plan to ~/.whip/plans and waiting for user authorization before triggering execution via $whip-start.

What's the best way to coordinate task boundaries and ownership across engineering teams?▼

The best way to coordinate task boundaries and ownership is using a structured 6-phase whip plan. It provides a canvas for cross-workflow orchestration, helping engineering teams align on backends and ownership to ensure reproducible outcomes.

Why does plan persistence matter for multi-agent workflows?▼

Plan persistence matters because it captures decisions and saves the 6-phase plan under ~/.whip/plans. This ensures the multi-agent workflow is documented for review, enforcing explicit backends and task boundaries before execution begins.