micro-ticket-planner

Breaks user stories and broad demands into self-contained micro-tickets for agent execution.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/psiagoleal/ai-coding-agent-profiles --skill micro-ticket-planner-psiagoleal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: micro-ticket-planner
Source: https://github.com/psiagoleal/ai-coding-agent-profiles/tree/main/skills/micro-ticket-planner
Command: npx skills add https://github.com/psiagoleal/ai-coding-agent-profiles --skill micro-ticket-planner-psiagoleal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents facing overly broad scope or ambiguous dependencies tend to stop early or ignore constraints as they approach context window limits. This Skill mitigates that "context anxiety" by decomposing large tasks into fine-grained micro-tickets that each fit within a single clean interaction cycle. ## Core Features & Use Cases - Decomposition Heuristics: Applies four rules for splitting work: one verifiable output per ticket, a closed list of files in scope, no ambiguous dependencies, and a size that fits in one turn. - Standard Ticket Format: Provides a Markdown template with objective, files in scope, acceptance criteria, explicit out-of-scope items, and dependencies on other tickets or ADRs. - Agile DoD Integration: Connects tickets to definition-of-done rituals, requiring passing tests/linters, CURRENT-STATE.md updates, and human PR review. - Use Case: During sprint planning or backlog refinement, paste a large feature request and receive an ordered set of micro-tickets, each independently executable by an agent without context overflow. ## Quick Start Ask the agent to break this large feature request into micro-tickets with clear scope, acceptance criteria, and dependencies.

Frequently Asked Questions about micro-ticket-planner

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

FAQPage Schema
How do I break a large user story into smaller tasks for an AI agent?

Apply four heuristics: each ticket produces one verifiable output, lists a closed set of files in scope, has no ambiguous dependencies, and fits in a single agent turn. Use the micro-ticket template with objective, files, acceptance criteria, out-of-scope items, and dependencies.

What is a micro-ticket format for agile backlog refinement?

A micro-ticket contains an imperative title, a single verifiable objective, the exact files in scope, an acceptance criterion such as a test or linter command, explicit out-of-scope items, and dependencies on other tickets or ADRs.

When should I write an ADR before splitting a task into tickets?

Write an ADR first whenever completing a ticket would require an architectural decision that has not yet been made. The ticket should then declare a dependency on that ADR instead of embedding an unresolved decision.

Why do AI agents fail on tasks with broad scope?

Agents facing wide scope or ambiguous dependencies tend to stop execution early or ignore safety constraints as they near context window limits, a behavior called context anxiety. Fine-grained tickets that fit one clean interaction cycle mitigate this.

What are the limitations of micro-ticket decomposition?

Decomposition cannot resolve architectural uncertainty on its own; tickets requiring unmade decisions must wait for an ADR. It also depends on external rituals like test scripts, CURRENT-STATE.md updates, and human PR review to mark work done.