From 85f2870830a4d7ba5e5eac732d3e69dfec038ad1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=86gir=20M=C3=A1ni=20Hauksson?=
 <54936225+sourcehawk@users.noreply.github.com>
Date: Tue, 6 Oct 2026 10:07:24 +0100
Subject: [PATCH 1/2] fix(skills/reporting-a-skill-gap): let the location block
 hold more than one skill

The template said that `## Where in the plugin` holds "exactly these three lines", and the same comment said to repeat the Skill and Section lines when more than one skill is involved. A report about two skills cannot obey both rules. The guidance now asks for one Skill and Section pair for each skill, then one Plugin version line at the end.

Fixes #82

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 skills/reporting-a-skill-gap/templates/skill-gap.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/skills/reporting-a-skill-gap/templates/skill-gap.md b/skills/reporting-a-skill-gap/templates/skill-gap.md
index 56d18f6..e46db69 100644
--- a/skills/reporting-a-skill-gap/templates/skill-gap.md
+++ b/skills/reporting-a-skill-gap/templates/skill-gap.md
@@ -25,13 +25,13 @@ When you comment on an existing issue instead of filing a new one, the comment h
 ## Where in the plugin
 
 <!--
-Exactly these three lines:
+One Skill and Section pair for each skill, then one Plugin version line:
 
 - Skill: `feature-dev-workflow:<name>`
 - Section: `<the heading, copied from the installed SKILL.md, with its # marks>`
 - Plugin version: `<version from .claude-plugin/plugin.json>`
 
-When the failure is that a skill did not trigger, the section is `description` (the frontmatter trigger text). When more than one skill is involved, repeat the Skill and Section lines for each.
+When the failure is that a skill did not trigger, the section is `description` (the frontmatter trigger text). When more than one skill is involved, write the Skill and Section pair once for each skill, and the Plugin version line once at the end.
 -->
 
 <!-- optional -->

From 89199657d7f531e519871074a7e6686923a1dd71 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=86gir=20M=C3=A1ni=20Hauksson?=
 <54936225+sourcehawk@users.noreply.github.com>
Date: Tue, 6 Oct 2026 11:27:53 +0100
Subject: [PATCH 2/2] fix(skills/reporting-a-skill-gap): give the title and
 reproduction a shape for two skills

The title rule named "the skill" in the singular, and `## Reproduction` gave no shape for a gap that spans an agent and the agents it dispatches. Test runs on a two-skill report guessed at both. One wrote a predicate that needed a second run which the scenario did not describe. The title rule now names each skill, joined with "and". The reproduction guidance asks for one scenario for the agent that dispatches, whose predicate checks the dispatch prompts and what the dispatched agents do in the same run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---
 skills/reporting-a-skill-gap/templates/skill-gap.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/skills/reporting-a-skill-gap/templates/skill-gap.md b/skills/reporting-a-skill-gap/templates/skill-gap.md
index e46db69..cbf55c9 100644
--- a/skills/reporting-a-skill-gap/templates/skill-gap.md
+++ b/skills/reporting-a-skill-gap/templates/skill-gap.md
@@ -12,7 +12,7 @@ When you comment on an existing issue instead of filing a new one, the comment h
 
 # <plain-english-title>
 
-<!-- Title rule: a human-readable sentence that names the skill and the failure. Example: "fanning-out-with-worktrees: parallel subagents overwrite each other's files in the shared scratch directory". -->
+<!-- Title rule: a human-readable sentence that names the skill and the failure. Example: "fanning-out-with-worktrees: parallel subagents overwrite each other's files in the shared scratch directory". When more than one skill is involved, name each of them, joined with "and". -->
 
 ## What happened
 
@@ -42,7 +42,7 @@ When the failure is that a skill did not trigger, the section is `description` (
 
 ## Reproduction
 
-<!-- Required. A self-contained scenario that a maintainer can hand to a fresh subagent as a RED baseline. It must run without access to this session or the user's project: every fact the agent needs is written here, in generic terms. -->
+<!-- Required. A self-contained scenario that a maintainer can hand to a fresh subagent as a RED baseline. It must run without access to this session or the user's project: every fact the agent needs is written here, in generic terms. When the gap spans an agent and the agents it dispatches, write one scenario for the agent that dispatches: the Task prompt is the message it receives, the Environment facts name the skill that each dispatched agent follows, and the Failure predicate checks the dispatch prompts and what the dispatched agents do, in the same run. -->
 
 ### Situation