fix(commands,workflows): make the planning step read issue comments as authoritative #2404
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -49,6 +49,32 @@ gh issue view {number} --json title,body,labels,comments,state,url,author | |
| - Parse as problem description | ||
| - Note: No GitHub posting (artifact only) | ||
|
|
||
| ### 1.2a Comments outrank the body, and linked issues are part of the input | ||
|
|
||
| An issue body describes a problem as first understood. Comments are where it gets | ||
| **decided**. Treat them with that authority: | ||
|
|
||
| - **Read every comment before planning anything.** A later maintainer comment | ||
| supersedes the body wherever the two disagree — the body is the opening | ||
| position, not the specification. | ||
| - **A comment stating a decision IS the specification.** If one settles a shape, | ||
| a field list, an interface, or an explicit "do X, not Y", implement that. Do | ||
| not re-derive the choice from the body and do not average the two. | ||
| - **Follow linked issues.** When the body or a comment points at another issue | ||
| (`#1234`, or a full URL) for a decision, design, or contract, fetch it and read | ||
| its comments too: | ||
| ```bash | ||
| gh issue view 1234 --json title,body,comments,state,url | ||
| ``` | ||
|
Comment on lines
+63
to
+68
Contributor
There was a problem hiding this comment. 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win 🧩 Analysis chain🏁 Script executed: #!/bin/bash
set -euo pipefail
echo "== changed files/stat =="
git diff --stat || true
echo "== target snippets =="
for f in .archon/commands/defaults/archon-investigate-issue.md .archon/commands/defaults/archon-create-plan.md; do
if [ -f "$f" ]; then
echo "--- $f"
nl -ba "$f" | sed -n '45,80p'
else
echo "missing $f"
fi
done
echo "== gh issue view occurrences =="
rg -n "gh issue view|url parsing|repo " .archon/commands/defaults/archon-*.md || true
echo "== all linked-issue guidance occurrences =="
rg -n "Follow linked issues|follow the link|gh issue view" .archon/commands/defaults || trueRepository: coleam00/Archon Length of output: 299 🌐 Web query:
💡 Result: The GitHub CLI (gh) Citations:
🏁 Script executed: #!/bin/bash
set -euo pipefail
echo "== changed files/stat =="
git diff --stat || true
for f in .archon/commands/defaults/archon-investigate-issue.md .archon/commands/defaults/archon-create-plan.md; do
if [ -f "$f" ]; then
echo "--- $f"
awk '{printf "%6d %s\n", NR, $0}' "$f" | sed -n '45,80p'
else
echo "missing $f"
fi
done
echo "== relevant occurrences in target files =="
grep -nE "Follow linked issues|gh issue view|owner/repo|`#1234`|issue URL|URL" .archon/commands/defaults/archon-investigate-issue.md .archon/commands/defaults/archon-create-plan.md || true
echo "== broader linked-issue guidance locations =="
grep -RInE "Follow linked issues|follow the link|gh issue view|owner/repo|`#1234`" .archon/commands/defaults || trueRepository: coleam00/Archon Length of output: 6593 Preserve the linked issue repository when the reference is a full URL.
📍 Affects 2 files
🤖 Prompt for AI Agents |
||
| One level of following is enough — do not spider the whole graph. | ||
| - **If the body and a decision conflict, say so in your investigation artifact** | ||
| and state which you followed. A silent choice is the failure mode here. | ||
|
|
||
| This is not hypothetical. On 2026-08-03 a run implemented an issue's body while a | ||
| maintainer comment on that same issue — fetched, present in the input, posted 16 | ||
| seconds before the run started — specified a different shape entirely. The PR was | ||
| discarded. The data was there; nothing said it outranked the body. | ||
|
|
||
| ### 1.3 Classify Issue Type | ||
|
|
||
| | Type | Indicators | | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Classify GitHub issue inputs before the free-form branch.
The input table above lists only PRD, document, and free-form inputs. It has no GitHub issue number or URL case. Therefore,
1234or a GitHub issue URL can enter Phase 0.3 and skip this new comment-fetch path. Add number and URL cases beforeFree-form text, matching.archon/commands/defaults/archon-investigate-issue.mdLines 30-32.🤖 Prompt for AI Agents