skills.rest
korchasa
korchasaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

flowai-epic

Create structured epics with dependency-ordered phases and atomic tasks for multi-session software features.

Updated Mar 7, 2026
Search Tags:#planning#specification#requirements#decomposition#task-management#epic#software-architecture
One-click install
npx skills add https://github.com/korchasa/flowai-workflow --skill flowai-epic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flowai-epic
Source: https://github.com/korchasa/flowai-workflow/tree/main/.claude/skills/flowai-epic
Command: npx skills add https://github.com/korchasa/flowai-workflow --skill flowai-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a structured, traceable epic for large software features that cannot be specified or delivered in a single agent session, eliminating ad-hoc, untrackable plans and ensuring phased, dependency-ordered work with clear verification criteria.

Core Features & Use Cases

  • Produces a canonical specification file at documents/tasks/epic-{name}.md that contains metadata, goals, non-goals, architecture boundaries, definition of done, and phased work breakdown.
  • Enforces planning rules: no code output in the epic, phase size guard (≤50 requirements), per-phase status lifecycle, task-level verification, and use of a task-management tool to track execution.
  • Ideal for large features that span multiple files or sessions (e.g., cross-cutting refactors, platform migrations, multi-component feature rollouts) where phased delivery, traceability, and manual approval points are required.

Quick Start

Use the flowai-epic skill to create a draft epic for "Search Performance Rewrite" and present the phase decomposition in chat first.

Frequently Asked Questions about flowai-epic

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

FAQPage Schema
How do I decompose large software features into tracked phases and tasks?▼

To decompose large software features, create structured epics by breaking them into dependency-ordered phases and atomic tasks, outputting a specification file with per-phase status, prerequisites, and verification steps.

When do I need to create an epic specification for a software feature?▼

You need an epic specification when a feature spans more than three files, requires multiple agent sessions, or includes five or more phases where coordination, traceability, and phased status updates are needed.

How do I structure requirements for a multi-session software feature?▼

Structure requirements by generating a canonical epic file containing metadata, goals, non-goals, architecture boundaries, definition of done, and a phased work breakdown with task-level verification criteria.

Does epic planning allow generating code directly within the task specification?▼

Epic planning enforces a no code generation rule within the specification, focusing entirely on task decomposition, phase size limits of 50 requirements, and tracking execution via a task-management tool.

Can I use epic decomposition for smaller features under three files?▼

Epic decomposition is designed for large, multi-session features exceeding three files or five phases, making it unsuitable for smaller features that lack the need for phased delivery and manual approval points.

What is the best way to track cross-cutting refactors across multiple agent sessions?▼

The best way to track cross-cutting refactors is producing a dependency-ordered epic document with per-phase status lifecycle, prerequisites, and verification steps, using a task-management tool to coordinate execution.

Related Skills

Explore More Software Engineering Skills→
loianeloiane
50

epic-slicing-planning

Plan Epic-level architecture and vertical-slice roadmaps for large features.

Community
Advanced
0xharryriddle0xharryriddle
3

plan-harder

Create phased implementation plans with sprints and atomic tasks.

Community
Intermediate
Obsidian-OwlObsidian-Owl
1

dev.tasks

Convert feature design artifacts into a dependency-ordered tasks.md file.

Official
Advanced
ma08ma08
28

save-status

Persist task status files and reconcile session metadata across machines.

Community
Advanced