implement-ticket

Automate ticket implementation through a 14-phase workflow for single-repo and multi-repo projects.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/thisisqubika/ai-mast-challenge-promptazo --skill implement-ticket-thisisqubika
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-ticket
Source: https://github.com/thisisqubika/ai-mast-challenge-promptazo/tree/main/.claude/skills/implement-ticket
Command: npx skills add https://github.com/thisisqubika/ai-mast-challenge-promptazo --skill implement-ticket-thisisqubika

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the ticket implementation process, providing a comprehensive 14-phase workflow from planning to PR, and supporting both single-repo and multi-repo projects.

Core Features & Use Cases

  • End-to-End Workflow: Handles ticket implementation from context gathering to PR creation and review.
  • Multi-Repo Support: Works seamlessly with single-repo and multi-repo workspaces.
  • Graph-Aware & Wiki-Aware: Utilizes graph and wiki data for informed decision-making.
  • Use Case: Use this Skill to automate the implementation of a new feature in a software project, ensuring that all steps from planning to deployment are followed systematically.

Quick Start

To implement a ticket, run the skill with the ticket ID or markdown spec:

/implement-ticket --from-jira "PROJ-123"

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 implementation from planning to PR creation?▼

This skill streamlines ticket implementation with a 14-phase workflow covering planning to PR review. It supports multi-repo projects and uses graph and wiki data for informed planning and execution.

Does this ticket implementation workflow support multi-repo projects?▼

Yes, the ticket implementation workflow supports both single-repo and multi-repo workspaces seamlessly. It uses graph and wiki data to navigate and plan changes across multiple repositories.

How do I implement a Jira ticket using an automated SDLC workflow?▼

Run the implementation skill with your Jira ticket ID to start the automated workflow. The process gathers context, plans the implementation using graph and wiki data, and creates a PR for review.

What environment setup is required for graph-aware ticket implementation?▼

Graph-aware ticket implementation requires a well-configured project environment and access to the Claude Code platform. Proper wiki and graph data configuration is necessary for informed planning and execution.

Can I use a markdown spec instead of a Jira ID for ticket implementation?▼

Yes, you can initiate ticket implementation using either a Jira ticket ID or a markdown spec. The workflow processes the provided specification to automate the planning and PR creation process.

What are the limitations of automating ticket implementation with graph data?▼

The main limitation is the requirement for a well-configured project environment and Claude Code platform access. Without proper graph and wiki data configuration, the planning and implementation phases cannot function optimally.