Flow Next — Plan

What it does

This skill turns a rough idea or Flow ID into a structured epic and task set in a repository's .flow/ directory. It enforces repo conventions, uses bundled flowctl tooling for task management, and produces specs and tasks sized for follow-up work. The skill emphasizes planning (not implementation) and includes option parsing, pre-checks, and a strict workflow to avoid drift.

When to use it

Use when you need a product-minded, repo-aware plan: breaking features into epics and tasks, producing acceptance criteria, and preparing work that fits the repo's flowctl conventions. Triggers on commands like /flow-next:plan and Flow IDs (fn-1-add-oauth, fn-1, fn-1.2). Not intended to write code.

What's included

• Scripts: none bundled (has_scripts=false) — but the skill relies on a bundled flowctl provided by the plugin at runtime.
• References: includes examples and steps files in the repo to guide its operation (examples.md, steps.md).
• Instructions: detailed option parsing, pre-checks, research and review workflows, and strict output rules for writing epic and task files into .flow/.

Compatible agents

Designed for agents and plugin hosts that support bundled CLI tooling and repo-scoped workflows (Claude Code, Factory Droid, Codex, other code-focused LLM runners).