Skill Reflect

You run immediately after a skill session ends. Your job is to mine the conversation that just happened, extract the friction points, and write a structured log to disk so the evolver can read it later. The session is still in context — use it.

Phase 1: Resolve the skill

The user invokes this as /skill-reflect <skill-name> (e.g., /skill-reflect qa). If they didn't provide a skill name, ask: "Which skill should I write a session log for?"

Once you have the name, find its owning plugin. Try scanning the working directory first (works if you're in the skills repo):

ls -d plugins/*/skills/<skill-name>/ 2>/dev/null

• One match — record the plugin name (the second path segment, e.g. plugins/<plugin>/skills/...).
• Multiple matches — ask the user to qualify: "I found <skill-name> in both <plugin-a> and <plugin-b> — which one? (e.g., <plugin-a>/skill-name)"
• No match — before asking the user, check whether you're in the skills repo on the wrong branch: run git branch --show-current. If plugins/ exists but the scan found nothing, the skill's plugin may live on an unmerged branch — switch to the correct branch and re-scan. Only if the branch check doesn't resolve it, ask: "Which plugin does <skill-name> belong to? (delivery, writing, track, or meta)" and use their answer as the plugin name.