Convert feature requests or Flow IDs into epics and tasks in .flow/ via flowctl.
npx skills add https://github.com/tiendung/flow-next --skill flow-next-plan-tiendung
Please help me install this Agent Skill. Skill: flow-next-plan Source: https://github.com/tiendung/flow-next/tree/main/skills/flow-next-plan Command: npx skills add https://github.com/tiendung/flow-next --skill flow-next-plan-tiendung
Plan and structure work by converting feature requests or Flow IDs into well-scoped epics and tasks in the Flow-Next planning system.
Invoke /flow-next:plan with a feature description or an existing fn-N-slug to generate an Epic and its Tasks in .flow/.
High-intent search queries and answers about installing and using this skill.
To convert feature requests into structured epics and tasks, invoke /flow-next:plan with a natural language description or an existing Flow ID. It generates well-scoped .flow/ markdown spec files using flowctl, enforcing non-implementation planning guidelines.
Yes, you can use natural language to plan multi-epic initiatives in the Flow-Next system. The planning tool accepts natural language requests or explicit Flow IDs like fn-1-add-oauth to generate appropriately sized epics and tasks.
No, the Flow-Next planning system enforces non-implementation spec guidelines, meaning no code is allowed in plans. It requires explicit acceptance criteria and adherence to task sizing rules to keep specs focused on planning.
To start sprint planning with flowctl, invoke the /flow-next:plan command with your feature outline. The system outputs structured epic and task markdown files inside the .flow/ directory, providing explicit acceptance criteria for engineering teams.
The best way to structure work for a small enhancement without code is using /flow-next:plan to generate specs-only planning files. This enforces non-implementation guidelines, ensuring tasks contain explicit acceptance criteria rather than code snippets.
raydocsConvert feature requests or Flow IDs into Flow epics and tasks.
Nairon-AITrigger plan-sync to update downstream task specs after code drift.
tiendungCoordinate Flow-Next epic plan reviews across RepoPrompt and Codex backends.
MiDouTechGuide product managers through creating user story maps with structured outputs.
