skills/next/SKILL.md
--- tldr: Show actionable items to work on category: observation --- # /eidos:next Aggregate actionable items into a prioritised list. ## Usage ``` /eidos:next ``` ## Instructions ### 1. Scan Sources (fast) Use grep/glob to quickly filter without reading full files. Only read a file when you need detail for presentation. ```bash # Active plans with unchecked actions grep -rl '\[ \]' memory/plan\ -\ *.md 2>/dev/null # Open todos (existence = open) ls memory/todo\ -\ *.md 2>/dev/null # U
npx skillsauth add agenticnotetaking/eidos skills/nextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Aggregate actionable items into a prioritised list.
/eidos:next
Use grep/glob to quickly filter without reading full files. Only read a file when you need detail for presentation.
# Active plans with unchecked actions
grep -rl '\[ \]' memory/plan\ -\ *.md 2>/dev/null
# Open todos (existence = open)
ls memory/todo\ -\ *.md 2>/dev/null
# Unprocessed goodjobs
grep -rl 'status: unprocessed' memory/goodjob\ -\ *.md 2>/dev/null
# Planned items
grep -rn '{{\[!\]' eidos/ 2>/dev/null
# Postponed plan actions
grep -rn '\[p\]' memory/plan\ -\ *.md 2>/dev/null
# Open comments
${CLAUDE_PLUGIN_ROOT}/scripts/open_comments.py --path eidos/ skills/ memory/ --cap 20
These pattern checks are fast — don't read entire files just to check status.
[p] (postponed) actions{{comments}}{[!]} items not yet in a plan[p]) — low priority awareness, not a call to actionUse [[spec - numbered lists - structured selectable output]] format:
1 - Active Plan: [[plan - 2602101614 - migrate mono]]
- 1.1 - Research skill + spec (Phase 3.1)
- 1.2 - Architecture skill + spec (Phase 3.2)
2 - Open Comments
- 2.1 - {{should push auto-commit?}} in spec - push
3 - Planned Items
- 3.1 - {[!] PreToolUse hook} in spec - eidos
4 - Todos
- 4.1 - [[todo - 2602111642 - pull spec from session context hook]]
5 - Postponed
- 5.1 - [p] Add comprehensive error messages (plan - 2602101614 - migrate mono, Phase 4)
Which items to work on?
Run date '+%y%m%d%H%M' to get the current timestamp.
Create memory/next - <timestamp> - <claim>.md (per [[spec - naming - prefixes structure filenames as prefix claim pairs]], e.g. next - 2602141030 - aggregated actionable items.md) with the aggregated list.
Commit.
Route to the appropriate action:
/eidos:plan-continue{{comment}} → use /eidos:refine{[!]} item → suggest creating a plan or implementing directly/eidos:toeidos to extract pattern, then mark status: processedmemory/next - <timestamp> - <claim>.mdtools
--- tldr: Generate a manim explainer video through staged research → outline → scenes → code → render → merge, with the outline doubling as a plan/state document category: utility --- # /eidos:video Turn a topic (or a folder of wiki-linked md) into a rendered manim video through a fixed pipeline. Pauses after each stage for review by default. Outline doubles as the plan/state document — wiki-linked checklist tracks progress. Full design in [[spec - video skill - outline driven manim pipeline
tools
--- tldr: Surface session status to the human via a native OS notification category: utility --- # /eidos:ping Send a short out-of-band signal to the human — "I'm done", "I have a question", "I hit a wall" — as a native OS notification. The agent picks the moment; the human gets a popup without watching the terminal. ## Setup (macOS, opt-in) This skill is a no-op until the human has installed the **eidos-ping** menubar app and pointed at it in `.eidos-config.yaml`: ```yaml ping_macos: /path
tools
--- tldr: Persist behaviour corrections to CLAUDE.md category: utility --- # /eidos:toclaude Update CLAUDE.md or specs to correct undesired behaviour. ## Usage ``` /eidos:toclaude [description of correction] ``` ## Instructions 1. Understand the correction — what went wrong, what should happen instead 2. Identify the right location: - **`inject/core/*.md`** — plugin rules that apply to all eidos projects (pick the matching section file) - **`inject/feature/*.md`** — rules tied to a c
development
--- tldr: Create persistent plan for multi-step work category: planning --- # /eidos:plan Create a persistent plan file for multi-step work. ## Usage ``` /eidos:plan [brief description] ``` ## Instructions ### 1. Gather Context If the target file already exists with `status: seed`, read it — its content is raw context that seeds the plan. Use the seed's notes, links, and brain dumps to draft phases and actions. Skip clarification questions the seed already covers. Search for related arti