task

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

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill task-me2resh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/task
Command: npx skills add https://github.com/me2resh/apexyard --skill task-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents vague, inconsistent issue tickets for non-user-facing engineering work by forcing structured inputs (driver, scope, acceptance criteria, risks) into a consistent GitHub issue format.

Core Features & Use Cases

  • Structured technical ticket generation: Creates a GitHub Issue with an explicit driver (why), scope (what), and actionable acceptance criteria (what must be true).
  • Works for tech debt and refactoring: Supports chores like infra changes, refactors, dependency updates, CI/CD improvements, and other work that doesn’t fit /feature or /bug.
  • Prevents bad submissions: Enforces single-question flow, requires a driver, and requires at least one acceptance criterion before allowing issue creation.
  • Auto-labeling and repo targeting: Applies priority labels, derives a work-type title prefix, and targets the correct repo based on the active project context.

Quick Start

Ask the AI to create a technical task ticket by calling /task and answering the driver, scope, acceptance criteria, priority, and any optional risks or dependencies.

Frequently Asked Questions about task

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

FAQPage Schema
How do I create structured GitHub issues for technical debt and refactoring?

Structured GitHub issues for technical debt require a driver, scope, and at least one acceptance criterion. This tool formats those inputs into a consistent ticket, applies priority labels, targets the correct repo, and requires explicit confirmation before creating the issue.

What is the best way to write acceptance criteria for SDLC infrastructure tasks?

Writing acceptance criteria for SDLC infrastructure tasks means defining exactly what must be true upon completion. This tool enforces a stepwise input flow to capture the driver, scope, and actionable acceptance criteria, preventing vague submissions for non-user-facing engineering work.

Can I automate priority labeling and repo targeting for non-feature work tickets?

Yes, you can automate priority labeling and repo targeting for non-feature work tickets. The tool derives a work-type title prefix, applies priority labels, and targets the correct repo based on the active project context during the ticket generation process.

Does this ticket generation tool work for dependency updates and CI/CD improvements?

Yes, this ticket generation tool works for dependency updates and CI/CD improvements. It specifically supports chores like infra changes, refactors, and other SDLC-gated tasks that do not map to standard feature or bug workflows.

Why does the tool enforce a single-question flow for creating technical tickets?

The tool enforces a single-question flow for creating technical tickets to prevent bad submissions. By requiring a driver and at least one acceptance criterion step-by-step, it eliminates ambiguity and ensures all necessary context is captured before allowing issue creation.