plan-to-tk

Convert a plan file into structured tk tickets with dependencies.

5|4|Updated Dec 4, 2017
One-click install
npx skills add https://github.com/Nathan-Schwartz/dotfiles --skill plan-to-tk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-to-tk
Source: https://github.com/Nathan-Schwartz/dotfiles/tree/main/claude/.claude/skills/plan-to-tk
Command: npx skills add https://github.com/Nathan-Schwartz/dotfiles --skill plan-to-tk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a plan file into a structured set of tk tickets by vetting against the codebase, decomposing work, and generating a ready-to-execute ticket graph.

Core Features & Use Cases

  • Read a project plan, spawn a research and vet phase with orthogonal agents, and produce a hierarchical set of tickets (parent/child) with dependencies.
  • Verify the decomposition and ensure tickets carry conformance to a defined contract, so a fresh Claude session can implement them.
  • Generate the necessary metadata for ticket creation in tk, including descriptions, designs, and tests.

Quick Start

Provide the path to the plan file and optional supervision mode to begin planning.

Frequently Asked Questions about plan-to-tk

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

FAQPage Schema
How do I convert a project plan into structured tickets with dependencies?

To convert a project plan into structured tickets, the Skill analyzes the plan file against the codebase, decomposes work hierarchically with dependencies, and generates ready-to-execute ticket graphs for ticketing systems.

What does hierarchical ticket decomposition mean for project planning?

Hierarchical ticket decomposition breaks a project plan into parent and child tickets with explicit dependencies. It ensures each ticket carries a description, design, and verification criteria for autonomous implementation.

How do I generate actionable tickets from a plan file?

Generating actionable tickets requires providing a plan file path. The Skill then spawns research and vet phases against the codebase to produce structured metadata, ensuring tickets are ready for execution.

Can I use autonomous supervision mode for project management ticketing?

Yes, you can use autonomous supervision mode for project management ticketing by specifying it as an optional parameter alongside the plan file path when initiating the ticket creation workflow.

Do I need a codebase to create tk tickets from a plan?

Yes, a codebase is required to create tk tickets from a plan. The workflow vets the plan against existing code to validate dependencies, ensure conformance, and verify readiness before creating tickets.

What are the limitations of automated plan decomposition for ticketing?

The limitations of automated plan decomposition include dependency on the plan file's clarity and the codebase structure. If the plan lacks detail, the generated ticket metadata may require manual refinement before execution.