skills/sync/SKILL.md
--- tldr: Bidirectional reconciliation of specs and code category: core --- # /eidos:sync Reconcile specs and code bidirectionally — combines drift analysis with push and pull resolution. ## Usage ``` /eidos:sync # sync all specs vs all code /eidos:sync [file or spec ...] # sync specific files/specs /eidos:sync recent [N] # sync recently changed files ``` ## Instructions ### 1. Run Drift Run the drift analysis (same as `/eidos:drift` with matching args) to
npx skillsauth add agenticnotetaking/eidos skills/syncInstall 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.
Reconcile specs and code bidirectionally — combines drift analysis with push and pull resolution.
/eidos:sync # sync all specs vs all code
/eidos:sync [file or spec ...] # sync specific files/specs
/eidos:sync recent [N] # sync recently changed files
Run the drift analysis (same as /eidos:drift with matching args) to identify all discrepancies.
Do not create a separate drift report file — the sync report will capture findings.
For each item drift found, classify:
Use [[spec - numbered lists - structured selectable output]] format:
Sync found N discrepancies:
Spec-ahead (push):
1 - [claim] in [spec] → code doesn't implement this
2 - [claim] in [spec] → code partially implements this
Code-ahead (pull):
3 - [file:pattern] → not described in any spec
4 - [file:behaviour] → spec is missing this
Conflicts:
5 - [spec] says X, [file] does Y → decision needed
Options:
a - Resolve all (push spec-ahead, pull code-ahead, prompt for conflicts)
b - Select items by number
c - Create drift report only, resolve later
For each selected item:
After each resolution, verify the relevant claims.
For conflicts the user defers:
memory/decision - <timestamp> - <claim>.md with both options documentedRun date '+%y%m%d%H%M' to get the current timestamp.
Create memory/sync - <timestamp> - <claim>.md (per [[spec - naming - prefixes structure filenames as prefix claim pairs]], e.g. sync - 2602141030 - reconciled auth specs and code.md) summarising:
Commit.
eidos/ (pull direction)memory/decision - <timestamp> - <claim>.md for deferred conflictsmemory/sync - <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