create-plan

Name: create-plan
Availability: InStock
Author: Hubble

Generate PR-sized implementation plans from technical specifications.

Updated Aug 27, 2026

Search Tags:#planning #task management #pull request #software development #decomposition #execution plan

Ready to run

npx skills add https://github.com/Hubble-inc/demo-nego --skill create-plan-hubble-inc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/Hubble-inc/demo-nego/tree/main/.cursor/skills/create-plan
Command: npx skills add https://github.com/Hubble-inc/demo-nego --skill create-plan-hubble-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms detailed technical specifications (SPEC) into actionable, PR-sized implementation plans (PLAN), ensuring clarity and efficiency for developers.

Core Features & Use Cases

Atomic Task Decomposition: Breaks down large features into small, independent tasks, each suitable for a single Pull Request.
Dependency Management: Orders tasks logically (Common -> Backend -> Frontend) to prevent blocking and rework.
Use Case: A Tech Lead can use this Skill to automatically generate a detailed, step-by-step execution plan for a new feature, complete with specific files to modify and verification commands, allowing Senior Developers to start coding immediately.

Quick Start

Use the create-plan skill to generate an execution plan from the provided SPEC files.

Frequently Asked Questions about create-plan

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

FAQPage Schema

How do I generate an implementation plan from a technical specification?▼

To generate an implementation plan from a technical specification, the Skill analyzes detailed SPEC files and decomposes them into atomic, PR-sized tasks with defined contexts, files, and verification commands.

What is the best way to break down large software features into pull request units?▼

The best way to break down large features into pull request units is through atomic task decomposition, which splits specifications into small, independent tasks ordered logically to prevent blocking and rework.

How does dependency management work when creating a phased execution plan?▼

Dependency management works by ordering tasks logically from Common to Backend to Frontend specifications, ensuring structured execution that prevents blocking and minimizes rework during software development.

Can I automatically generate verification commands for my development workflow tasks?▼

Yes, you can automatically generate verification commands for development workflow tasks, as the Skill produces a phased execution plan where each defined task includes specific verification commands for immediate coding.

What specifications are required to produce a structured task decomposition plan?▼

Producing a structured task decomposition plan requires analysis of common, backend, and frontend specifications, which are then transformed into a phased execution plan with defined tasks and files to modify.

Why should I use atomic task decomposition for my software development workflow?▼

You should use atomic task decomposition for software development workflows because it transforms detailed technical specifications into actionable, PR-sized plans, ensuring clarity and allowing developers to start coding immediately.