From d978a365345af075789f1ab0dccf2ab64ef5e4af Mon Sep 17 00:00:00 2001 From: Lee Overy Date: Mon, 27 Jul 2026 14:09:19 +0100 Subject: [PATCH] fix(investigation): the interview starts from the carrier, not over it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The guard fix beneath this made the symptom interview run for work shaped in discovery. The first walk through it showed what the arm does when it finally executes: three of six questions put back to the user things the carrier had already answered and initialisation had already written into the file — asking what the user sees when it crashes, against a Symptoms section already reading "No error surfaces to the user — the page just fails." That is what the prose literally said to do. The Otherwise arm loaded the question bank with no instruction to read the file it had just seeded, and the question bank has no such instruction either. The don't-re-ask rule lived in the entry skill; the process skill lost it at the handoff. The arm was unreachable for carrier-shaped work until the guard fix, so the gap has been there as long as the arm has — it just never ran. Step 3 now reads what the Symptoms section already holds before asking: the seed is the user's own account, questions go to what it does not answer, and thin answers get confirmed rather than re-asked. Found by the investigation-gathers-symptoms case two commits below, on its first run. Co-Authored-By: Claude Opus 5 --- skills/workflow-investigation-process/SKILL.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/skills/workflow-investigation-process/SKILL.md b/skills/workflow-investigation-process/SKILL.md index 5411525fe..2971e9e10 100644 --- a/skills/workflow-investigation-process/SKILL.md +++ b/skills/workflow-investigation-process/SKILL.md @@ -151,6 +151,8 @@ An earlier session already interviewed the user — don't re-interview. Fold in > messages, affected areas, and environmental context. ``` +Read what the Symptoms section already holds — initialisation seeded it from the carrier, and that is the user's own account. Ask what it does not answer, and confirm rather than re-ask where it is thin. Putting a question they have already answered back to them reads as not having listened. + Load **[symptom-gathering.md](references/symptom-gathering.md)** and use its questions to gather symptoms from the user. Document symptoms in the investigation file as you gather them. Commit after each significant addition.