skills/brainstorm/SKILL.md
--- tldr: Brainstorm ideas around a topic and capture them in a structured file category: planning --- # /eidos:brainstorm Generate and structure ideas around a topic. Starts broad, then clusters and selects standouts. ## Usage ``` /eidos:brainstorm [topic or question] ``` ## Instructions ### 1. Orient If the topic is broad or vague, use AskUserQuestion to focus: - What are we brainstorming about? - Any constraints or directions to favour? - What would a good outcome look like? If the to
npx skillsauth add agenticnotetaking/eidos skills/brainstormInstall 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.
Generate and structure ideas around a topic. Starts broad, then clusters and selects standouts.
/eidos:brainstorm [topic or question]
If the topic is broad or vague, use AskUserQuestion to focus:
If the topic is already clear, confirm and proceed.
Search for related artifacts:
eidos/ that touch the same domainmemory/Note relevant context — it seeds better ideas.
Read the template: [[template - brainstorm - structured ideation around a topic]]
Run date '+%y%m%d%H%M' to get the current timestamp.
Create memory/brainstorm - <timestamp> - <claim>.md (per [[spec - naming - prefixes structure filenames as prefix claim pairs]], e.g. brainstorm - 2602101400 - alternative auth approaches.md) with the Seed filled in.
Commit immediately.
Produce an initial batch of ideas — aim for breadth. Include both obvious and unconventional options. Write them to the Ideas section as you go.
Then ask the user:
Add the user's ideas and any new ones sparked by the conversation. Update the file and commit.
Group ideas into themed clusters. Let themes emerge from the ideas — don't impose categories.
Highlight standouts with brief rationale. Update the file and commit.
Brainstorm captured: [[brainstorm - <timestamp> - <claim>]]
Options:
1 - Create specs from standouts with /eidos:spec
2 - Plan implementation with /eidos:plan
3 - Create a decision file to choose between options
4 - Done for now
memory/brainstorm - <timestamp> - <claim>.mdactive, set to complete when donetools
--- 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