Plan vault restructuring from config changes. Compares config.yaml against derivation.md, identifies dimension shifts, shows restructuring plan, executes on approval.
SkillScore43Maintained
Automatic
◆Knowledge Management pack
Last verified 8/12/2026
What it changes
Passed 6 of 13 test cases with the skill, and 2 of 13 without it.
Without skill13%
With skill43%
Checks it passed that the model alone missed
Schedules the /reduce skill for regeneration.
Rejects turning off session capture in active system settings.
Scans internal wiki links to confirm zero dangling target references.
and 12 more in the full report
10 fixed0 passed either way10 still failing3 broke
Pass-rate lift
+30 pp
Tokens
+195%
Agent turns
0%
Response time
-30%
Model gemini-3.6-flashMeasured 8/12/2026v110 of 23 cases passed with skill · 13 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Before generating updated skills or updating context file sections in Phase 4, what mapping must be read from `ops/derivation-manifest.md`?
What was checked, without and with the skill
Checked
Without skill
With skill
Reads customized folder and note type terms from vocabulary definitions in derivation-manifest.md.
Missed
Passed
Applies workspace vocabulary transformations during skill regeneration.
Missed
Passed
case-18 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md436 linessingle file
Runtime Configuration (Step 0 — before any processing)
Read these files to configure domain-specific behavior:
Use vocabulary.note / vocabulary.note_plural for note type references
Use vocabulary.topic_map / vocabulary.topic_map_plural for MOC references
Use vocabulary.inbox for the inbox folder name
ops/config.yaml — current live configuration (the "after" state)
ops/derivation.md — original derivation record (the "before" state)
If these files don't exist, report error: "Cannot refactor without both ops/config.yaml and ops/derivation.md. These files establish the baseline and current configuration."
EXECUTE NOW
INVARIANT: /refactor never executes without approval. The plan is always shown first.
Target: $ARGUMENTS
Parse immediately:
If target is empty: detect ALL config changes and plan restructuring
If target names a specific dimension (e.g., "granularity", "organization"): focus on that dimension only
If target is --dry-run: show plan without asking for approval
Execute these phases:
Detect changes between config.yaml and derivation.md
Plan restructuring for each changed dimension
Show the plan with affected artifacts and risk assessment
Update old notes with new connections. The backward pass that /reflect doesn't do. Revisit existing notes that predate newer related content, add connections, sharpen claims, consider splits. Triggers on "/reweave", "/reweave [note]", "update old notes", "backward connections", "revisit notes".