What problem does it solve? Turning a written ticket into verified, committed code is where implementations drift: scope creeps, tests get skipped, and tickets get marked done on a red build. This Skill enforces a disciplined cycle — ground in the spec, build a checklist, write the least code, test, verify against a gate, then close out tracking — so a ticket is only complete when evidence says so. ## Core Features & Use Cases - Checklist-gated implementation: Extracts every deliverable and acceptance criterion into a numbered checklist printed before coding, and blocks verification until each item has evidence. - Bounded verification loop: Runs the ticket's commands plus the project gate, iterating gather-evidence → fix-root-cause → re-verify up to 3 cycles, and reports the ticket blocked rather than claiming false success. - Ordered close-out and set runs: Updates memory, checkboxes, status, and _tasks.md in a fixed sequence, and runs multi-ticket slugs sequentially in dependency order with optional read-only subagent fan-out. - Use Case: You have a slug of five tickets from a tech spec. Invoke this Skill with the slug; it resolves dependencies, implements each ticket with tests, verifies against the project gate, and stops with a blocked report if any ticket cannot reach green. ## Quick Start Ask the agent to implement ticket PROJ-12 using rc-implement and verify it against the project gate before marking it complete.
