tk-planner

Automate software ticket planning by decomposing work into sub-tasks.

3|Updated Nov 22, 2020
One-click install
npx skills add https://github.com/jeffutter/nixpkgs --skill tk-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tk-planner
Source: https://github.com/jeffutter/nixpkgs/tree/main/modules/home/languages/ai/skills/tk-planner
Command: npx skills add https://github.com/jeffutter/nixpkgs --skill tk-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

tk-planner automates end-to-end planning for software tickets by researching, decomposing, and detailing actionable sub-tasks.

Core Features & Use Cases

  • Spawns research subagents to gather context and dependencies
  • Analyzes upstream and downstream dependencies to determine sequencing
  • Creates sub-tickets (Epic/Feature/Task) with clear descriptions and blocking relationships
  • Writes comprehensive implementation plans that guide execution and testing

Quick Start

Run the planner on a ticket to generate a structured plan, e.g. /tk-planner proj-42 to start planning.

Frequently Asked Questions about tk-planner

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

FAQPage Schema
How do I automate ticket planning for software epics and subtasks?

Ticket planning automation researches context, decomposes work into sub-tickets, analyzes upstream and downstream dependencies, and writes comprehensive implementation plans with clear blocking relationships.

How does autonomous subtask decomposition handle dependency sequencing?

Subtask decomposition analyzes upstream and downstream dependencies to determine sequencing, creating structured metadata and actionable design notes that define clear blocking relationships between discrete work items.

Can I generate implementation plans for individual software tickets automatically?

Yes, you can generate implementation plans for individual tickets by running the planner, which researches context, details subtasks, and produces structured design notes executable via the tk workflow.

What is the best way to orchestrate research subagents for software ticket planning?

Orchestrating research subagents for ticket planning involves spawning agents to gather context and dependencies, then using that data to decompose epics into sub-tickets with actionable design notes and sequencing.

Does autonomous ticket planning work for both individual tasks and epics?

Yes, autonomous ticket planning applies to both individual tickets and Epics, spawning research subagents and creating sub-tickets with clear descriptions and blocking relationships for each scope.