executing-tickets

Automate ticket execution from ready to close using the tk command set.

Updated Jan 12, 2021
One-click install
npx skills add https://github.com/jssee/.dotfiles --skill executing-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-tickets
Source: https://github.com/jssee/.dotfiles/tree/main/.config/opencode/skill/executing-tickets
Command: npx skills add https://github.com/jssee/.dotfiles --skill executing-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable approach to implementing work tickets by guiding a developer through a disciplined, test-driven workflow, reducing context switching and ensuring traceable progress.

Core Features & Use Cases

  • Guided ticket lifecycle: From ready to close, including planning, testing, coding, and documentation.
  • TDD-first workflow: Emphasizes writing failing tests before implementing code and validating with the test suite.
  • Contextual execution: Works in the worktree where tickets were created and records outcomes for accountability.

Quick Start

Run through the next ticket with tk ready, then tk start <id>, tk show <id>, follow the ticket’s steps, and finally tk close <id>.

Frequently Asked Questions about executing-tickets

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

FAQPage Schema
How do I automate ticket execution for software development workflows?

Automating ticket execution involves using a command set like 'tk' to guide a test-driven workflow from ready through close, ensuring traceable progress and reducing context switching. It applies a deterministic workflow with per-ticket context and auditable history.

What is a TDD-first workflow for implementing work tickets?

A TDD-first workflow emphasizes writing failing tests before implementing code and validating with the test suite. It provides a structured approach to implementing work tickets, guiding a developer through planning, testing, coding, and documentation.

How do I start executing a ticket using the tk command set?

To start executing a ticket, run tk ready, then tk start <id>, tk show <id>, follow the ticket’s steps, and finally tk close <id>. This guides the lifecycle from ready to close with auditable commit and note history.

Does guided ticket lifecycle management work within an existing worktree?

Yes, contextual execution works in the worktree where tickets were created. It records outcomes for accountability and applies to TDD-based tasks where each ticket is worked from ready through close with steps, tests, and acceptance criteria.

Why use a deterministic workflow for software ticket execution?

A deterministic workflow ensures traceable progress and reduces context switching by applying a structured, repeatable approach to implementing work tickets. It meets functional requirements using per-ticket context and auditable commit and note history.