flow-next

Automate planning and tracking of Flow-Next epics and tasks with flowctl.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/tiendung/flow-next --skill flow-next-tiendung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next
Source: https://github.com/tiendung/flow-next/tree/main/skills/flow-next
Command: npx skills add https://github.com/tiendung/flow-next --skill flow-next-tiendung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flow-Next Task Management centralizes administration of .flow/ epics and tasks directly in the repository, reducing manual tracking, context switching, and drift between code and project work.

Core Features & Use Cases

  • Centralized planning and progress tracking for epics (fn-N) and tasks (fn-N.M) within a repository.
  • Clear visibility of epics and tasks, with commands to list, show, and filter by status or epic.
  • Automation-friendly workflow that integrates with the bundled flowctl tool to orchestrate planning and execution work.

Quick Start

Run the bundled flowctl command to list epics and tasks for your repository.

Frequently Asked Questions about flow-next

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

FAQPage Schema
How do I track epics and tasks within a code repository?

You can track epics and tasks within a repository using centralized planning commands to list items, show details, and mark progress without manual tracking or context switching.

What is the best way to automate task management workflows in a repository?

Automate task management workflows by orchestrating commands with bundled flowctl tooling, providing a consistent context for planning and executing epics and tasks directly in the codebase.

How do I list and filter repository tasks by status or epic?

List and filter repository tasks by status or epic using dedicated commands that provide clear visibility into task progress and epic details across the project.

Can I manage multiple epics simultaneously in a single repository?

Yes, you can manage multiple epics simultaneously in a single repository, tracking progress and creating tasks across various epics using centralized administration commands.

Does flow-next require external dependencies to manage repository workflows?

No, flow-next manages repository workflows without external dependencies, relying entirely on bundled flowctl tooling to orchestrate task management commands.

Why use repository-level task tracking instead of external project management tools?

Repository-level task tracking reduces drift between code and project work, centralizing administration of epics and tasks directly within the codebase to eliminate context switching.