insight-skill-gap

# /skill-gap Identify gaps in the skill library based on recent implementation work — propose new skills or updates to existing ones. > **Structured execution spec:** [`protocol.yon`](protocol.yon). Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the `@STAMP` date. > **Skill Discovery Protocol — ensures reusable patterns don't stay buried in implementation code.** ## Phase 1 — Recent Work Scan 1. **Gather recent context** — conversation history, changed files, new patterns introduced. Summarize: what was built, which libraries/frameworks were used, what novel patterns emerged. 2. **Load skill index** — read the current skill index to know what already exists before analyzing gaps. ## Phase 2 — Gap Analysis Cross-reference patterns from Phase 1 against the skill index. Classify each pattern: - **(A) Skill exists and covers it** — no action - **(B) Skill exists but is incomplete** — propose update; specify which sections are missing or outdated - **(C) No skill exists** — evaluate against new-skill criteria below **Criteria for a new skill:** - Pattern is reusable (used 2+ times, or clearly will be) - Pattern involves non-obvious decisions or gotchas - Pattern spans multiple files or concepts **Gate:** gap analysis must be documented before proceeding. ## Phase 3 — Skill Proposals For each gap, draft a skill specification: - **Skill name** — domain-prefix convent...