Stats
Actions
Tags
How this skill is triggered — by the user, by Claude, or both
Slash command
/lisa:epic-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Epic name:** Provided via arguments
Epic name: Provided via arguments
Read .lisa/epics/<epicName>/ directly.
Epic '<name>' not found.
Create it with: /lisa:create-epic <name>
STOP.
Read .state, spec.md, research.md, plan.md, and all task files.
Epic: <name>
Phase: <current phase>
Progress:
✓ Spec - complete (.lisa/epics/<name>/spec.md)
✓ Research - complete
✓ Plan - complete (X tasks)
● Execute - in progress (3/8 tasks done)
✓ 01-setup-database
✓ 02-create-models
✓ 03-api-endpoints
○ 04-add-auth (pending)
○ 05-write-tests (waiting on 04)
✗ 06-deploy-config (blocked)
Spec Summary:
<first 4-5 lines of spec.md Goal and Acceptance Criteria sections>
Yolo: <active with iteration X/Y | not active>
Next Actions:
• /lisa:continue <name> - Resume interactively
• /lisa:yolo <name> - Auto-execute remaining work
Task status icons:
✓ = done○ = pending or waiting on dependencies✗ = blocked→ = in-progressnpx 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.
Creates epic JSON files with vision (overview, goals, metrics, scope, NFRs) via user dialog, ID generation, and existence checks. Deprecated; use /plan instead.
Shows a single-screen work status dashboard with task state, epic progress, knowledge flywheel health, and recent activity. Useful for getting oriented or deciding next actions.