What problem does it solve? Vague or bundled engineering tickets cause the Joshua AI agent (MiniMax via Antfarm) to implement the wrong file, stop after the first criterion, or mark work done prematurely. This Skill enforces a strict ticket format so every Linear issue assigned to Joshua passes the CI ticket validator and contains everything needed for correct implementation. ## Core Features & Use Cases - Routing Check: Verifies the task is a single-repo implementation task before assigning to Joshua, redirecting KB, SPIKE, planning, and iOS tasks to David. - Verified File Paths: Requires Glob/Grep verification of exact file paths and forbids ambiguous qualifiers like "or equivalent" or "similar". - Atomic Ticket Splitting: Enforces one acceptance criterion per ticket and splits multi-part work into separate issues. - Canonical Format with CI Validation: Produces tickets with Repo, File, Acceptance Criteria checkboxes, and the correct per-service test command (pytest, npm test, gradlew, xcodebuild). - Use Case: When a bug is found in the workout-ingestor service, use this Skill to locate the exact file, draft a ticket with a pre-written failing pytest, and create the Linear issue assigned to Joshua via the Linear MCP tool. ## Quick Start Ask the assistant to create a Joshua ticket for a specific backend fix, and it will verify the file paths, draft the ticket in canonical format, and create it in Linear after your approval.