create-prompt-plan

Decompose specification files into ordered implementation prompts with status tracking.

399|31|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/tobihagemann/turbo --skill create-prompt-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-prompt-plan
Source: https://github.com/tobihagemann/turbo/tree/main/skills/create-prompt-plan
Command: npx skills add https://github.com/tobihagemann/turbo --skill create-prompt-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill tackles the challenge of translating large, complex project specifications into manageable, bite-sized prompts that can be executed in individual AI sessions, ensuring a structured and efficient development process.

Core Features & Use Cases

  • Specification Decomposition: Analyzes a given specification file and breaks it down into a series of discrete, context-sized implementation prompts.
  • Prompt Ordering: Arranges prompts logically based on dependencies, ensuring foundational work precedes dependent tasks.
  • Status Tracking: Assigns a status (pending, in-progress, done) to each generated prompt for progress monitoring.
  • Use Case: When you have a detailed project spec for a new feature, use this Skill to generate a sequence of prompts that guide the AI through building each part of the feature, from setup to final implementation.

Quick Start

Use the create-prompt-plan skill to decompose the specification file located at .turbo/spec.md into a series of implementation prompts.

Frequently Asked Questions about create-prompt-plan

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

FAQPage Schema
How do I break down a project specification into actionable AI prompts?

To break down a project specification into actionable AI prompts, you decompose the spec file into context-sized implementation prompts. This process manages project scope, work categories, dependencies, and ordering for sequential AI execution.

How does specification decomposition manage prompt ordering for code generation?

Specification decomposition manages prompt ordering by analyzing dependencies and arranging prompts logically. This ensures foundational work precedes dependent tasks, generating a structured file with status tracking and context for each sequential AI execution prompt.

Can I use this specification decomposition approach for an existing codebase?

Yes, you can use this specification decomposition approach for an existing codebase. It manages project scope, work categories, dependencies, and ordering for both greenfield and existing codebases to generate sequential implementation prompts.

What is the best way to track progress when generating implementation prompts from a spec?

The best way to track progress when generating implementation prompts is to use a structured file that assigns a status to each prompt. It assigns pending, in-progress, or done statuses to each generated prompt for continuous progress monitoring.

Do I need a specific file format to decompose specs into implementation prompts?

You need a specification file, typically located at a defined path like your project's spec file. The Skill analyzes this file and generates a structured prompts file containing the decomposed, context-sized implementation prompts with status tracking.