Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
bump: patch
---

### Fixed

- `/session-flow:retro`: the gotcha on mechanical findings puts "when the `corrections` plugin is
enabled" on the hand-off to `/corrections:codify`, where the condition applies.
- `/session-flow:retro`: without the `corrections` plugin, the catalog's "Check first" step states
in item 2 that one occurrence of a policy-class mistake is enough to propose a check, beside a
repeat with the same cause.
4 changes: 2 additions & 2 deletions plugins/session-flow/skills/retro/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -215,8 +215,8 @@ writing it into a brief: a `${…}` token in a spoke reaches the Bash tool unsub
`AGENTS.md` or rules-file line, the guidance tier of
[reference/enforcement-ladder.md](reference/enforcement-ladder.md)) names its proof in the PR:
an eval case, or a deletion watch with a date (`/harness-config:unhobble`, when the
`harness-config` plugin is enabled). A mechanical finding goes to `/corrections:codify`, which
proves its own check (when the `corrections` plugin is enabled), run once the user picks it at
`harness-config` plugin is enabled). A mechanical finding goes to `/corrections:codify` (when
the `corrections` plugin is enabled), which proves its own check, run once the user picks it at
Phase 4
- **Phase 4 is an interactive checkpoint**, never persist codifications without explicit user
approval
Original file line number Diff line number Diff line change
Expand Up @@ -29,16 +29,17 @@ banned API, a file written in the wrong place, a step skipped before a commit.
`/corrections:codify "<the mistake>"`, which counts it, applies the ladder's guardrail
criterion, picks the strongest rung that can decide it and proves the check. Without it, judge
the finding on the "Guardrail criterion" items a retro can settle from the finding itself: item
1 (decidable without reasoning), item 2 (it recurs, by the rule "When to propose a check" under
[Owner skills](#owner-skills) gives for when the plugin is not enabled) and item 7 (no stronger rung
already covers it). A finding that meets those three takes the [Hooks](#hooks) section's format
and names the strongest rung of the ladder copy that can decide it. Without the plugin, items
3-6 and 8 (precision, a message naming the fix, proof on a planted violation, the same command
at edit time and in CI, a kill switch) describe a check that exists, and a retro proposes a
check without writing or proving one, so the row lists them as requirements the proposed check
must meet. A finding that fails item 1, 2 or 7 goes on to the placement decision tree, since the
ladder keeps it on the guidance tier. Give a finding that gets a check row no CLAUDE.md,
`AGENTS.md` or rules-file row, a pointer to the check included: the check replaces the line.
1 (decidable without reasoning), item 2 (it repeats with the same cause, or it happened once and
is policy-class: irreversible, public, or security-relevant, as "When to propose a check" under
[Owner skills](#owner-skills) says) and item 7 (no stronger rung already covers it). A finding
that meets those three takes the [Hooks](#hooks) section's format and names the strongest rung
of the ladder copy that can decide it. Without the plugin, items 3-6 and 8 (precision, a message
naming the fix, proof on a planted violation, the same command at edit time and in CI, a kill
switch) describe a check that exists, and a retro proposes a check without writing or proving
one, so the row lists them as requirements the proposed check must meet. A finding that fails
item 1, 2 or 7 goes on to the placement decision tree, since the ladder keeps it on the guidance
tier. Give a finding that gets a check row no CLAUDE.md, `AGENTS.md` or rules-file row, a pointer
to the check included: the check replaces the line.
- **No**: go on to the placement decision tree below.

## Placement Decision Tree
Expand Down
Loading