work

Name: work
Availability: InStock
Author: tigredonorte

Orchestrate Jira tasks with state-machine transitions and agent delegation.

Updated Feb 25, 2026

Search Tags:#automation #workflow #orchestration #deterministic #jira #software-development #task-management

Ready to run

npx skills add https://github.com/tigredonorte/claude-plugin-work --skill work-tigredonorte

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work
Source: https://github.com/tigredonorte/claude-plugin-work/tree/main/skills/work
Command: npx skills add https://github.com/tigredonorte/claude-plugin-work --skill work-tigredonorte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate Jira-based development tasks with deterministic step execution to avoid drift and ensure predictable outcomes.

Core Features & Use Cases

Deterministic Workflow Engine - State-machine driven step execution with forward/backward transitions
Jira Integration - Automatically fetches task details, transitions issue status, and links PRs
Quality Enforcement - Built-in hooks enforce screenshot requirements, step ordering, and code review
Parallel Agent Orchestration - Delegates work to specialized sub-agents (TDD, React, DevOps, QA) while keeping the orchestrator context lean
Multi-task Support - Bootstrap and orchestrate multiple Jira tasks across isolated git worktrees

Quick Start

Input a Jira ticket ID to initiate the orchestrator plan and begin the deterministic workflow.

Frequently Asked Questions about work

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

FAQPage Schema

How do I automate Jira task orchestration for software development workflows?▼

Jira task orchestration is automated using a state-machine driven plan that fetches ticket details, enforces step ordering, and transitions issue status deterministically. You input a Jira ticket ID to initiate the workflow and avoid execution drift.

What is deterministic workflow execution for Jira tickets?▼

Deterministic workflow execution uses a state machine to drive forward and backward step transitions for Jira tasks. This ensures repeatable, auditable outcomes by enforcing plan validation and step ordering throughout the software development process.

Can I orchestrate multiple Jira tasks in parallel across different git worktrees?▼

Yes, multiple Jira tasks can be bootstrapped and orchestrated across isolated git worktrees. The engine delegates work to specialized sub-agents like TDD, React, DevOps, and QA while keeping the orchestrator context lean.

How do I enforce code review and screenshot requirements in Jira workflows?▼

Code review and screenshot requirements are enforced through built-in quality hooks within the deterministic workflow engine. These hooks validate step execution and prevent forward transitions until specific quality criteria are met.

Does this Jira orchestration workflow support multi-agent coordination?▼

Multi-agent coordination is supported by delegating specialized work to sub-agents for TDD, React, DevOps, and QA tasks. The orchestrator manages these parallel agents to execute steps while maintaining a lean context for overall workflow control.

What is the best way to link pull requests to Jira issues automatically?▼

Pull requests are linked to Jira issues automatically by the workflow engine during task orchestration. The state machine transitions the issue status and associates the PR once the deterministic execution steps are completed.