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

flow-next-plan

Convert feature requests or Flow IDs into Flow epics and tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates vague feature requests or Flow IDs into structured Flow epics and tasks, enabling consistent planning, traceability, and faster delivery.

Core Features & Use Cases

  • Converts natural-language requests or existing Flow IDs (fn-N, fn-N.M) into an epic and a set of executable tasks stored under .flow/.
  • Enforces standardized planning workflows using flowctl for updates, dependencies, and spec generation.
  • Supports reuse and alignment across teams by centralizing plans, references, and task artifacts within .flow/.

Quick Start

Trigger the planning workflow by providing a feature description or a Flow ID with /flow-next:plan.

Frequently Asked Questions about flow-next-plan

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

FAQPage Schema
How do I convert a natural language feature request into structured project tasks?▼

Feature planning translates natural language briefs into structured Flow epics and tasks. It generates a centralized .flow directory containing executable specs and standardized task documentation for consistent execution.

What is a Flow ID and how do I use it for feature planning?▼

A Flow ID uses formats like fn-N or fn-N.M to reference existing feature requests. Supplying a Flow ID to the planning workflow retrieves the request and generates the corresponding epic, task dependencies, and spec documentation under .flow/.

How do I standardize project planning workflows across my team?▼

Standardizing project planning requires enforcing a consistent tool for all updates. This workflow enforces flowctl for dependencies, spec generation, and task updates, centralizing all plans and artifacts within a shared .flow directory for team alignment.

Do I need flowctl to manage task dependencies and spec generation?▼

Yes, flowctl is required for managing task dependencies and spec generation. The workflow enforces flowctl for all updates to the .flow directory, ensuring traceability and standardized execution across feature epics and tasks.

Can I use existing feature requests to generate executable task specs?▼

Yes, existing feature requests can generate executable task specs. Provide a natural language brief or an existing Flow ID, and the workflow creates an epic with a set of executable tasks stored under the .flow directory.

What are the limitations of managing epics and tasks in a .flow directory?▼

The .flow directory structure relies entirely on flowctl for updates and dependency management. Teams must adopt this specific workflow toolchain, as plans and task artifacts are centralized strictly within the .flow directory for traceability.

Related Skills

Explore More Product & Management Skills→
tiendungtiendung

flow-next-plan

Convert feature requests or Flow IDs into epics and tasks in .flow/ via flowctl.

Community
Advanced
raydocsraydocs

flow-next

Manage Flow epics and tasks within a repository using the flowctl CLI.

Community
Intermediate
raydocsraydocs

flow-next-interview

Conduct structured interviews with 40+ questions to refine specifications via flowctl.

Community
Advanced
ElmarbouheElmarbouhe

speckit-tasks

Generate dependency-ordered tasks.md files from Spec-Kit project structures.

Community
Advanced