flow-planner

Plan phases, tasks, and iterations for structured work coordination.

38|4|Updated Oct 1, 2025
One-click install
npx skills add https://github.com/khgs2411/flow --skill flow-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-planner
Source: https://github.com/khgs2411/flow/tree/main/framework/skills/flow-planner/SKILL.md
Command: npx skills add https://github.com/khgs2411/flow --skill flow-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps plan and structure work using Flow's hierarchical structure (phases, tasks, iterations).

Core Features & Use Cases

  • Phase Planning: Create and organize phases
  • Task Planning: Add tasks to phases
  • Iteration Planning: Define iterations within tasks
  • Brainstorming Guidance: Suggest when to brainstorm

Quick Start

Start planning by creating a phase or adding a task to an existing phase.

Frequently Asked Questions about flow-planner

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

FAQPage Schema
How do I plan work across phases, tasks, and iterations?

Hierarchical planning organizes work by creating phases first, then adding tasks to those phases, and defining iterations within tasks. This structure ensures phases → tasks → iterations flow, preventing mixed standalone tasks and iterations while enabling coordination across projects and development cycles.

When should I use phases versus tasks versus iterations?

Phases group major work segments; tasks break phases into actionable units; iterations subdivide tasks into time-boxed cycles. Use phases for architectural decisions or feature roadmaps, tasks for specific deliverables, and iterations for sprint-level execution and incremental progress tracking.

Can I structure complex feature planning with this approach?

Yes. The hierarchical workflow supports brainstorming, architectural decisions, and breaking complex features into manageable iterations. Template-backed outputs integrate with planning dashboards, enabling cross-project coordination and enforcing consistent structure across new work.

What's the best way to organize development work across multiple projects?

Use the hierarchical phase-task-iteration model to maintain consistent planning structure across projects. The Golden Rule prevents mixing standalone tasks with iterations, ensuring clarity; template-compatible outputs sync with dashboards for unified visibility and progress tracking.

How do I avoid mixing standalone tasks with iteration-based work?

The Golden Rule enforces hierarchical purity: never place standalone tasks and iterations at the same level within a task. Follow the phases → tasks → iterations structure strictly; if a task contains iterations, all work units within it must be iterations, not mixed standalone items.