docs: repoint CHK008/CHK018 to the surviving spec section#121
Conversation
- **Replace** the dangling references to Spec section 輸入與生成規則 in CHK008 and CHK018, because spec-template v1.6.0 (PR #120) converted that section into a template-internal HTML comment that no longer appears in spec instances - **Anchor** both items to Spec section 已釐清事項 instead, the surviving section that records clarify conclusions and intentional deviations - **Ship** separately from PR #120 because adding a sixth file there would exceed the 5-file PR limit (same split pattern as PR #118 → #119) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR correctly fixes the dangling section references left by PR #120. The changes update CHK008 and CHK018 to reference §已釐清事項 (the surviving section) instead of §輸入與生成規則 (which was converted to a template-internal HTML comment). The version bump to 1.9.1 and changelog entry are appropriate for a PATCH-level reference fix. No blocking issues identified.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the checklist template (.specify/templates/checklist-template.md) to version 1.9.1. Specifically, it updates the referenced sections for CHK008 and CHK018 from 'Spec §輸入與生成規則' to 'Spec §已釐清事項' to align with spec-template v1.6.0, and adds a corresponding entry to the changelog. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e90b784133
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - [ ] CHK007 功能需求是否與每個使用者故事的驗收情境一致？[Consistency, Spec §功能需求] | ||
| - [ ] CHK008 原型、規格與需求來源的差異是否有記錄，而非靜默衝突？[Consistency, Spec §輸入與生成規則] | ||
| - [ ] CHK008 原型、規格與需求來源的差異是否有記錄，而非靜默衝突？[Consistency, Spec §已釐清事項] |
There was a problem hiding this comment.
When /speckit.checklist is run against an existing feature spec, these references no longer resolve: all 16 current specs/**/spec.md files are explicitly grandfathered with ## 輸入與生成規則 and none has a ## 已釐清事項 heading (for example, specs/task-management/013-task-new/spec.md:12). The checklist command requires traceability references to existing spec sections, so CHK008 and CHK018 can now direct reviewers to a nonexistent heading for every existing spec. Use a backward-compatible reference or migrate the grandfathered specs before repointing the template.
Useful? React with 👍 / 👎.
1 participant
Purpose
Fix the dangling section references in checklist-template CHK008 and CHK018 left behind by the What/How separation in PR #120.
Reason
spec-template v1.6.0 (PR #120) converted
§輸入與生成規則into a template-internal HTML comment, so spec instances no longer contain that section. CHK008 and CHK018 still anchored to it, which would send checklist authors to a section that does not exist. This could not ride along in PR #120 because a sixth file would exceed the 5-file PR limit (same split pattern as #118 → #119).Result
Spec §輸入與生成規則Spec §已釐清事項Spec §輸入與生成規則Spec §已釐清事項§已釐清事項is the surviving section that records clarify conclusions and intentional deviations, which is exactly what both items ask reviewers to verify.Changed Files
.specify/templates/checklist-template.mdTest Plan
grep "輸入與生成規則" .specify/templates/checklist-template.mdreturns no checklist-item references (only the changelog entry describing this fix)§已釐清事項exists in spec-template v1.6.0 as a landed section (verified at spec-template L32)Impact Scope
Related
Follow-up to #120
🤖 Generated with Claude Code