From 919c7ccc4dbf0c1b63358fe6db5d8728d6a2bee3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juan=20Rodr=C3=ADguez?= Date: Wed, 29 Apr 2026 13:17:24 -0300 Subject: [PATCH 1/3] feat(debrief): replace unimplemented ticket stub with issue previews --- skills/debrief/SKILL.md | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/skills/debrief/SKILL.md b/skills/debrief/SKILL.md index 154fdcf..7cb410f 100644 --- a/skills/debrief/SKILL.md +++ b/skills/debrief/SKILL.md @@ -96,11 +96,32 @@ Use the **AskUserQuestion tool** to present next steps: **Options:** 1. **Review and refine**: improve the document using structured review -2. **Create action item tickets**: draft GitHub issues from the action items (not implemented yet — note this) +2. **Generate issue previews**: format action items as ready-to-copy GitHub issue drafts 3. **Done**: debrief complete **If the user selects "Review and refine"** → apply the @refine-approach skill to the document. When refinement is complete, present these options again (without the refine option). +**If the user selects "Generate issue previews"** → read the action items from the written debrief document and render one preview block per item: + +``` +--- +Title: +Label: prevent | detect | respond +Body: + ## Context + Debrief: docs/debriefs/YYYY-MM-DD--debrief.md + Root cause: + + ## What happened + + + ## What to do + +--- +``` + +Render all previews in a single fenced block so the user can copy them. Do not call `gh`, `glab`, or any external CLI — output is display only. + ## Output Summary When complete, display: From bf23188b1fe32223772e39ae1b62589d76c7af4d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juan=20Rodr=C3=ADguez?= Date: Wed, 29 Apr 2026 13:36:49 -0300 Subject: [PATCH 2/3] refactor: add language for code fenced blocks --- skills/debrief/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/debrief/SKILL.md b/skills/debrief/SKILL.md index 7cb410f..48c4b90 100644 --- a/skills/debrief/SKILL.md +++ b/skills/debrief/SKILL.md @@ -103,7 +103,7 @@ Use the **AskUserQuestion tool** to present next steps: **If the user selects "Generate issue previews"** → read the action items from the written debrief document and render one preview block per item: -``` +```text --- Title: Label: prevent | detect | respond From f294f35484a230e110d6cd1138eb4eec62ded0ba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juan=20Rodr=C3=ADguez?= Date: Tue, 19 May 2026 18:27:35 -0300 Subject: [PATCH 3/3] feat(debrief): use project issue templates for issue previews when available --- skills/debrief/SKILL.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/skills/debrief/SKILL.md b/skills/debrief/SKILL.md index 48c4b90..96bc30e 100644 --- a/skills/debrief/SKILL.md +++ b/skills/debrief/SKILL.md @@ -101,7 +101,13 @@ Use the **AskUserQuestion tool** to present next steps: **If the user selects "Review and refine"** → apply the @refine-approach skill to the document. When refinement is complete, present these options again (without the refine option). -**If the user selects "Generate issue previews"** → read the action items from the written debrief document and render one preview block per item: +**If the user selects "Generate issue previews"** → read the action items from the written debrief document, then: + +1. **Check for issue templates**: look for `.github/ISSUE_TEMPLATE/` in the project root. Read every `.yaml` or `.yml` file found there (skip `config.yml`). + +2. **If templates exist**: render one preview block per action item using the most appropriate template. Map each item to a template based on its content (e.g., a missing test or validation gap → bug report; a new monitoring check → feature request; a dependency update or runbook → chore). Populate every required field defined in the template. Include a `Template:` line naming the chosen template file. + +3. **If no templates exist**: fall back to the generic format: ```text ---