Repository navigation
Description
Parent #7575 decides "Retro trends moves to /session-flow:audit-sessions, the all-transcripts source for codify (D50 item 3, D53)", and names this as half of the retro-absorb-and-trends-move slice, which was never filed. The owner approved D53 on 2026-10-13 (poteto-review decision row 53): "move retro trends to audit-sessions". D50 item 3, approved the same day, reads "audit-sessions stays the all-transcripts-on-this-machine source, retro stays one chain". On main, trends is still a retro mode (plugins/session-flow/skills/retro/SKILL.md:2,3,12,70,114,166, context/trends.md), and audit-sessions says its sweep measures "no trend over time" (plugins/session-flow/skills/audit-sessions/SKILL.md, Purpose). The score history both skills use is this plugin's state file ${CLAUDE_PLUGIN_DATA}/scores/<project-slug>.md, which retro session and quick modes keep writing. This is a cut to /session-flow:retro, so a host session does it: the PR's Verification section carries before/after evals (retro's remaining cases, the moved trends cases, the trigger probes for probes/retro.json and probes/audit-sessions.json, run concurrently with the same flags) and a /docs-hygiene:compress compare over retro's SKILL.md, in the shape of PR #9328.
Done when
-
plugins/session-flow/skills/retro/context/trends.mdno longer exists. Its process, including the step 6 delivery metrics through/work-items:measure-delivery, lives in a file underplugins/session-flow/skills/audit-sessions/. - That file, or audit-sessions
SKILL.md"Paths", states the score history path${CLAUDE_PLUGIN_DATA}/scores/<project-slug>.mdand how<project-slug>is derived (the same rule as retroSKILL.md"Paths"). It does not point into retro's files for either. -
plugins/session-flow/skills/audit-sessions/SKILL.mdaddstrendsthroughout:- in the
argument-hint, the Arguments line and its full form; - in the action count and the accepted set that "Stop and name this accepted set" checks;
- in a section for the action that reads the moved file and states which options
trendstakes.
- in the
- The audit-sessions Purpose no longer says the skill measures no trend over time without naming
trends, and itsdescriptiongains a trigger for score trends ("show trends" or "how am I doing"). -
plugins/session-flow/skills/retro/SKILL.mdno longer offerstrends:- it is gone from the
description,argument-hint, the Arguments line, the Step 0 mode table, the Step 2 handoff table and the/insightsRouting sentence; /session-flow:retro trendsstops and names/session-flow:audit-sessions trends;- retro's
## Nextnames/session-flow:audit-sessions trendsfor cross-session score history.
- it is gone from the
- The
trendsmention inplugins/session-flow/skills/retro/reference/native-insights.md(:18on main) names/session-flow:audit-sessions trends. - Evals move with the mode:
- the three cases
trends-mode-routing,trends-reads-delivery-metrics-when-availableandtrends-names-missing-measure-deliveryleaveplugins/session-flow/skills/retro/evals/evals.jsonand are added toplugins/session-flow/skills/audit-sessions/evals/evals.json, with prompts that invoke/session-flow:audit-sessions trends; - retro's remaining cases no longer list
trendsamong its modes; - retro gains a case in which
/session-flow:retro trendsnames/session-flow:audit-sessions trendsand analyzes no session.
- the three cases
- Trigger probes follow:
- in
plugins/session-flow/probes/retro.json,pos-train-05("Show me trends across my last several retros.") becomes a negative with the next freeneg-train-id, andranking_notesays why; plugins/session-flow/probes/audit-sessions.jsongains that request as a positive.
- in
-
plugins/session-flow/README.mdlists the command as/session-flow:audit-sessions trendsand not as/session-flow:retro trends(:225,233on main). -
plugins/session-flow/skills/workflow/context/steps.mdstep 12 (:189on main) no longer credits retro with trend tracking, or names/session-flow:audit-sessions trendsfor it. - Every line of
plugins/session-flow/skills/retro/SKILL.mdthatgit grep -n -w trendsprints also containsaudit-sessions trends. -
git grep -n -E '/(session-flow:)?retro trends' -- plugins docs ':!**/CHANGELOG.md' ':!.changes/**' ':!plugins/session-flow/skills/retro/SKILL.md' ':!plugins/session-flow/skills/retro/evals/evals.json'prints nothing. The frozen probeneg-train-02inprobes/running-retro.json("Show retro trends over the past month.") stays unchanged. - A
.changes/session-flow/*.mdfragment withbump: majordescribes the move:/session-flow:retro trendsstops working, as theshow-optionsrename in feat(session-flow)!: rename show-options to recommend-skills #11149 did with its old command. - The PR's Verification section shows the before/after eval results and the compress-compare verdict, with no case lost.
- The PR's CI is green.
Out of scope
- Matt's retro findings (slice S1).
- Moving codify or the audit-sessions
stylepass (D50 item 3 and the corrections plugin). - Changing what the score history records or the five scored dimensions.
Parent: #7575
Activity
kyle-sexton commentedon Nov 1, 2026
github-actions commentedon Nov 1, 2026
The triage sweep dispatched intake triage for this issue (attempt 1 of 2).
github-actions commentedon Nov 1, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Understood: move the
trendsmode from/session-flow:retroto/session-flow:audit-sessions, per the owner-approved D50 item 3 and D53 under #7575. The move covers the process file, SKILL.md edits in both skills, evals, trigger probes, README and workflow docs, and a major-bump change fragment. The done-when list is specific. Retro should stop and point to the new command. The before/after evals and compress-compare need a host session, so they are left for admission to route. No likely duplicates found among the open issues.Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 1, 2026
Not admitted to the issue lane: it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (
.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Nov 1, 2026
The latest triage verdict holds nothing: admission moved the issue to
status: confirmed; its comment says why.