ship-it
Ship It
Own execution from an accepted plan to a recorded terminal delivery state. Do not reopen settled product decisions unless new repository evidence creates a material conflict.
Scope and authorization
Honor explicit user scope and applicable prior authorization over workflow defaults. Continue authorized preparation and reversible work using established conventions; ask only for material unresolved decisions or authority not already given. Preserve engineering safeguards and access controls. If a skill blocks progress, identify the exact instruction and concrete conflict, and continue independent authorized work.
For a read-only or no-change request, return findings in chat without creating or updating plans, state, memory, configuration, or knowledge records unless those writes are explicitly authorized. Preserve current user corrections over stale artifacts, updating those artifacts only when writes are in scope.