What problem does it solve? Coding agents ship tickets with inconsistent quality: reviews get skipped on small changes, security passes are dropped under time pressure, and tests are written after the code. This Skill defines one canonical cycle for executing a single ticket so every ticket gets the same expert-team coverage regardless of how it was started. ## Core Features & Use Cases - Predicate-keyed triage: Each pass (architecture, migration safety, E2E, UX/UI, security, dogfooding) fires only when its observable predicate is true, while ALWAYS passes like TDD, review, and verification can never be skipped. - Team orchestration: Coordinates specialist subagents (type-design-analyzer, doctrine-critic, silent-failure-hunter) through a Mission Engine controller with fresh-context dispatch, structured completion events, and degraded/blocked verdicts. - Tracker lifecycle integration: Claims tickets before edits, keeps status truthful, attaches PR evidence, and respects human review gates. - Use Case: You pick up a backlog issue that touches a database schema and a settings UI. The cycle runs migration safety before TDD, applies the migration locally, runs the UX/UI and deep security passes, dogfoods the CLI output on the real repository, and ships bisectable commits with a PR. ## Quick Start Ask the agent to take ticket PROJ-123 and implement it end to end using the void-implement cycle.
