bounded-work-item

What problem does it solve?

In multi-agent coding workflows, agents often drift beyond their assigned scope, touch unrelated files, or claim unverified success. This Skill constrains a Coder agent to exactly one canonical work packet, enforcing strict boundaries on what can be read, edited, and submitted.

Core Features & Use Cases

• Scoped Execution: Reads only the declared work packet and its refs, then makes the smallest change satisfying the packet inside allowed paths.
• Evidence-Based Submission: Runs focused verification and submits results to the assigned Reviewer through the assigned-review chain, returning a terminal status of done, blocked, or needs_rework.
• Boundary Enforcement: Prohibits editing authoritative state, running workflow wrappers, expanding scope, or claiming whole-round success.
• Use Case: In an agentic loop workflow, a controller dispatches a node work packet to a Coder agent; the agent implements the change, verifies it, submits evidence for review, applies bounded rework if requested, and stops.

Quick Start

Execute this single work packet within its declared scope and allowed paths, verify the change, and submit the evidence to the assigned reviewer.