workflow-planner

Generate executable implementation plans from brainstorm outputs with TDD-first guidance.

9|3|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/mattdurham/bob --skill workflow-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-planner
Source: https://github.com/mattdurham/bob/tree/main/agents/planner
Command: npx skills add https://github.com/mattdurham/bob --skill workflow-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans provide detailed, executable implementation steps for software tasks by analyzing brainstorm outputs and generating a structured, step-by-step plan.

Core Features & Use Cases

  • TDD-first planning: prioritize tests and verification before implementation, and produce test skeletons.
  • Structured task breakdown: convert requirements into concrete, ordered tasks with dependencies.
  • Artifact generation: save the plan to bots/plan.md and reference brainstorm inputs.

Quick Start

Provide a brainstorm document or task description; the planner will create a detailed, executable plan and store it in bots/plan.md.

Frequently Asked Questions about workflow-planner

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

FAQPage Schema
How do I convert brainstorming outputs into a step-by-step software implementation plan?

To convert brainstorming outputs into an implementation plan, provide the brainstorm document to generate a structured, step-by-step plan. It analyzes the inputs and saves the detailed, executable tasks to bots/plan.md.

What is TDD-first planning and how does it structure task decomposition?

TDD-first planning prioritizes writing tests and verification before implementation. It structures task decomposition by converting requirements into ordered tasks, generating test skeletons, and ensuring edge-case consideration and risk analysis are included.

Can I use this workflow planner for dependency assessment and risk analysis?

Yes, you can use this workflow planner for dependency assessment and risk analysis. It evaluates task dependencies and identifies potential risks during the breakdown process to ensure executable software implementation steps.

Do I need a brainstorm document to start generating an executable implementation plan?

You need a brainstorm document or a task description to start generating an executable implementation plan. The planner references these inputs to produce ordered tasks, TDD-first guidance, and final documentation artifacts.

What's the best way to document software task decomposition and edge-case consideration?

The best way to document task decomposition and edge-case consideration is to generate a structured plan artifact. This process creates a bots/plan.md file containing ordered tasks, dependencies, and test-first guidance for clear documentation.