Skip to content

Improve retrospective skill countermeasure quality #105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ikuwow merged 2 commits into from
Mar 19, 2026
Merged

Improve retrospective skill countermeasure quality #105

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
27e7d5f
Improve retrospective skill countermeasure quality
ikuwow Mar 19, 2026
edec5df
Add CI check as an example structural countermeasure
ikuwow Mar 19, 2026
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
22 changes: 22 additions & 0 deletions claude/skills/retrospective/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ recurrence through external mechanisms:
- Script or automation
- Template or checklist
- Permission setting
- CI check (GitHub Actions workflow, test assertion, etc.)
- Project structure change

Format as a numbered list of pairs. Include a severity rating for each:
Expand All @@ -41,6 +42,24 @@ Severity: high / medium / low (with brief justification: time wasted, user inter
Countermeasure: <structural fix> (scope: global / project-specific)
```

### Countermeasure Specificity

Each countermeasure must specify:

- The exact target file path (e.g., `AIRULES.md`, `CLAUDE.md`,
`.claude/rules/foo.md`, `.pre-commit-config.yaml`)
- The concrete content to add or modify — draft the actual wording, not
just "add a rule about X"

### Placement Scope

Choose the placement based on who benefits:

- Team-shared enforcement → project's `CLAUDE.md` or its `rules/` directory
- Personal habits or preferences → global `AIRULES.md` or `~/.claude/rules/`
- Memory is for recording facts only. It must not be used as a mechanism
for behavior change (see Prohibited Countermeasures below).

## Prohibited Countermeasures

The following are NOT valid countermeasures. Never propose them:
Expand All @@ -51,6 +70,9 @@ The following are NOT valid countermeasures. Never propose them:
- "Remember to Z"
- Any countermeasure that relies on the model's judgment, attention, or
memory improving in the future
- "Save to memory" / "Record in memory" — memory depends on model
judgment for recall and is not a structural enforcement mechanism.
Memory is valid for recording facts, but not for driving behavior change.
- Restating an existing rule as if adding it would help

The premise: the model's behavior cannot be trusted to improve through
Expand Down