What problem does it solve? Coordinating a multi-phase engineering ticket workflow (scope, investigate, plan, review, implement, test, verify, finalize) by hand is error-prone, with gates, monitoring writes, and sidecar bookkeeping easily skipped or done out of order. ## Core Features & Use Cases - Full pipeline orchestration: Executes every phase of the implement-ticket workflow in order, translating the authoritative .claude/workflows/implement-ticket.js into direct tool calls. - Tier support: Handles hotfix (skips Investigate/Plan/Review), standard (full pipeline), and epic (scope only) tiers, plus resuming existing tickets by ID. - Gate integrity enforcement: Hard-blocks on gate failures (DOC_STALENESS_BLOCKED, PARITY_INCOMPLETE, TESTS_FAILED, etc.) and forbids editing artifacts to make checks pass. - Use Case: A developer runs /implement-ticket ticket_id=TCK-20260607-MY-TICKET to resume an in-progress ticket, and the skill drives it through testing, parity ledger updates, security review, and finalization with monitoring recorded at every exit. ## Quick Start Run the implement-ticket skill with a ticket ID like TCK-20260607-MY-TICKET or a natural language request describing the change you want implemented.