skills.rest
AAbdulghany
AAbdulghanyCOMMUNITY
Explore all skills by this author →
𝕏@AAbdulghanyyGitHub

task

Create structured technical task tickets with driver, scope, acceptance criteria, and risks.

Updated Apr 15, 2026
Search Tags:#task-management#tech-debt#github-issues#technical-ticket#driver-scope-acs#infra-refactor
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill task-aabdulghany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/task
Command: npx skills add https://github.com/AAbdulghany/fms --skill task-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool standardizes the creation of technical task tickets by guiding engineers to capture the driver, scope, acceptance criteria, and risks in a consistent format.

Core Features & Use Cases

  • Generate GitHub issues for tech debt, infrastructure changes, or non-user-facing tasks with a predefined template that includes driver, scope, acceptance criteria, and risks.
  • Enforce a consistent structure across projects to improve traceability, review speed, and scope clarity.
  • Use case: When planning a tech debt cleanup, create a single task ticket that documents why the work is needed, what will change, and how success will be measured.

Quick Start

Provide a concise task title and let the skill generate a structured ticket containing the driver, scope, acceptance criteria, and risks.

Frequently Asked Questions about task

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

FAQPage Schema
How do I create structured technical task tickets for tech debt and infrastructure refactors?▼

You can generate technical task tickets by providing a task title, which automatically produces a structured template capturing the driver, scope, acceptance criteria, and risks for your tech debt or infrastructure refactor work.

What should a technical task ticket include for non-user-facing work across multi-repo projects?▼

A technical task ticket for non-user-facing work should include the driver explaining why the work is needed, the scope of changes, acceptance criteria for measuring success, and identified risks to ensure traceability across multi-repo projects.

Can I use this skill to generate GitHub issues for technical debt cleanup?▼

Yes, this skill supports GitHub integration for issue creation. It enforces a standard template for technical debt cleanup that documents the driver, scope, acceptance criteria, and risks directly within the GitHub issue.

What is the best way to standardize technical ticket formats across multiple engineering projects?▼

The best way to standardize technical ticket formats across projects is by enforcing a predefined template. This skill ensures consistent structure for driver, scope, acceptance criteria, and risks to improve traceability and review speed.

Does this skill support custom fields for priority and acceptance criteria when creating technical tickets?▼

Yes, the skill supports fields for driver, scope, acceptance criteria, risks, and priority. It applies these fields to a standard template to ensure all technical task tickets capture the necessary details for non-user-facing work.

Related Skills

Explore More Software Engineering Skills→
maxmurrmaxmurr

template-skill

Generate structured skill metadata with request, description, is_toxic, and toxic_reason fields.

Community
Basic
me2reshme2resh
489

task

Generate structured GitHub issue tickets for technical tasks with acceptance criteria.

Community
Intermediate
pacphipacphi
7

github-project-management

Coordinate GitHub project issues, boards, and sprints via AI swarm orchestration.

Community
Advanced
mpetitompetito

story-writing

Format Azure DevOps work items with markdown templates and acceptance criteria.

Community
Intermediate