Skip to content

Commit 33cf0a0

Browse files
committed
docs(assess): scope dependent-wording review to all affected artifacts
Copilot pointed out that limiting the review to the artifact being edited misses downstream staleness: a clarification in problem.md can leave concept.md wording stale, and decide reads both. The README and the reference page now direct the user to review dependent wording across the affected artifacts, with decision.md staying the command-owned exception. Assisted-by: Claude Code (model: Claude Fable 5, supervised)
1 parent 146332c commit 33cf0a0

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

‎docs/reference/agentic-assessment.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,8 @@ A documented decision to stop is a useful result.
8383
Run each stage once in the usual flow. To resolve clarification markers or a
8484
`needs-clarification` verdict, edit the affected Markdown directly or ask the
8585
agent in free-form chat to incorporate the missing facts. Preserve sources and
86-
confidence tags and review dependent wording in the refined artifacts.
86+
confidence tags, and review dependent wording across the affected artifacts —
87+
a clarification in one artifact can leave a downstream artifact stale.
8788
`decision.md` itself is not revised in place: once the refined artifacts answer
8889
the blocking questions, request reassessment by re-running the decide command,
8990
which rebuilds the scorecard, verdict, and handoff from the updated artifacts

‎extensions/assess/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Resolve them by refining the existing file:
6565
1. **Edit the Markdown directly** (fill in the missing metric, owner, constraint, and so on), or
6666
2. **Ask the agent in free-form chat** to incorporate the missing information into that artifact.
6767

68-
Then ask whether the new information clears the blocker and to update any downstream wording in the refined artifact that depended on it. `decision.md` is the exception — it is rebuilt by the command, not edited in place: once the refined artifacts answer the blocking questions, request reassessment by re-running `/speckit-assess-decide`. It rebuilds the scorecard, rationale, verdict, and handoff from the updated artifacts, and asks before overwriting the previous decision.
68+
Then ask whether the new information clears the blocker and to review and update dependent wording across the affected artifacts — a clarification in `problem.md` can leave downstream `concept.md` wording stale, and `decide` reads both. `decision.md` is the exception — it is rebuilt by the command, not edited in place: once the refined artifacts answer the blocking questions, request reassessment by re-running `/speckit-assess-decide`. It rebuilds the scorecard, rationale, verdict, and handoff from the updated artifacts, and asks before overwriting the previous decision.
6969

7070
When you add evidence, keep the source and confidence tags the research stage already uses (`ASSUMPTION` vs cited claims). Do not invent citations.
7171

0 commit comments

Comments
 (0)