create-spec

Convert planning conversations into structured feature spec folders with task files.

Updated May 20, 2026
One-click install
npx skills add https://github.com/gelowzzz/plushyai --skill create-spec-gelowzzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/gelowzzz/plushyai/tree/main/.agents/skills/create-spec
Command: npx skills add https://github.com/gelowzzz/plushyai --skill create-spec-gelowzzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams transform planning conversations into a concrete, self-contained specification structure that can be implemented by multiple agents in parallel.

Core Features & Use Cases

  • Decompose planning conversations into a set of atomic, independent tasks organized into parallel execution waves.
  • Enforce self-containment: each task file includes its own context, dependencies, files to create/modify, and acceptance criteria.
  • Produce a ready-to-run spec scaffold under specs/{feature}/ with README, requirements, action-required, and a task folder structure.

Quick Start

Run the create-spec command after a planning session to generate the specs/ folder structure.

Frequently Asked Questions about create-spec

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

FAQPage Schema
How do I convert a planning conversation into a spec folder for parallel agents?

To convert a planning conversation into a spec folder, run the create-spec command to generate a structured directory under specs/{feature}/ containing README, requirements, action-required, and self-contained task files.

What is task decomposition into wave-based parallel execution?

Wave-based task decomposition organizes atomic, independent tasks into parallel execution waves. Each task file specifies dependencies, files to create/modify, and acceptance criteria, allowing multiple agents to execute tasks concurrently within the same wave.

How do I decompose a feature into self-contained task files for parallel work?

Decomposing a feature into self-contained task files requires structuring each task with its own context, dependencies, files to create/modify, and acceptance criteria. This ensures each parallel agent has full autonomy without needing external documentation.

Does create-spec work without external dependencies for task decomposition?

Yes, create-spec works without external dependencies for task decomposition. It operates as a standalone skill to generate ready-to-run spec scaffolds, applying its internal templates directly to your planning conversations.

What is the best way to structure feature specs for parallel agent execution?

The best way to structure feature specs for parallel agent execution is using a wave-based dependency graph. This approach organizes self-contained task files into sequential waves, enabling concurrent work while respecting task dependencies.

When should I not use wave-based task decomposition for feature planning?

You should not use wave-based task decomposition for feature planning if your project lacks clear task boundaries or if tasks are highly interdependent. This method requires atomic, independent tasks to successfully execute parallel waves.