From ai-in-the-human-loop
Triage open HUMAN.md feedback entries, moving each to adopted, obsolete, or merged based on linked PRs and friction logs. Also supports re-reading adopted items for obsolescence.
How this command is triggered — by the user, by Claude, or both
Slash command
/ai-in-the-human-loop:triageThe summary Claude sees in its command listing — used to decide when to auto-load this command
The loop keeps two files: `HUMAN.md` (rules layer — the action rules) and
`HUMAN_FRICTIONS.md` (log layer — raw observations, append-only). Triage works on
the rules in `HUMAN.md`; it reads the log for context but never rewrites it.
Walk through every rule under `## Open Feedback Items` in `HUMAN.md` one at a
time. For each rule:
1. Read the rule's `Better Human Action`, its `Friction log` (the observations it
cites in `HUMAN_FRICTIONS.md`), and any `Linked PRs`.
2. Decide its next status:
- **adopted** if the improvement has shown up in real work. There must be
at least one P...The loop keeps two files: HUMAN.md (rules layer — the action rules) and
HUMAN_FRICTIONS.md (log layer — raw observations, append-only). Triage works on
the rules in HUMAN.md; it reads the log for context but never rewrites it.
Walk through every rule under ## Open Feedback Items in HUMAN.md one at a
time. For each rule:
Read the rule's Better Human Action, its Friction log (the observations it
cites in HUMAN_FRICTIONS.md), and any Linked PRs.
Decide its next status:
Linked PRs, and the PR's body or diff must reflect
the Prompt Pattern or Review Pattern. If Linked PRs is empty, the
rule stays open.Merged Items with a pointer to the survivor's ID, and
have the meta-rule's Friction log cite every contributing H-ID. Do not
delete content, and never collapse the friction log — only the rule side.When you change a rule's status:
Status field.Adopted Items, Obsolete Items, or Merged Items).## Operation Log at the bottom of
HUMAN_FRICTIONS.md: YYYY-MM-DD — H-NNN: open → adopted (or similar).
Include a short reason if the transition is not obvious.After processing every open rule, also re-read the Adopted Items
section. If an adopted rule has not been referenced in any new work for
a long stretch and the underlying behavior change appears stable, you may
move it to Obsolete Items with the note "behavior change is now
habitual." This is a judgment call; when in doubt, leave it adopted.
Do not invent new rules during triage. If you observe new friction while
reading old rules, that is a job for the human-feedback skill in a
separate session.
When the walk is complete, summarize:
Linked PRs for many weeks)
and might be candidates for obsoletion next round.scope category all moved to adopted at once may mean the human has
internalized scope declaration.npx claudepluginhub kawasima/ai-in-the-human-loop --plugin ai-in-the-human-loop/learn-from-reviewDistills human review feedback from a GitHub PR into actionable rules appended to the Manual section of .claude/standards.md, so future pre-review catches the same issues.
/triageTriages findings from code reviews, audits, or analysis by presenting each for categorization by severity, category, effort, then creates or updates ready todo files in todos/ directory on user approval.
/feedbackCaptures feedback on KARIMO or Claude Code operations with auto-detection of issue complexity, generates rules for simple cases or launches adaptive investigation for complex ones.
/reflectAnalyzes filtered diary entries for patterns in user preferences, code decisions, solutions, and challenges, then synthesizes insights and proposes CLAUDE.md updates.
/2-triageClassifies code review comments by type and priority into Fix Now, This PR, Backlog, and Skip categories, outputting structured markdown tables.
/triageRuns a 7-question gate triage on a security finding to decide go/no-go before writing a full report. Outputs a kill decision or passes for validation.