implement-tickets

Implements dependency-ordered ticket batches in isolated worktrees with per-ticket acceptance and review.

Updated May 19, 2026
One-click install
npx skills add https://github.com/wenyue/SmartKit --skill implement-tickets-wenyue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-tickets
Source: https://github.com/wenyue/SmartKit/tree/main/docs/zh-CN/skills/implement-tickets
Command: npx skills add https://github.com/wenyue/SmartKit --skill implement-tickets-wenyue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multi-ticket implementation work often leads to unreviewed changes, broken dependency order, lost partial progress, and unclear tracker state. This Skill orchestrates a controlled batch workflow that implements eligible tickets in dependency order inside an isolated worktree, accepts each ticket independently, reviews the combined result, and finishes with a verifiable delivery. ## Core Features & Use Cases - Frozen batch selection: Resolves tracker eligibility, dependency edges, and claim paths, then freezes members, order, and accepted requirements before any work begins. - Per-ticket acceptance: Each ticket gets one independently reviewed commit with a canonical ticket trailer, verified against its frozen base before the batch proceeds. - Bounded review and repair: One formal review round and at most one focused repair per ticket and per batch, with Controller-led issue closure tied to the exact final HEAD. - Pause and resume: Preserves claims, accepted commits, review evidence, and handoff state so interrupted batches resume at the latest attributable stage. - Use Case: A team has five queued bug-fix tickets with dependencies. The Skill claims them, creates a clean worktree, implements and reviews each in order, accepts the combined result, and hands off authoritative delivery evidence for tracker closure. ## Quick Start Ask the agent to implement the eligible tickets from the configured tracker in dependency order using the implement-tickets workflow.

Frequently Asked Questions about implement-tickets

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

FAQPage Schema
How do I implement multiple tickets in dependency order automatically?▼

This Skill freezes a selection of eligible tickets, orders them by dependency edges, and implements each in an isolated worktree. Every ticket produces exactly one independently reviewed commit before the batch moves to combined acceptance and final delivery.

How does per-ticket code review work in a batch workflow?▼

Each ticket gets one formal review round with independent Standards and Spec dimensions, followed by at most one focused repair. The Controller closes findings against the exact final HEAD before marking the ticket commit as accepted.

Can an interrupted ticket batch be resumed safely?▼

Yes. The workflow preserves claims, accepted commit prefixes, review evidence, and handoff state, then resumes at the latest attributable stage. It never repeats possibly completed external operations and pauses when evidence is ambiguous.

What happens when a ticket requires no code changes?▼

Empty-diff tickets still undergo independent Standards and Spec review proving requirements are already satisfied at the base. An empty commit with the canonical ticket trailer marks acceptance, and no-change results must match the baseline tree exactly.

When does this workflow return nothing-to-do?▼

When the bounded selection scope contains no eligible tickets after dependency and eligibility checks, the Skill returns nothing-to-do with observations and exclusions. It creates no batch, no worktree, and no changes in that case.