ship

What problem does it solve? After a decision or spec is accepted, implementation work often drifts into scope creep, untested changes, and bloated diffs. This Skill enforces a disciplined patch workflow that locks scope first, implements the smallest correct change, and proves it with focused validation. ## Core Features & Use Cases - Scope-locked implementation: Declares goals, non-goals, likely files, and stop conditions before editing, and halts when scope expands. - Structured pipeline: Runs implementation, spec-check/test-writer, doc-writer, and simplification (Occams) passes, optionally delegating to subagents. - Operating modes: Supports patch, test, docs, polish, and bench modes for bugfixes, focused refactors, test passes, docs updates, and pre-PR cleanup. - Use Case: A developer with an accepted bugfix spec runs the workflow to produce a minimal patch, maps each acceptance criterion to test evidence, and reports changed files with validation results. ## Quick Start Ask the agent to ship the accepted bugfix spec using the ship workflow in patch mode and report the changed files with validation results.