ticket-implement

Automate ticket implementation workflows from plan hub through PR orchestration.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/ganzinn/deja-word --skill ticket-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-implement
Source: https://github.com/ganzinn/deja-word/tree/main/.claude/skills/ticket-implement
Command: npx skills add https://github.com/ganzinn/deja-word --skill ticket-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end ticket implementation workflow that orchestrates plan-hub tickets, worktree management, and PR coordination to deliver feature work efficiently.

Core Features & Use Cases

  • Plan-hub driven: sequences tickets based on dependencies and readiness to enable parallel workstreams.
  • Worktree orchestration: creates and manages per-ticket worktrees for isolated development.
  • Status and PR orchestration: updates plan hub statuses and automates PR creation and merge flows for both single-branch and per-ticket PR modes.
  • Guardrails and reporting: enforces deterministic sequencing, readiness checks, and clear failure reporting with handoff guidance.

Quick Start

Provide a feature name (and optional --pr) to begin implementing tickets as described in docs/plan for that feature.

Frequently Asked Questions about ticket-implement

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

FAQPage Schema
How do I automate end-to-end ticket implementation from planning to PR?

Automating ticket implementation involves orchestrating plan-hub workflows, creating per-ticket git worktrees, and coordinating PR merges. This enforces deterministic sequencing and readiness checks to ensure isolated development and feature delivery.

How does git worktree orchestration work for isolated feature development?

Git worktree orchestration creates isolated working directories for each ticket, enabling parallel workstreams without branch switching. It enforces readiness conditions and deterministic sequencing to manage isolated feature development.

Can I use per-ticket PR workflows instead of a single-branch integration?

Yes, ticket implementation orchestration supports both per-ticket PR modes and single-branch integration. It automates PR creation and merge flows while enforcing deterministic sequencing and readiness checks for either workflow.

What is the best way to coordinate plan-hub dependencies for parallel workstreams?

The best way to coordinate plan-hub dependencies is to enforce deterministic sequencing based on readiness conditions. This allows parallel workstreams by automatically sequencing tickets and ensuring prerequisites are met before starting dependent work.

When do I need to enforce deterministic sequencing for ticket implementation?

You need deterministic sequencing when managing multiple tickets with complex dependencies. It enforces readiness conditions before starting dependent work, preventing integration failures and providing clear failure reporting and handoff guidance.