skills.rest
Space-Dinosaurs
Space-DinosaursOFFICIAL
Explore all skills by this author →
Website𝕏@SpaceDinosaurS6GitHub

implement-ticket

Coordinate ticket-to-PR workflows across Linear, Jira, or freeform inputs.

12|1|Updated Apr 7, 2026
Search Tags:#automation#orchestration#linear#jira#ticket#ci#pull-request
One-click install
npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill implement-ticket-space-dinosaurs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-ticket
Source: https://github.com/Space-Dinosaurs/DinoStack/tree/main/.openclaw/skills/implement-ticket
Command: npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill implement-ticket-space-dinosaurs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning a ticket reference or freeform ticket description into a merged PR, coordinating multiple agents (Architect → Orchestration Planner → Engineer → Skeptic) and posting the CI Test URL back to the ticket.

Core Features & Use Cases

  • End-to-end ticket-to-PR orchestration across Linear, Jira, or freeform inputs.
  • Fixed conductor pipeline (Architect → Orchestration Planner → Engineer → Skeptic) with CI URL posting and audit trail.
  • Supports project tracker integration, per-ticket state management, and robust resume/rollback behavior for reliable automation.

Quick Start

Provide a ticket reference or description and run /implement-ticket to start the automated workflow.

Frequently Asked Questions about implement-ticket

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

FAQPage Schema
How do I automate ticket-to-PR workflows from Jira or Linear?▼

Ticket-to-PR automation coordinates an end-to-end conductor pipeline from ticket intake through a merged pull request. It processes Linear, Jira, or freeform text inputs, drives engineering phases, and posts the CI Test URL back to the original ticket.

How does multi-agent orchestration work for software engineering tickets?▼

Multi-agent orchestration uses a fixed conductor pipeline routing work sequentially through Architect, Orchestration Planner, Engineer, and Skeptic phases. This enforces structured reasoning and auditable state management before a PR is generated.

Can I use freeform ticket descriptions instead of Jira or Linear references?▼

Freeform ticket descriptions are fully supported as valid inputs for the orchestration pipeline. You can provide raw text instead of formal tracker references, and the workflow generates a merged PR and posts the CI URL.

What is the best way to track CI Test URLs across automated pull requests?▼

Tracking CI Test URLs is handled automatically by posting the link back to the originating ticket upon pipeline completion. This applies across Linear, Jira, and freeform inputs, maintaining a clear audit trail for each PR.

How do I safely resume or rollback automated ticket orchestration if a step fails?▼

Resume and rollback behavior is managed through per-ticket state tracking and safe, auditable state management. This ensures reliable automation recovery without losing progress if a pipeline phase fails.

Do I need strict frontmatter requirements for automated ticket orchestration?▼

Strict frontmatter requirements are enforced to support phase-driven orchestration and per-ticket batch tracking. Meeting these formatting standards ensures safe state management and reliable workflow automation.

Related Skills

Explore More Software Engineering Skills→
paulchiupaulchiu
3

linear-do

Automate Linear issue handling from ticket intake through CI monitoring.

Community
Advanced
aoki-taquanaoki-taquan

issue-pr

Create a pull request from the current branch and monitor CI status.

Community
Advanced
mvillmowmvillmow
18

gh-get-review-comments

Retrieve GitHub pull request review comments via the GitHub API.

Community
Basic
davidYichengWeidavidYichengWei
159

workflow-code-review

Automate multi-agent code review coordination and triage into a structured assessment.

Community
Advanced