planning

Creates implementation plans with phased checklists from tickets and acceptance criteria.

5|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/micahcourey/temporal-plane --skill planning-micahcourey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/micahcourey/temporal-plane/tree/main/.ai/skills/planning
Command: npx skills add https://github.com/micahcourey/temporal-plane --skill planning-micahcourey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams often receive tickets with insufficient structure for implementation, which leads to unclear scopes, missed dependencies, and inconsistent estimates; this Skill converts ticket descriptions and acceptance criteria into actionable, developer-ready plans.

Core Features & Use Cases

  • Structured Implementation Plans: Produce a summary, scope analysis, technical design, API and database changes, and a phased implementation checklist.
  • Task Breakdown & Estimates: Translate a ticket into subtasks, assign affected areas and layers, and provide story point and time estimates using the included complexity guide.
  • Developer Handoff Ready Output: Generate checklists, testing requirements, documentation updates, and dependency lists for smooth handoff and sprint planning.
  • Use Case: When starting a new feature, convert the ticket and linked design docs into a multi-phase plan with migration notes and test strategies.

Quick Start

Use the planning skill to produce a detailed implementation plan for ticket <agent>-<model>/<type>/<task-id>-<description> including acceptance criteria and relevant context links.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I turn tickets and acceptance criteria into an implementation plan?

To create an implementation plan, you convert ticket descriptions and acceptance criteria into a structured format with scoped area analysis, technical design, API and database change lists, and phased checklists. This ensures developer-ready handoff.

What is the best way to break down tickets into subtasks and estimates?

Breaking down tickets involves translating requirements into subtasks, assigning affected areas and layers, and applying a complexity guide to generate story point and time estimates for accurate sprint planning.

How do I generate technical design and dependency tracking for a new feature?

Generating technical design and dependency tracking requires analyzing the ticket scope to produce migration notes, API and database changes, and testing requirements suitable for developer handoff and phased implementation.

Can I use this task breakdown approach for both frontend and backend work?

Yes, you can apply ticket breakdown and checklist creation to backend, frontend, and testing work. It produces scoped area analysis and phased implementation checklists covering all affected layers.

Does this implementation plan generation require specific framework dependencies?

No specific framework dependencies are required to generate implementation plans from tickets. The process relies on applying acceptance criteria and relevant context links to produce developer-ready output.

Why do my feature tickets have unclear scopes and missed dependencies?

Feature tickets often have unclear scopes and missed dependencies because they lack sufficient structure for implementation, which converting them into actionable plans with technical design and dependency lists resolves.