skills.rest
AmirOssanloo
AmirOssanlooCOMMUNITY
Explore all skills by this author →
GitHub

pick-up-a-ticket

Guides starting, building, and closing implementation plan tickets and sprints.

Updated Sep 20, 2026
Search Tags:#task management#implementation plan#sprint planning#definition of done#status tracking#ticket workflow
One-click install
npx skills add https://github.com/AmirOssanloo/helix-game --skill pick-up-a-ticket-amirossanloo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pick-up-a-ticket
Source: https://github.com/AmirOssanloo/helix-game/tree/main/.claude/skills/pick-up-a-ticket
Command: npx skills add https://github.com/AmirOssanloo/helix-game --skill pick-up-a-ticket-amirossanloo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a consistent order of operations when an agent or developer picks up work from a structured implementation plan, preventing skipped dependencies, missing tests, and untracked status changes. ## Core Features & Use Cases - Ticket lifecycle management: Start a ticket by reading STATUS.md, verifying dependency rows are done, and marking the ticket in progress. - Build discipline: Build the ticket's Build, Acceptance, and Tests sections, and record unplanned work as new tickets instead of folding it in silently. - Sprint and phase closing: Fill the Sprint exit table, update STATUS.md pointers, and close phases only through the phase exit gates. - Use Case: An AI agent is asked to start ticket P0-S00-T01; it reads the sprint file, checks dependencies, updates statuses, builds with tests, runs pnpm check, walks the definition of done, and reports back. ## Quick Start Ask the agent to pick up the next ticket from the implementation plan and follow the ticket workflow.

Frequently Asked Questions about pick-up-a-ticket

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

FAQPage Schema
How do I start a ticket from an implementation plan?▼

Read STATUS.md to find the Next ticket, read the full sprint file including goal and risks, verify every Depends on ID has Status done, then set the ticket to in progress and update STATUS.md.

How do I close a sprint in a ticket-based plan?▼

Fill every row of the Sprint exit table with the requested numbers, then in STATUS.md move Last closed sprint and point Active sprint at the next file. Phases close only through the phase exit gates document.

What happens when a ticket depends on unfinished work?▼

If any ID in the ticket's Depends on row does not have Status done, stop and report it instead of starting. Dependencies must be completed before the ticket can be taken.

How should unplanned work be handled during a ticket?▼

Unplanned work becomes a new ticket in the same sprint with the next free number and a note saying it was unplanned. It must not be folded silently into the current ticket.

When is a ticket considered done?▼

A ticket is done when pnpm check is green (or the ticket explains why it cannot run), every definition-of-done row is walked, listed tests exist, and Status is set to done with STATUS.md updated.

Related Skills

Explore More Software Engineering Skills→
OntoLedgyOntoLedgy

task-executor

Automate end-to-end tracker ticket implementation across JIRA, Linear, Azure DevOps, and filesystem.

Official
Advanced
TECH-HYTECH-HY

tpo-roadmap-sprint-release-template

Generates roadmap, sprint planning, release checklist, and bug tracking templates for product delivery.

Official
Intermediate
synaptiaisynaptiai
6

code-review-methodology

Review code changes for compliance, security, correctness, and performance.

Official
Advanced
unblockedunblocked
11

unblocked-context-search-issues

Search issue trackers like Jira, Linear, Asana, and GitHub Issues for known work.

Official
Intermediate