skills.rest
jscottchapman
jscottchapmanCOMMUNITY
Explore all skills by this author →
GitHub

ticket-driven-dev-harness

Automate a tracked ticket into a merge-ready pull request.

Updated Jun 8, 2026
Search Tags:#automation#autonomy#test-first#pr-workflow#ticket-driven#repo-agnostic
One-click install
npx skills add https://github.com/jscottchapman/skills --skill ticket-driven-dev-harness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-driven-dev-harness
Source: https://github.com/jscottchapman/skills/tree/main/ticket-dev-harness/ticket-driven-dev-harness
Command: npx skills add https://github.com/jscottchapman/skills --skill ticket-driven-dev-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns a tracked ticket into a merge-ready pull request autonomously, eliminating manual handoffs and gate checks by planning, generating tests first, implementing, evaluating, and opening the PR without human intervention.

Core Features & Use Cases

  • Autonomous GAN-style planning: evaluator first, then generator, driving a hands-off cycle from ticket to PR.
  • Repo-agnostic detection of trackers, test frameworks, package managers, and target branches to adapt in any repo.
  • Size-driven ceremony: scales ceremony to trivial, standard, or substantial tickets with appropriate rigor.
  • PR creation and gating: pushes code, creates PR, and provides a self-contained test plan.

Quick Start

Install this skill and point it at a ticket or let it ingest a pasted ticket to autonomously plan, test, implement, evaluate, and open a PR.

Frequently Asked Questions about ticket-driven-dev-harness

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

FAQPage Schema
How do I automate turning a tracked ticket into a merge-ready pull request?▼

You can automate the ticket-to-PR flow by using an autonomous workflow that phases through PLAN, TEST-FIRST, IMPLEMENT, EVALUATE, and PR steps to generate a merge-ready pull request without manual intervention.

Does test-first automation work with any codebase and repository setup?▼

Yes, test-first automation applies repo-agnostic detection of trackers, test frameworks, package managers, and target branches to adapt across any codebase and generate tests before implementation.

Can I scale the development ceremony based on the size of the ticket?▼

You can scale development ceremony based on ticket size, applying appropriate rigor to trivial, standard, or substantial tickets throughout the autonomous planning and implementation phases.

What is the best way to eliminate manual handoffs when creating pull requests?▼

The best way to eliminate manual handoffs is an autonomous GAN-style planning cycle where the evaluator and generator drive a hands-off flow from ticket ingestion to opening a PR with a self-contained test plan.

Do I need to configure my repository before starting ticket-driven development?▼

No extensive configuration is needed because the workflow automatically detects your repo's trackers, test frameworks, package managers, and target branches to adapt its autonomous ticket-to-PR pipeline accordingly.

Related Skills

Explore More Software Engineering Skills→
Julian0444Julian0444
2

onex-plan-ticket

Convert plan descriptions into YAML tickets and create them in Linear.

Community
Intermediate
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
ibalasiteibalasite

ship

Merge a feature branch, run tests, bump VERSION, update CHANGELOG, and create a pull request.

Community
Advanced
ghbvfghbvf
4

ship

Orchestrate end-to-end delivery workflows with staged phases and multi-agent review.

Community
Advanced