skills.rest
t-jet
t-jetCOMMUNITY
Explore all skills by this author →
GitHub

workflow

Guides agents through ticket lifecycles, hierarchy rules, and Definition of Done compliance.

Updated Aug 11, 2026
Search Tags:#workflow#ticket management#definition of done#epic#sub-tasks#project lifecycle#dev story
One-click install
npx skills add https://github.com/t-jet/pal_found_cli --skill workflow-t-jet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/t-jet/pal_found_cli/tree/main/.ept/resources/skills/workflow
Command: npx skills add https://github.com/t-jet/pal_found_cli --skill workflow-t-jet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing multi-phase software projects with tickets requires consistent rules for statuses, transitions, sub-task types, and role responsibilities. Without a shared process, agents create tickets with wrong hierarchies, skip Definition of Done checks, or transition work prematurely. ## Core Features & Use Cases - Four-Phase Lifecycle Guidance: Covers Discovery, Requirements & Scope Refinement, Design, and Implementation phases with the exact ticket types and statuses for each stage. - Ticket Type and Hierarchy Reference: Defines top-level tickets (FEATURE, EPIC, BUG, TASK, RESOURCE-REQ), analysis/design sub-tasks (BA-ANA, SA-DES, UX-DES), and implementation sub-tasks (DEV, UNITTEST, CODEREVIEW, TESTCASE, TESTEXEC, DEVOPS, BUG-SUB) with parent-child rules and link types. - DoD and Transition Enforcement: Requires Definition of Done verification with documented evidence before any status transition, routed through the ticket-helper subagent. - Use Case: An agent picks up a FEATURE ticket, creates BA-ANA and SA-ANA analysis sub-tasks, closes them, opens design sub-tasks, spawns DEV-STORY tickets during BA-DES, and drives each story through Grooming, Development, QA, and Deployment while keeping the linked EPIC status in sync. ## Quick Start Ask the agent to create a FEATURE ticket for a new business requirement and move it through the workflow stages following the ticket-helper instructions.

Frequently Asked Questions about workflow

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

FAQPage Schema
How do I move a FEATURE ticket through development stages?▼

A FEATURE moves from Discovery to Analysis, where BA-ANA and SA-ANA sub-tasks capture requirements, then to In Design for BA-DES and SA-DES work. DEV-STORY tickets are created during design, and the feature reaches Waiting for Implementation once design sub-tasks close.

What sub-tasks are created during DEV-STORY grooming?▼

During Grooming, the DESIGN sub-task is created first for estimation and technical planning, alongside DEV, UNITTEST, CODEREVIEW, TESTCASE, TESTEXEC, and DEVOPS sub-tasks. The DESIGN sub-task must be closed before the story transitions to Development.

When does an EPIC ticket change status automatically?▼

An EPIC moves to In Progress when the first DEV-STORY linked via the EpicLink relationship enters Development. It transitions to Resolved or Done when all linked DEV-STORY tickets reach a terminal status such as Closed or Done.

Can I transition a ticket without meeting its Definition of Done?▼

No. Transitions are blocked until the DoD for the current status is met, with compliance documented in ticket comments by the responsible role and verified by the manager. DoD criteria come from the ticket-helper subagent output.

What ticket type should I use for ad-hoc work?▼

Use the TASK type for ad-hoc work not tied to any Feature or Epic. For unclassified sub-tasks inside an existing TASK or FEATURE, use the WORK type, and use QUESTION sub-tasks whenever clarification from another team member is needed.

Related Skills

Explore More Product & Management Skills→
IainMclIainMcl

ticket-writer

Create Jira task and bug tickets in the TK-APP project via Atlassian MCP.

Community
Intermediate
thuantan2060thuantan2060

bmad-create-story

Creates implementation-ready story files from sprint status and planning artifacts.

Community
Advanced
christian-byrnechristian-byrne

metrics-dashboard

Aggregate and analyze pipeline run data to track velocity and success rates.

Community
Intermediate
Zeyad-37Zeyad-37

migrate-board

Migrate a markdown Kanban board to GitHub Issues and Projects v2.

Community
Advanced