feat(retro): capture AAM tooling findings to HLPM inbox - #198
Merged
Conversation
Sprint retros sometimes surface findings about AIAgentMinder itself (platform-specific script failures, agent misbehavior, workflow friction) rather than the project under sprint. These previously died in the retro report — there was no formal capture channel, and auto-filing GitHub issues is wrong for a public plugin: findings are often environment- specific and would spam the upstream tracker from every user's retros. bin/hlpm-finding.sh follows the hlpm-ping.sh opt-in contract: it appends a structured JSONL record to $HLPM_DIR/tooling-findings.jsonl and is a silent no-op without HLPM_DIR, so non-HLPM users see no behavior change. Unlike events.jsonl the inbox is never trimmed — findings persist until the user's HLPM /findings triage disposes them (promote to AAM backlog, deliberately escalate to a GitHub issue, or dismiss). The retrospective skill (new Step 5) and sprint-retro agent now classify findings into project vs tooling and route each tooling finding through the script, with environment detail included so centralized triage can judge universal vs environmental. Co-Authored-By: Claude Fable 5 <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
Sprint retros sometimes surface findings about AIAgentMinder itself (platform-specific script failures, agent misbehavior, workflow friction) rather than the project under sprint. These previously died in the retro report -- there was no formal capture channel. Auto-filing GitHub issues here would be wrong for a public plugin: findings are often environment-specific and would spam this tracker from every user's retros.
Changes
bin/hlpm-finding.sh-- new capture script following thehlpm-ping.shopt-in contract: appends a structured JSONL record (type, severity, summary, environment detail, repo, branch, sprint, AAM version) to$HLPM_DIR/tooling-findings.jsonl; silent no-op withoutHLPM_DIR, loud arg-validation failures once the channel exists. Unlikeevents.jsonl, the inbox is never trimmed -- findings persist until the user's HLPM/findingstriage disposes them (promote to AAM backlog, deliberately escalate to a GitHub issue, or dismiss).skills/retrospective/SKILL.md-- new Step 5 classifies findings into project vs tooling and routes each tooling finding through the script; report template lists tooling findings so they stay visible without HLPM.agents/sprint-retro.md-- process step + output contract item mirroring the skill.tests/hlpm-finding.test.js(gating, capture, JSON escaping, validation; 14 cases) plus a content assertion inphase-agents-pr-retro.test.jsthat retros never auto-file GitHub issues.Test plan
node --test tests/hlpm-finding.test.js tests/phase-agents-pr-retro.test.js-- 25/25 pass locally under git-bash🤖 Generated with Claude Code