Friction cluster: teammate-redundant-idle-confirmation (1 report)

[hcross]

Friction cluster: teammate-redundant-idle-confirmation

1 friction tagged across the harness-friction wing (2026-05-14 (single day)). Routed to https://github.com/hcross/crewrig.

Pattern

Reports span room behavior. The common subcategory anchor is teammate-redundant-idle-confirmation.

Frictions

1. Teammates re-confirm completed tasks in subsequent idle notifications, creating noise for the team lead
   • Reported by: claude-code
   • Severity: low
   • Room: behavior
   • Evidence: community-config/agents/pr-reviewer/AGENT.md
   • Evidence: community-config/skills/pr-logbook/SKILL.md
   • Suggestion (from reporter): When an agent receives a wake-up (idle → active transition) and its assigned task is already marked completed, it should simply confirm availability in one sentence without re-summarising the entire task output. Repeated full summaries on idle notifications inflate the team lead's context and obscure actual status changes. A one-line "Task #N already completed, available for new work" is sufficient.

Suggested resolution

All reporters converge on: When an agent receives a wake-up (idle → active transition) and its assigned task is already marked completed, it should simply confirm availability in one sentence without re-summarising the entire task output. Repeated full summaries on idle notifications inflate the team lead's context and obscure actual status changes. A one-line "Task #N already completed, available for new work" is sufficient.

Out of scope

This issue was auto-generated by the Harness Curator (V0). It is descriptive only — a follow-up MR (human-authored, or via the auto-fix mode tracked in #42) will close it with the actual diff.

[hcross]

2026-05-14 — Add idle-behavior guideline to pr-reviewer and pr-logbook

Context: Implementation logbook for branch fix/issue-96-teammate-idle-confirmation, addressing the friction cluster described in this issue (teammates re-summarising completed tasks on idle wake-ups).

What was tried: Added an ## Idle behavior section to two component sources — community-config/agents/pr-reviewer/AGENT.md and community-config/skills/pr-logbook/SKILL.md — instructing the agent to confirm availability in a single sentence rather than re-summarising a completed task. The same edit was mirrored into the .claude/ and .gemini/ distributions to keep the three trees aligned. Provenance versions were bumped (pr-reviewer AGENT 1.0.0 → 1.0.1, pr-logbook SKILL 1.1.1 → 1.1.2) per the SKILL/AGENT version-bump rule documented in community-config/skills/pr-logbook/SKILL.md → Cross-cutting: skill / agent source version bumps.

Outcome: Green. One commit (3654f49), 6 files, +51/-6. The diff matches the version-bump rule (PATCH bumps for wording-only additions). No other surface was touched.

Lesson: The friction reporter already supplied a near-final one-sentence template ("Task #N already completed, available for new work"). When a curator-generated issue carries a Suggested resolution paragraph that is essentially the patch text, treating it as the spec — rather than re-deriving wording — keeps the diff minimal and the reviewer's job trivial. Also: any guideline that lands in a SKILL or AGENT must be mirrored across all three distribution trees (community-config/, .claude/, .gemini/) in the same commit, otherwise the trees drift and the next sync MR has to clean it up.