Stats
Actions
Tags
How this skill is triggered — by the user, by Claude, or both
Slash command
/lisa:list-epicsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read the `.lisa/epics/` directory directly.
Read the .lisa/epics/ directory directly.
For each subdirectory in .lisa/epics/:
.lisa/epics/<name>/.state (JSON) if it exists.state, infer from which files exist:
tasks/ dir exists → execute phaseplan.md exists → plan phaseresearch.md exists → research phasespec.md exists → spec phasetasks/*.md files and checking for ## Status: done/blocked/in-progress/pendingEpic: auth-system
✓ Spec
✓ Research
✓ Plan
● Execute (3/8 tasks done) [YOLO ACTIVE]
Next: /lisa:continue auth-system or /lisa:yolo auth-system
---
Epic: initial-setup
✓ Spec
✓ Research
✓ Plan
✓ Execute (5/5 complete)
---
Epic: new-feature
✓ Spec
○ Research
○ Plan
○ Execute
Next: /lisa:continue new-feature or /lisa:yolo new-feature
Legend:
✓ = complete (flag is true in .state, or file exists)● = in progress (has tasks but not all done)○ = not startedAlways show both /lisa:continue and /lisa:yolo for any epic with spec complete but not fully done.
If .lisa/epics/ does not exist or is empty:
No epics found.
Get started: /lisa:create-epic <name>
npx claudepluginhub fractalswift/llisa --plugin lisaVisualizes epic dependencies, blocking chains, and execution phases using flowctl and jq. Identifies ready epics, critical path, and parallel execution order.
Displays progress on incomplete task lists from .plans/tasks-*.yml files: total/completed counts, next actionable task per feature. Use to check active feature status.
Creates epic JSON files with vision (overview, goals, metrics, scope, NFRs) via user dialog, ID generation, and existence checks. Deprecated; use /plan instead.