ticket-implementation-copilot
Delivers roadmap features by selecting unblocked tickets and verifying completion against AC.
Install
mkdir -p .claude/skills/ticket-implementation-copilot && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14370" && unzip -o skill.zip -d .claude/skills/ticket-implementation-copilot && rm skill.zipInstalls to .claude/skills/ticket-implementation-copilot
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Execute DSDS roadmap tickets using dependency-aware, acceptance-criteria-first delivery. Use when selecting the next unblocked ticket, implementing code changes, validating behavior, and reporting completion against ticket AC.Key capabilities
- →Select the next unblocked ticket based on dependencies
- →Translate tickets into implementation plans
- →Implement code changes with testability in mind
- →Validate acceptance criteria with evidence
- →Report completion with summary and risks
How it works
The skill follows a workflow to implement DSDS tickets by prioritizing unblocked work, defining minimal implementation scope, and validating acceptance criteria.
Inputs & outputs
When to use ticket-implementation-copilot
- →Pick next ticket
- →Verify ticket acceptance criteria
- →Report task completion
About this skill
Ticket Implementation Copilot
Overview
Implement DSDS tickets in a predictable way by prioritizing unblocked work and validating acceptance criteria explicitly.
Workflow
- Select next unblocked ticket
- Read dependencies from
planning/TICKETS.md. - Pick the highest-priority ticket whose blockers are resolved.
- Translate ticket into implementation plan
- Extract required files, interfaces, and acceptance criteria.
- Define minimal implementation scope that satisfies AC.
- Implement with testability in mind
- Add or update code in the target files.
- Keep changes scoped to ticket intent.
- Validate acceptance criteria
- Run relevant checks (
tsc, tests, lint, runtime checks). - Record AC status as pass/fail with evidence.
- Report completion
- Summarize files changed, behavior added, test results, and remaining risks.
Output format
Selected ticket and dependency statusImplementation summaryAC verification checklistResidual risks
References
- Read
references/ticket-delivery-workflow.mdfor AC-first execution template. - Use these repo sources:
planning/TICKETS.mdplanning/IMPLEMENTATION_PLAN.mddocs/SYSTEM_OVERVIEW.md(feature-to-ticket mapping)
When not to use it
- →When tickets do not have defined dependencies
- →When acceptance criteria are not explicitly stated
- →When a formal completion report is not required
Limitations
- →Relies on `planning/TICKETS.md` for dependencies
- →Requires defined acceptance criteria for validation
- →Assumes the existence of `planning/IMPLEMENTATION_PLAN.md` and `docs/SYSTEM_OVERVIEW.md`
How it compares
This skill provides a structured, AC-first approach to ticket implementation, ensuring predictable delivery and explicit validation, unlike an ad-hoc development process.
Compared to similar skills
ticket-implementation-copilot side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ticket-implementation-copilot (this skill) | 0 | 5mo | No flags | Intermediate |
| work-on-issue | 0 | 6mo | Review | Intermediate |
| issues | 0 | 3mo | Review | Beginner |
| tasks | 0 | 5mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
work-on-issue
meta-pytorch
Start work on a GitHub issue. Extracts requirements, creates worktree, sets up TDD workflow.
issues
Anhvu1107
ALWAYS use this when the request matches Issues: Interact with GitHub issues - create, list, and view issues.
tasks
indexedlabs
Track and execute implementation work using Mighty (mt) tasks, with progress comments, linked evidence, recorded decisions, and clean closeout. Use when asked to fix a bug, implement a feature/refactor, or “work through” changes in code while keeping Mighty tasks/specs/decisions updated.
smith-new
ATTCKDigital
Start a new feature from scratch or from conversation context. Conversational requirements gathering, planning, questions gate, then fully autonomous build.
complete-task
Log2n-io
Complete work on a GitHub issue - close issue, update artifacts, prompt for doc updates
develop-feature
saptarshibasu
Use when starting spec-driven development on any change, large or trivial — triggers: \"create a spec for X\", \"start a new feature: Z\", \"use SDD for this\", \"write a spec before we code\". Proposes a right-sized workflow track for approval, then orchestrates Specify -> Plan -> Tasks -> Analyze