Converts feature requests into requirements, design, and task entries stored as durable Fux records.
npx skills add https://github.com/arpitarya/fux --skill fux-plan-arpitarya
Please help me install this Agent Skill. Skill: fux-plan Source: https://github.com/arpitarya/fux/tree/main/archive/v0.1/fux/data/skills/plan Command: npx skills add https://github.com/arpitarya/fux --skill fux-plan-arpitarya
fux refs and the graph to identify affected modules, and fux check flags tasks whose referenced code changed while still marked todo. - Graduation to durable knowledge: After implementation, design notes graduate into ADR and rule entries so the reasoning survives. - Use Case: Ask to plan a rollback feature; the Skill scaffolds a spec entry with user stories, links design to the actual modules in the graph, creates task entries with status tracking, and records decisions as ADRs. ## Quick Start Ask the assistant to run /fux plan with a feature request such as "plan adding rollback support to the release pipeline" and review the generated spec entry.High-intent search queries and answers about installing and using this skill.
Run /fux plan with your request in plain language. The Skill scaffolds a spec entry with user stories and EARS acceptance criteria, then builds design and task entries linked to the actual code through the Fux graph.
EARS (Easy Approach to Requirements Syntax) formats acceptance criteria as 'WHEN <trigger> THE SYSTEM SHALL <response>'. The Skill uses this pattern in the Requirements section of each spec entry to make criteria testable and unambiguous.
Each task entry carries code_refs pointing to the files it will change. Running fux check flags any task whose referenced code changed while its status is still todo, catching drift between plan and implementation automatically.
Yes, the Skill requires the fux CLI and a .fux/ project directory, created with fux init if missing. It also runs fux build before the design stage so the code graph is current for identifying affected modules.
The Skill explicitly forbids writing orphan docs like docs/*-plan.md. Instead, plans should be spec and task entries in the Fux index so they remain durable, code-linked, and maintainable rather than becoming stale scaffolding.
JoniPraiaAutomate plugadvpl installation and initialize the ADVPL/TLPP SQLite index.
tomfordrummAppend structured Context, Decision, and Consequences entries to daily ADR files.
Michael0520Load and aggregate specifications, changes, capabilities, and requirements from a repository.
endorphin-aiManage project documentation and work items using markdown files with Git.