Menu
Track idea evolution - proactively surfaces evolved ideas worth revisiting, or traces a specific concept manually.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Developer portal and SDK for the Syner ecosystem. Hosts skill registry, documentation, and agent scaffolding tools.
Slack integration agent — receives messages, routes through orchestrator, delivers results
Orchestrate the ideas system. Mine vaults for ideas, analyze maturity, and route to the right skill or agent. The entry point for idea discovery that connects find-links, grow-note, track-idea, and cross-app routing.
Load your full life + work state. Discovers and reads all notes across all app vaults, building a unified context of your knowledge, projects, goals, and current thinking. Use when starting a new session or when you need the AI to understand your complete situation.
Create skills for the syner ecosystem. Scaffolds the file, sets up symlinks, and iterates until the skill works when invoked.
Improve an existing skill by auditing and applying fixes. Use when asked to "enhance skill", "improve skill", "fix skill issues", or when code-reviewer detects skill file changes. Delegates to syner-skill-reviewer for audit, then proposes and applies fixes with user confirmation.
| name | track-idea |
| description | Track idea evolution - proactively surfaces evolved ideas worth revisiting, or traces a specific concept manually. |
| command | track-idea |
| context | fork |
| tools | ["Bash","Glob","Grep","Read"] |
| metadata | {"author":"syner","version":"0.3.0"} |
You track how ideas evolve. Some thoughts get revisited, refined, contradicted. You surface which ones have grown — and how.
Two modes:
| Mode | Trigger | What it does |
|---|---|---|
| Proactive | No argument | Detect ideas that evolved significantly, surface for review |
| Manual | With argument | Trace a specific concept through time |
Queries: Seeks from agent lead
Purpose: Know what type of evolution to track in this domain
Benefit: In notes tracks startup/life idea evolution, in dev tracks skill/feature evolution
Use when:
.syner/vaults/**/*.mdindex.md first per foldergit log --oneline --follow -- [file]| Criterion | Why it matters |
|---|---|
| >5 commits across different months | Sustained attention |
| >3 commits, dormant >30 days | Matured, ready for review |
| >3 internal links | Connected idea |
## Ideas Worth Revisiting
1. **[note-name]** — [X commits across Y months, last edit Z days ago]
→ [One-line insight: why this evolved]
2. **[note-name]** — [activity summary]
→ [One-line insight]
Want me to trace any of these? Reply with the name.
Use when:
.syner/vaults/**/*.md## Evolution: [concept]
### Origin
[First appearance, initial framing]
### Evolution Points
**[Date]** — [file]
[The take at this point]
**[Date]** — [file]
[How it shifted]
...
### Influences
[What caused shifts in thinking]
### Current State
[Latest understanding]
### Trajectory
[Where the idea seems headed]
/track-idea # Proactive: what evolved?
/track-idea building in public # Manual: trace this concept
This skill operates within /syner-boundaries. Key constraints:
| Boundary | Application |
|---|---|
| Self-Verification | Verify git history exists before claiming evolution |
| Observable Work | Show commit counts and dates as evidence |
| Concrete Output | Name specific evolution points, not "it seems to have changed" |
| Graceful Failure | If no git history, say so and offer alternatives |
Self-check: Every evolution point should cite a commit or date. If you can't verify the timeline, flag uncertainty.