Context
Discussion #11423 ideated a mechanism to eliminate the "Helpful Assistant" deference-slip that agents exhibit when transitioning into an idle/blocked state (such as waiting for a peer review or finishing an implementation).
The Problem
Agents default to their underlying RLHF conditioning at turn boundaries ("Would you like me to...", "What should I do next?") when a local task finishes, violating the Flat Peer-Team constraint (AGENTS.md §15.6). Descriptive L1 anchor text is too weak against this conditioning.
The Architectural Reality
Option B.1-prime was unconditionally [GRADUATION_APPROVED] cross-family. Instead of creating a new state-transition skill (which causes sprawl) or bloating AGENTS.md §0 with universal hard gates, we will expand the post-review-pickup skill's trigger surface to encompass other post-lifecycle-event transitions. This leverages the Phase B Description-Router hardening (PR #11424) to keep the L1 anchor lean.
The Fix
- Extend
post-review-pickup-workflow.md description and payload to encompass broader lifecycle transitions.
- Add a highly compact AGENTS.md §21 trigger pointer.
- Update
SKILL.md description to explicitly surface the broader trigger language to the description-router.
- Explicitly protect
blocked-task-state for strictly negative paths.
Discussion Criteria Mapping
Maps directly to the Option B.1-prime [RESOLVED_TO_AC] criteria established in Discussion #11423.
Acceptance Criteria
Out of Scope
- Creating a new generic state-transition skill.
- Adding universal
AGENTS.md hard gates for state transitions.
Related
Origin Session ID
188acb85-b41e-435c-94ee-0cc9944d4c97
Context Discussion #11423 ideated a mechanism to eliminate the "Helpful Assistant" deference-slip that agents exhibit when transitioning into an idle/blocked state (such as waiting for a peer review or finishing an implementation).
The Problem Agents default to their underlying RLHF conditioning at turn boundaries ("Would you like me to...", "What should I do next?") when a local task finishes, violating the Flat Peer-Team constraint (AGENTS.md §15.6). Descriptive L1 anchor text is too weak against this conditioning.
The Architectural Reality Option B.1-prime was unconditionally
[GRADUATION_APPROVED]cross-family. Instead of creating a newstate-transitionskill (which causes sprawl) or bloatingAGENTS.md§0 with universal hard gates, we will expand thepost-review-pickupskill's trigger surface to encompass other post-lifecycle-event transitions. This leverages the Phase B Description-Router hardening (PR #11424) to keep the L1 anchor lean.The Fix
post-review-pickup-workflow.mddescription and payload to encompass broader lifecycle transitions.SKILL.mddescription to explicitly surface the broader trigger language to the description-router.blocked-task-statefor strictly negative paths.Discussion Criteria Mapping Maps directly to the Option B.1-prime
[RESOLVED_TO_AC]criteria established in Discussion #11423.Acceptance Criteria
.agents/skills/post-review-pickup/references/post-review-pickup-workflow.mddescription/payload to cover:blocked-task-stateexit signal)lane-state:declaration (positive next-lane OR halt with survey evidence)..agents/skills/post-review-pickup/SKILL.mddescription to surface the broader trigger language.blocked-task-statescope for negative paths only.Out of Scope
AGENTS.mdhard gates for state transitions.Related
Origin Session ID
188acb85-b41e-435c-94ee-0cc9944d4c97