From 75ab6b0b9410ab9f6a9611adb563ba57ef2237be Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 5 Mar 2026 22:19:04 +0000 Subject: [PATCH] Remove stale references to removed tracing sections from templates After switching to single-direction tracing, some template files still referenced removed sections (Allocated To, Verified By, unit test listing). - requirement-format.md: Remove "Allocate to design units" guidance - syskit-trace.md: Update "Verified By" section reference to reverse lookup wording - plan-extract.md: Remove "design unit" from test file source reference (only VER docs have Test Implementation now) - Regenerate install_syskit.sh https://claude.ai/code/session_01GsTZh8J62TvCTN74zfRw2K --- install_syskit.sh | 5 ++--- templates/claude/commands/syskit-trace.md | 2 +- templates/syskit/prompts/plan-extract.md | 2 +- templates/syskit/ref/requirement-format.md | 1 - 4 files changed, 4 insertions(+), 6 deletions(-) diff --git a/install_syskit.sh b/install_syskit.sh index 40fb462..e1ef938 100755 --- a/install_syskit.sh +++ b/install_syskit.sh @@ -3439,7 +3439,7 @@ You are extracting implementation scope from approved specification changes. 6. For each specification change, identify: - Which source files need modification (from design unit Implementation sections) - - Which test files need modification or creation (from design unit and verification Test Implementation sections) + - Which test files need modification or creation (from verification Test Implementation sections) - Which verification documents need updating if requirements or design unit behavior changed - Dependencies between changes (what must be done first) - How to verify the change was implemented correctly @@ -3933,7 +3933,6 @@ Every requirement must use the condition/response pattern: - **SHALL** = mandatory, **SHOULD** = recommended, **MAY** = optional - Reference interfaces with `INT-NNN` -- Allocate to design units with `UNIT-NNN` ## Quality Criteria @@ -5162,7 +5161,7 @@ After the tree, provide a brief coverage assessment: 1. **Trace completeness** — Flag any sections that are empty or contain only placeholders (TBD, None, etc.). For example: - A requirement with no "Implemented By" unit → "Not yet implemented by a design unit" - - A requirement with no "Verified By" → "No verification defined" + - A requirement not verified by any VER document → "No verification defined" - A design unit with no "Implements Requirements" → "No requirements traced" - An interface with no provider or consumer → "No units provide or consume this interface" diff --git a/templates/claude/commands/syskit-trace.md b/templates/claude/commands/syskit-trace.md index 3bc414a..68289a3 100644 --- a/templates/claude/commands/syskit-trace.md +++ b/templates/claude/commands/syskit-trace.md @@ -87,7 +87,7 @@ After the tree, provide a brief coverage assessment: 1. **Trace completeness** — Flag any sections that are empty or contain only placeholders (TBD, None, etc.). For example: - A requirement with no "Implemented By" unit → "Not yet implemented by a design unit" - - A requirement with no "Verified By" → "No verification defined" + - A requirement not verified by any VER document → "No verification defined" - A design unit with no "Implements Requirements" → "No requirements traced" - An interface with no provider or consumer → "No units provide or consume this interface" diff --git a/templates/syskit/prompts/plan-extract.md b/templates/syskit/prompts/plan-extract.md index ead40c2..9c417af 100644 --- a/templates/syskit/prompts/plan-extract.md +++ b/templates/syskit/prompts/plan-extract.md @@ -24,7 +24,7 @@ You are extracting implementation scope from approved specification changes. 6. For each specification change, identify: - Which source files need modification (from design unit Implementation sections) - - Which test files need modification or creation (from design unit and verification Test Implementation sections) + - Which test files need modification or creation (from verification Test Implementation sections) - Which verification documents need updating if requirements or design unit behavior changed - Dependencies between changes (what must be done first) - How to verify the change was implemented correctly diff --git a/templates/syskit/ref/requirement-format.md b/templates/syskit/ref/requirement-format.md index 2b1a657..bc60fe1 100644 --- a/templates/syskit/ref/requirement-format.md +++ b/templates/syskit/ref/requirement-format.md @@ -8,7 +8,6 @@ Every requirement must use the condition/response pattern: - **SHALL** = mandatory, **SHOULD** = recommended, **MAY** = optional - Reference interfaces with `INT-NNN` -- Allocate to design units with `UNIT-NNN` ## Quality Criteria