create-joshua-ticket

Creates well-formed Linear tickets for the Joshua AI agent with verified file paths and acceptance criteria.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/Amakaflow/amakaflow-dev-workspace --skill create-joshua-ticket-amakaflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-joshua-ticket
Source: https://github.com/Amakaflow/amakaflow-dev-workspace/tree/main/.claude/skills/create-joshua-ticket
Command: npx skills add https://github.com/Amakaflow/amakaflow-dev-workspace --skill create-joshua-ticket-amakaflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about create-joshua-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Linear ticket for an AI coding agent?

Verify the exact file path with Glob or Grep, write one atomic acceptance criterion with a test command, and create the issue via the Linear MCP tool assigned to the agent. This Skill enforces that canonical format so the CI ticket validator passes.

What makes a good ticket for an AI agent like MiniMax?

Good tickets include exact verified file paths, the function or line range to change, a pre-written failing test, and a single verifiable acceptance criterion. Avoid qualifiers like "or equivalent" or "similar", which cause the agent to guess wrong files.

Which tasks should not be assigned to the Joshua agent?

Do not assign knowledge base tasks, SPIKE or research tasks, planning or architecture work, PRD writing, or iOS tasks to Joshua. Those belong to David; Joshua only handles single-repo implementation tasks with a clear spec.

Why does the CI ticket validator reject a Linear ticket?

The validator blocks tickets missing a Repo field, at least one verified File entry, an Acceptance Criteria section, a checkbox item, or a test command such as pytest or npm test. All five elements must be present.

How should multi-part bug fixes be split into tickets?

Create one ticket per distinct acceptance criterion rather than bundling them. Joshua tends to complete the first item and stop, so three distinct fixes require three separate tickets, each with its own test command.