Convert feature requests or Flow IDs into epics and task trees via fluxctl.
npx skills add https://github.com/Nairon-AI/flux --skill flux-plan
Please help me install this Agent Skill. Skill: flux-plan Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-plan Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-plan
Converts vague feature requests or Flow IDs into a concrete epic with organized tasks, enabling clear planning and coordination without writing implementation code.
Invoke the Flux plan with /flux:plan followed by a brief description of the work or a Flow ID to generate an epic and task tree under the .flux/ directory.
High-intent search queries and answers about installing and using this skill.
To turn a vague feature request into a structured epic, use the flux-plan Skill to organize software work by generating hierarchical task trees, scoping boundaries, and acceptance criteria via fluxctl without writing implementation code.
The best way to plan dependencies and acceptance criteria is applying planning discipline through the flux-plan system, which encodes scope, future pressure checks, and cross-team traceability directly into the generated task tree.
You can refine existing epics by invoking the plan with a Flow ID, allowing the system to update the scope, dependencies, and hierarchical tasks for cross-team collaboration without embedding implementation code.
No, flux-plan does not write implementation code for bug fixes or refactoring; it communicates only through fluxctl to enforce planning discipline and manage state under the .flux/ directory.
You can use flux-plan for scoping upgrades, refactors, and bug fixes, as it converts varied software work requests into organized epics with future pressure checks and clear task trees.
StudentCristianLaunch a guided wizard to derive a feature ID and initial wave.
darrencrotonImplement code features strictly within an implementation-plan document's boundaries.
Nairon-AIVerify implemented behavioral branches against epic specs from .flux and git diff.
mattolsonDecompose project milestones into sequenced tasks with dependencies and risks.
