docs(skills): add staleness check + low-resolution issue template - #44
Merged
Merged
Conversation
Mirrors two improvements that landed in ~/.claude/skills/ during recent streamlib work back into the canonical repo copies: amos-next: - New Step 2.5 "Verify against current state (staleness check)" that requires the picker to audit the issue body against current code + current issue state before announcing a plan. Picker updates the issue body in place (with strike-throughs and reasoning preserved) when load-bearing claims have gone stale, then announces a fresh plan that supersedes the body where evidence has shifted. - Step 3 announcement template revised to lead with "Goal" + "Refined plan (after Step 2.5 staleness check)" + "What changed vs. issue body" rather than treating the issue body as authoritative. - Step 5 reframes scope as "the goal as refined in Step 3's plan," not a literal reading of every checkbox in the issue body. - Also pulls in the pre-PR review gate (Step 7) that was added in ~/.claude but hadn't been mirrored back yet — same content already in use locally, see streamlib PR #540. amos-file: - "Amos default template" rewritten to be low-resolution by default. Issues capture goals not pre-implementation plans; the picker produces the high-resolution plan at pickup time. Specifics in the issue body just create staleness for the next agent to clean up. - AI Agent Notes default to "None." with examples of content that does and does not belong (search-fuel and ruled-out approaches with reasoning belong; ordering suggestions and file paths don't — they go stale fast). Why: streamlib issue #528 surfaced repeated staleness in issue bodies (impl issues already filed, dependency edges already wired, "defects" already fixed at compile time). The pickup-research loop catches that automatically; the lower-resolution template prevents new issues from being filed with the same staleness problem baked in. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
amos-next: new Step 2.5 "Verify against current state (staleness check)" — picker audits the issue body against current code + current issue state before announcing a plan, updates the body in place with strike-throughs when load-bearing claims have gone stale, and announces a fresh plan that supersedes the body where evidence has shifted. Step 3 announcement, Step 5 scope, and Step 7 pre-PR review gate updated to match.amos-file: default template rewritten to be low-resolution. Issues capture goals, not pre-implementation plans; the picker produces the high-resolution plan at pickup time. AI Agent Notes default to "None." with explicit examples of what does and does not belong (search-fuel + ruled-out approaches with reasoning belong; ordering suggestions and file paths don't).Why
streamlib issue #528 surfaced repeated staleness in issue bodies — impl issues already filed, dependency edges already wired, "defects" already fixed at compile time. The pickup-research loop catches that automatically, and the lower-resolution template prevents new issues from being filed with the same staleness problem baked in. See tatolab/streamlib#540 for the matching streamlib-side changes (CLAUDE.md "Editing markdown documentation" rules, "Issues are goals, not specs" reframing in Work Tracking, lower-resolution
docs/issue-template.md).Test plan
Follow-ups
None.
🤖 Generated with Claude Code