What problem does it solve?
Manually implementing individual tracker tickets, coordinating with coding engines, managing state transitions, running quality checks, and logging implementation details is disjointed and error-prone, especially when running parallel sprint workflows or handling multiple trackers.
Core Features & Use Cases
- Tracker-agnostic implementation: Works with JIRA, Linear, Azure DevOps, or local filesystem trackers via adapter modules, no hardcoded platform logic.
- Intelligent engine delegation: Routes implementation work to Codex or specialist Claude-native engineer skills based on ticket complexity, explicit assignment labels, or caller input.
- Automated quality gates: Runs syntax checks, test validation, dependency vulnerability scanning, and clean-code reviews for complex tickets, with up to 3 targeted fix iterations.
- Parallel sprint support: Integrates with sprint-executor to run per-ticket work in isolated git worktrees for concurrent wave execution, no manual worktree management.
- Full workflow automation: Handles all ticket state transitions, progress comments, and structured implementation logging end-to-end.
Use case example: A software team running a 2-week sprint can use this skill to automatically pick up assigned tickets, delegate implementation to the appropriate engine, validate the output, commit changes, and update tracker status — all without manual coordination between team members.
Quick Start
Use the task-executor skill to implement ticket TI-101 end-to-end, delegating coding work to the assigned engine and updating its JIRA status through to In Review.
