From 7897ba31307ac066c52b55ad175cad8f3941713e Mon Sep 17 00:00:00 2001 From: Yordis Prieto Date: Mon, 14 Sep 2026 13:55:01 -0400 Subject: [PATCH 1/2] fix(trogonstack-ask): avoid unnecessary session naming interruptions Signed-off-by: Yordis Prieto --- plugins/trogonstack-ask/skills/ask-question/SKILL.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/plugins/trogonstack-ask/skills/ask-question/SKILL.md b/plugins/trogonstack-ask/skills/ask-question/SKILL.md index 1028397..5eff981 100644 --- a/plugins/trogonstack-ask/skills/ask-question/SKILL.md +++ b/plugins/trogonstack-ask/skills/ask-question/SKILL.md @@ -38,7 +38,11 @@ You are a critical thinking partner, not a yes-machine. If my answer reveals a f ## Session persistence -Before asking the first question, ask the user for a name for the session and create `.qa.md` at the root of the project immediately (use `git rev-parse --show-toplevel` to locate the root). Persistence is mandatory — every question MUST be recorded in this file as the conversation progresses. +Choose a short, descriptive kebab-case session name from the topic, goal, and available conversation context. Honor a name the user has already provided. Do not ask the user to choose or approve a filename. + +Only if the topic cannot be inferred, ask one question about the missing topic or goal, then derive the name from the answer. This context clarification is the only question allowed before creating the session file; record it and its answer as the first entry immediately after creating the file. + +Create `.qa.md` at the project root before asking any further questions (use `git rev-parse --show-toplevel` to locate the root). Follow explicit user or repository instructions for the location and filename suffix. Persistence is mandatory: every question MUST be recorded in this file as the conversation progresses. For each exchange, append an entry using this exact format: From 7807287de4ad120121f5b3d02a4b77bf33cf51aa Mon Sep 17 00:00:00 2001 From: Yordis Prieto Date: Mon, 14 Sep 2026 14:25:00 -0400 Subject: [PATCH 2/2] fix(trogonstack-ask): preserve transcripts across repeated sessions Signed-off-by: Yordis Prieto --- plugins/trogonstack-ask/skills/ask-question/SKILL.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/plugins/trogonstack-ask/skills/ask-question/SKILL.md b/plugins/trogonstack-ask/skills/ask-question/SKILL.md index 5eff981..a5c7463 100644 --- a/plugins/trogonstack-ask/skills/ask-question/SKILL.md +++ b/plugins/trogonstack-ask/skills/ask-question/SKILL.md @@ -42,7 +42,11 @@ Choose a short, descriptive kebab-case session name from the topic, goal, and av Only if the topic cannot be inferred, ask one question about the missing topic or goal, then derive the name from the answer. This context clarification is the only question allowed before creating the session file; record it and its answer as the first entry immediately after creating the file. -Create `.qa.md` at the project root before asking any further questions (use `git rev-parse --show-toplevel` to locate the root). Follow explicit user or repository instructions for the location and filename suffix. Persistence is mandatory: every question MUST be recorded in this file as the conversation progresses. +Use `.qa.md` at the project root (use `git rev-parse --show-toplevel` to locate the root). Follow explicit user or repository instructions for the location and filename suffix. + +For a new session, check the final target path after applying those location and suffix rules. If it already exists, leave it unchanged and automatically try `-2`, `-3`, and so on with the same location and suffix until an unused path is found. Do not ask for a different filename. Never overwrite an existing transcript. + +Reuse an existing transcript only when the user explicitly asks to resume that session; read it before appending new exchanges. Create the new file or open the transcript being resumed before asking any further questions. Persistence is mandatory: every question MUST be recorded in this file as the conversation progresses. For each exchange, append an entry using this exact format: