flow-plan

Decompose dependencies with a DAG and produce an actionable implementation plan.

25|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/benkruger/flow --skill flow-plan-benkruger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-plan
Source: https://github.com/benkruger/flow/tree/main/skills/flow-plan
Command: npx skills add https://github.com/benkruger/flow --skill flow-plan-benkruger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates Phase 2 planning by decomposing dependencies with a DAG and producing an actionable implementation plan.

Core Features & Use Cases

  • DAG decomposition to generate a dependency-aware task graph that guides implementation.
  • Issue exploration and risk assessment to validate assumptions against the repository state and surface blockers.
  • Plan writing and governance to produce a structured plan detailing context, exploration, risks, approach, and tasks, with dependency mapping.

Quick Start

Run /flow:flow-plan to initiate Phase 2 planning and generate a concrete DAG-driven plan.

Frequently Asked Questions about flow-plan

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

FAQPage Schema
How do I automate project planning with a dependency DAG in Claude Code?

Automating project planning with a dependency DAG in Claude Code involves decomposing dependencies and validating risks to produce an actionable implementation plan. flow-plan coordinates Phase 2 activities by exploring the codebase and enforcing stateful transitions from plan extraction to execution.

What is DAG-driven planning for software engineering tasks?

DAG-driven planning for software engineering tasks is the process of decomposing project dependencies into a directed acyclic graph to generate a dependency-aware task graph. This approach validates assumptions against the repository state and surfaces blockers before implementation begins.

How do I generate a structured implementation plan from codebase exploration?

To generate a structured implementation plan from codebase exploration, you initiate Phase 2 planning to extract context, assess risks, map dependencies, and produce a governance plan. This validates assumptions and details the approach for implementation tasks.

Does flow-plan require specific dependencies to validate planning risks?

flow-plan does not require external dependencies to validate planning risks. It operates independently to explore the repository state, extract a structured plan, and enforce plan-check gates during stateful transitions from plan extraction to execution.

When do I need plan-check gates for workflow transitions?

You need plan-check gates for workflow transitions when coordinating Phase 2 activities to ensure dependencies are validated before execution. These gates enforce stateful transitions from plan extraction to execution, preventing unvalidated assumptions from reaching implementation.

What's the best way to decompose dependencies for an actionable implementation plan?

The best way to decompose dependencies for an actionable implementation plan is using DAG decomposition to generate a dependency-aware task graph. This method validates assumptions against the repository state and surfaces blockers through structured plan governance.