Skip to content

Remove stale references to removed tracing sections from templates #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
londey merged 1 commit into from
Mar 6, 2026
Merged

Remove stale references to removed tracing sections from templates #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions install_syskit.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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

Expand Down Expand Up @@ -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"

Expand Down
2 changes: 1 addition & 1 deletion templates/claude/commands/syskit-trace.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"

Expand Down
2 changes: 1 addition & 1 deletion templates/syskit/prompts/plan-extract.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
1 change: 0 additions & 1 deletion templates/syskit/ref/requirement-format.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down