From ticket-agent
Autonomous ticket-to-production lifecycle with promptlet-driven phases. Use when executing /ticket commands or working on ticket-driven development.
npx claudepluginhub jack-michaud/faire --plugin ticket-agentThis skill uses the workspace's default tool permissions.
The ticket workflow drives an autonomous agent through 10 phases from ticket intake to production validation. Each phase is defined by a **promptlet** -- a markdown template that specifies what agents to spawn, how they coordinate, and what they produce.
resources/phase-reference.mdresources/promptlet-format.mdresources/promptlets/ci-review-loop.mdresources/promptlets/completion.mdresources/promptlets/deploy-watch.mdresources/promptlets/implementation.mdresources/promptlets/intake.mdresources/promptlets/planning.mdresources/promptlets/pr-creation.mdresources/promptlets/production-validation.mdresources/promptlets/verification.mdFetches next ready_to_develop ticket via Board API or Supabase, creates feature/fix/chore branch, implements autonomously through build, code review, QA, docs checks, and ships without stopping.
Drives end-to-end ticket workflow: analyzes tickets, investigates codebase, plans, implements via TDD, commits changes, and creates PRs. Adapts to stack via interactive supplement setup.
Creates self-contained Jira/Asana/Linear/GitHub tickets optimized for autonomous Claude Code execution using INVEST+C criteria. Use when writing specs for AI agents.
Share bugs, ideas, or general feedback.
The ticket workflow drives an autonomous agent through 10 phases from ticket intake to production validation. Each phase is defined by a promptlet -- a markdown template that specifies what agents to spawn, how they coordinate, and what they produce.
| # | Phase | Key | Session Boundary |
|---|---|---|---|
| 1 | Intake | intake | no |
| 2 | Planning | planning | YES - human reviews plan |
| 3 | Implementation | implementation | no |
| 4 | Verification | verification | no |
| 5 | PR Creation | pr-creation | no |
| 6 | CI + Review Loop | ci-review-loop | YES - if 3 fix attempts fail |
| 7 | Human Merge Gate | human-merge-gate | YES - always |
| 8 | Deploy Watch | deploy-watch | YES - conditional |
| 9 | Production Validation | production-validation | no |
| 10 | Completion | completion | no |
/ticket <id>Two-tier resolution, project-local overrides defaults:
.claude/ticket-agent/promptlets/<phase>.md${CLAUDE_PLUGIN_ROOT}/skills/ticket-workflow/resources/promptlets/<phase>.mdIf a project-local promptlet exists, use it (it already contains project-specific knowledge from /ticket-learn). Otherwise, fall back to the generic default.
State is stored at .claude/ticket-agent/state/<ticket-id>.json in the target project. The state file is immutable-write (full replace each time). It tracks:
ticket_id: The ticket identifiercurrent_phase: Which phase the ticket is inbranch_name: The VCS branch (created during implementation)pr_number and pr_url: PR details (set during pr-creation)phases: Per-phase status and dataAll VCS operations use jj by default. Projects using git can override via learned promptlets.
All sub-agents are general-purpose type. The promptlet defines:
The /ticket command in the main session IS the orchestrator. Sub-agents cannot spawn sub-agents.
CRITICAL ORCHESTRATOR RULE: The orchestrator MUST delegate work to sub-agents as defined by each promptlet. During phases that define agents (especially implementation), the orchestrator MUST NOT directly use Edit, Write, Grep, or Bash tools for code changes. It should only use tools for state management (reading/writing state files) and spawning agents. Each promptlet's agent templates contain literal prompt text — the orchestrator fills in values from state data and passes the constructed prompt to the Agent tool. If a promptlet defines per-component agents, the orchestrator iterates over the components array and spawns one agent per component.
The agent saves state and ends at these natural breakpoints:
After the PR is created, the ci-review-loop phase forms a continuous monitoring loop:
Reference documents for this workflow:
resources/phase-reference.md - Detailed phase definitions and transition rulesresources/promptlet-format.md - How to write and customize promptletsresources/promptlets/ - Generic implementations for each phase