Evolve PKM specialists from friction observations to autonomous subagents. Use when the ideas system fails you, when retrieval breaks, or when synthesis falls short.
Evolve specialists through maturity levels based on real PKM friction, not theory.
Generic PKM advice is everywhere. Real value comes from specialists adapted to YOUR:
This skill manages the evolution from friction observation to autonomous subagent.
L0: Observation
↓ (repeats 3+ times)
L1: Proposal
↓ (consulted/refined 5+ times)
L2: Custom Specialist
↓ (critical in 10+ interactions)
L3: Subagent
Key insight: Low threshold to observe, high threshold to promote. Let usage refine the scope.
Before graduating proposal → specialist, validate ALL three:
✅ 1. Requires JUDGMENT, not information
Test: Can coding agent with Read/Grep solve this? NO
✅ 2. Is RECURRING, not one-off
Test: Happens every time you [capture/search/synthesize]? YES
✅ 3. Has CONCRETE evidence
Test: Are there specific moments where this friction occurred? YES
One-sentence test:
"This specialist helps me [do what] by knowing [what about me] whenever I [when]."
If you can't complete that sentence confidently → not ready.
Each command has detailed reference documentation:
observe — Log a PKM frictionReference: references/observe.md
Record when the ideas/notes system failed you.
Usage:
/vaults-grow-specialist observe
/vaults-grow-specialist observe --type retrieval
Output: Entry added to .syner/ops/vaults-grow-specialist/observations.md
review — Detect patterns in observationsReference: references/review.md
Analyze accumulated observations, detect recurring patterns, propose specialists.
Usage:
/vaults-grow-specialist review
/vaults-grow-specialist review --threshold 2
Output: Proposals for new specialists based on evidence
refine — Improve a proposalReference: references/refine.md
Enhance proposal based on real usage, add concrete examples from your notes.
Usage:
/vaults-grow-specialist refine retrieval-optimizer
Output: Updated proposal with better scope/examples
graduate — Proposal → Custom SpecialistReference: references/graduate.md
Promote mature proposal to custom specialist.
Usage:
/vaults-grow-specialist graduate retrieval-optimizer
Validates: 3 conditions + threshold
Output: File in .syner/artifacts/vaults-grow-specialist/specialists/
promote — Custom Specialist → SubagentReference: references/promote.md
Elevate critical specialist to autonomous subagent.
Usage:
/vaults-grow-specialist promote retrieval-optimizer
Validates: Criticality threshold
Output: File in agents/ with full frontmatter
audit — Detect redundancyReference: references/audit.md
Find overlapping specialists, mark deprecated generics.
Usage:
/vaults-grow-specialist audit
/vaults-grow-specialist audit --mark-deprecated
Output: Consolidation recommendations
status — View evolution stateReference: references/status.md
Show current state of all specialists at all levels.
Usage:
/vaults-grow-specialist status
/vaults-grow-specialist status retrieval-optimizer
Output: Dashboard of maturity levels and metrics
.syner/
├── ops/
│ └── vaults-grow-specialist/
│ ├── observations.md # L0: Raw observations log
│ ├── tracking.md # Metrics for all levels
│ ├── proposals/ # L1: Immature proposals
│ │ ├── retrieval-optimizer.md
│ │ └── voice-processor.md
│ └── archive/ # Archived proposals/specialists
│
└── artifacts/
└── vaults-grow-specialist/
└── specialists/ # L2: Mature custom specialists
└── retrieval-optimizer.md
apps/vaults/agents/
retrieval-optimizer.md # L3: Autonomous subagents (final destination)
Common categories of PKM friction to observe:
| Type | Description | Example |
|---|---|---|
retrieval | Can't find what you know exists | "I wrote about X but can't find it" |
capture | Friction in getting ideas into notes | "Voice memo never processed" |
linking | Missing connections between ideas | "These should have been connected" |
synthesis | Can't combine into insights | "Had all pieces, couldn't see pattern" |
processing | Captured but never digested | "Inbox overflowing, nothing processed" |
vocabulary | Different words for same concept | "Called it X here, Y there" |
Current settings (high, mostly manual):
{
observationToProposal: 3, // 3 observations → propose
proposalToSpecialist: 5, // 5 consultations → graduate
specialistToSubagent: 10, // 10 interactions affected → promote
autoApprove: false, // Always ask confirmation
}
Future: Lower thresholds, increase automation as confidence grows.
references/{command}.md)Load proportionally based on command:
observe: Just observations filereview: Observations + trackingrefine/graduate: Proposal + related notes + trackingpromote: Specialist + full usage dataaudit: All specialists + all genericsThis skill operates within /syner-boundaries:
| Boundary | Application |
|---|---|
| Suggest, Don't Enforce | Propose promotions, require confirmation |
| Concrete Output | Deliver actual specialist files, not suggestions |
| Evidence-Based | Never speculate, always cite real friction |
| Route, Don't Hoard | Graduates specialists, doesn't try to do their job |
Self-check before promotion:
Direct. Evidence-based. PKM-native.
Speak in maturity levels:
When promoting, cite concrete evidence:
| Skill | Relationship |
|---|---|
find-ideas | Specialists improve idea discovery |
find-links | Specialists improve connection detection |
track-idea | Specialists improve evolution tracking |
grow-note | Specialists improve graduation decisions |
This skill doesn't replace them — it evolves specialists that make them work better for YOU.
This skill shares philosophy with design-grow-specialist:
The difference: design observes UI/component decisions, notes observes PKM/ideas friction.
Related skills: /grow-note, /find-ideas, /design-grow-specialist
Related agents: vaults, dev