From cf6cb1287f94ac047772a708691f1bdf0a24fb75 Mon Sep 17 00:00:00 2001
From: song-chaeyoung <153435389+song-chaeyoung@users.noreply.github.com>
Date: Fri, 10 Apr 2026 21:54:28 +0900
Subject: [PATCH] docs: clarify /speckit.clarify persistence timing

Clarify that accepted answers are first recorded in working memory and then passed to the integration step below for per-integration persistence.

This preserves the intended incremental-save flow while removing the conflict between step 4's earlier "do not yet write to disk" wording and step 5's instruction to save after each integration.
---
 templates/commands/clarify.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/templates/commands/clarify.md b/templates/commands/clarify.md
index d6d6bbe91..fd8cf5908 100644
--- a/templates/commands/clarify.md
+++ b/templates/commands/clarify.md
@@ -161,7 +161,7 @@ Execution steps:
        - If the user replies with "yes", "recommended", or "suggested", use your previously stated recommendation/suggestion as the answer.
        - Otherwise, validate the answer maps to one option or fits the <=5 word constraint.
        - If ambiguous, ask for a quick disambiguation (count still belongs to same question; do not advance).
-       - Once satisfactory, record it in working memory (do not yet write to disk) and move to the next queued question.
+       - Once satisfactory, record it in working memory and immediately hand it to the integration step below; persist it to disk there after each integration before continuing to the next queued question.
     - Stop asking further questions when:
        - All critical ambiguities resolved early (remaining queued items become unnecessary), OR
        - User signals completion ("done", "good", "no more"), OR