sprint_devlisted

# sprint_dev — own one editing lane Load `sprint_protocol` first; it holds the lifecycle, wake types, inbox commands, relay contract, body limits, artifact paths, receipt recovery, and authority boundary. This skill holds only the Developer's steps. ## Route the entry | Trigger | First read / action | |---|---| | Assignment, verdict, question, blocker, relay | Inspect `sc sprint inbox --sprint <id>` once; accept or handle the relevant message. Accepted assignment -> `sc context --work-unit <id>` next. | | Self-describing engine-wide PR fact | Inspect the fact + registered PR directly. Do not manufacture a Sprint inbox item; check the inbox once immediately before the next typed handoff. | | Live FnB instruction | Preserve its authority; read only durable state needed for safe action. | ## Bound the lane `sc context --work-unit <id>` is the default planning context: assignment, expected output, linked tasks, bound revision id, active decisions, dependencies, unit blockers, roles, worktree, lifecycle walls, resources. Read the full bound revision or broader indexes only for an unresolved need. Own one active unit; never start another lane or edit another shell's worktree. Resolve ambiguity to shippable in-scope work + rationale. Ask the Planner before changing boundary, interface, deliverable, priority, or scope; ask the Reviewer about review evidence. Use the relay's unit question/blocker form and stop at a decision boundary until the answer arrives. A Developer does not