task-tickets

Convert implementation plans into kanban tickets for GitHub Projects, Linear, Notion, or Jira.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/polikeiji/skills --skill task-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-tickets
Source: https://github.com/polikeiji/skills/tree/main/skills/task-tickets
Command: npx skills add https://github.com/polikeiji/skills --skill task-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns implementation and DevOps plans into actionable kanban tickets with enough detail for an AI coding agent to start work without follow-up questions.

Core Features & Use Cases

  • Converts impl-plan and devops-plan documents into ticket-sized work items.
  • Captures source links, objectives, technical guidance, acceptance criteria, testing requirements, and PR instructions.
  • Supports GitHub Projects, Linear, Notion, and Jira while preserving dependency order and labels.
  • Use it when a team needs to transform a finished plan into tracked work across a project board.

Quick Start

Turn this implementation plan into tickets for GitHub Projects and include source links, acceptance criteria, testing requirements, and dependencies.

Frequently Asked Questions about task-tickets

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

FAQPage Schema
How do I convert an implementation plan into kanban tickets for GitHub Projects or Linear?

To convert an implementation plan into kanban tickets, this Skill parses your plan documents and registers ticket-sized work items into GitHub Projects or Linear. It preserves dependency order, links source plans, and includes acceptance criteria and testing requirements.

Can I create Jira or Notion tickets directly from devops-plan documents?

Yes, you can create Jira or Notion tickets directly from devops-plan documents. The workflow checks CLI or MCP availability, then registers the tasks with source links, technical guidance, and PR-ready testing instructions.

What is the best way to ensure AI coding agents have enough detail in tracked work items?

The best way to ensure AI agents have enough detail is to enrich kanban tickets with source links, objectives, acceptance criteria, and PR instructions during creation. This Skill automatically captures that context from implementation plans.

Does this ticket generation workflow support dependency ordering and label assignment?

Yes, this ticket generation workflow supports dependency ordering and label assignment. It preserves the execution sequence from the implementation plan and assigns appropriate labels when registering tasks across project boards.

Do I need CLI or MCP availability checks before turning plans into tracked work?

Yes, CLI or MCP availability checks are required before turning plans into tracked work. The workflow verifies that the necessary command-line interfaces or Model Context Protocol connections are active to interact with GitHub, Linear, Notion, or Jira.

Why convert implementation plans into kanban tickets instead of just using the plan document?

Converting implementation plans into kanban tickets splits large plans into actionable, tracked work items. This ensures dependency order is visible on project boards and provides AI coding agents with PR-ready testing guidance without follow-up questions.