skills.rest
raydocs
raydocsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

flow-plan

Generate epics and tasks in the .flow/ directory from feature descriptions.

Updated Jan 22, 2026
Search Tags:#workflow#planning#epics#task-management#product-management#flowctl
One-click install
npx skills add https://github.com/raydocs/antiflowskills --skill flow-plan-raydocs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-plan
Source: https://github.com/raydocs/antiflowskills/tree/main/.factory/skills/flow-plan
Command: npx skills add https://github.com/raydocs/antiflowskills --skill flow-plan-raydocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and design of feature work is often informal and hard to governance. This skill converts ideas into structured epics and tasks stored under .flow/, providing a repeatable, auditable planning process that aligns with repository conventions.

Core Features & Use Cases

  • Turn rough ideas into epics and tasks within the .flow/ directory to drive alignment and tracking.
  • Ensure planning outputs are specifications, not implementations; no code is written at this stage.
  • Integrate with flowctl for lifecycle management, status updates, and evidence collection.
  • Use for planning a new feature, refining an existing plan, or turning concepts into actionable work items.

Quick Start

Provide a feature description to create an epic and tasks in the .flow/ directory.

Frequently Asked Questions about flow-plan

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

FAQPage Schema
How do I turn rough feature ideas into structured epics and tasks for product planning?▼

Structured product planning involves generating epics and tasks with clear acceptance criteria from feature descriptions, storing them in the .flow/ directory to drive alignment and tracking.

Does flowctl work with .flow/ directory files for task lifecycle management?▼

Yes, flowctl integrates with the .flow/ directory for lifecycle management, status updates, and evidence collection during planning to track work items effectively.

Can I generate code implementations alongside task breakdowns when planning a feature?▼

No, planning outputs are specifications, not implementations. The process generates structured work items and task breakdowns but writes no code at this stage of the workflow.

What is the best way to refine an existing feature plan into actionable work items?▼

The best way to refine an existing plan is to apply structured planning to update or generate new epics and tasks in the .flow/ directory, ensuring outputs align with repository conventions.

Do I need flowctl to manage status updates for epics in the .flow/ directory?▼

Yes, you need flowctl for state management and tracking. It handles lifecycle management and status updates for the structured work items generated during the planning process.

Related Skills

Explore More Product & Management Skills→
mickpletchermickpletcher
14

spec-writer

Convert rough repo change ideas into numbered spec folders with requirements, plans, and task lists.

Community
Intermediate
Gundlapuriswathiii006Gundlapuriswathiii006

project-tasks

Create, update, and track project tasks with states and dependencies.

Community
Intermediate
gmickelgmickel
674

flow-next-work

Orchestrate Flow epics and tasks with git-based tracking and quality gates.

Community
Advanced
klenklen
5

theme-epic-story

Organize product work into themes, epics, and stories.

Community
Intermediate