What problem does it solve? Codebases accumulate explicit implementation stubs—TODO(implementation) markers, TEMP placeholders, and draft-code sentinels—that must be finished without accidentally claiming neighboring work like bug fixes, test authoring, or new features. This Skill completes only those accepted stubs while routing everything else to the correct owning workflow. ## Core Features & Use Cases - Scoped stub completion: Scans a file, directory, or package for accepted markers and replaces each with the smallest production implementation satisfying the established contract. - Strict boundary routing: Classifies nearby markers and routes FIXME to coding:fix, test TODOs to coding:complete-test, and missing functionality to coding:write-code instead of overreaching. - Contract-driven verification: Reads specifications, types, call sites, and existing tests to derive behavior, then runs focused tests, type checks, and lint after each replacement. - Use Case: After running a draft-code pass that emitted throw new Error('IMPLEMENTATION: ...') sentinels across a package, invoke this Skill on that package to fill in each sentinel against the existing spec and test suite, with ambiguous markers reported as blocked rather than guessed. ## Quick Start Ask the agent to complete all implementation stubs in the src/payments directory using the complete-code workflow.
