create-spec

Generate local specs/{feature}/ folders with self-contained task files and dependency graphs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms planning conversations into a structured, self-contained spec folder that enables parallel implementation by multiple agents and ensures decisions are captured as actionable tasks.

Core Features & Use Cases

  • Self-contained task files: one file per task with full context and acceptance criteria.
  • Wave-based planning: defines dependencies and parallelizable work streams for concurrent execution.
  • Local, Git-free specs: generates specs under specs/{feature}/ without requiring GitHub integration.

Quick Start

Execute the create-spec flow by feeding your feature plan and running the skill to generate a specs/{feature}/ directory with self-contained task files organized into waves.

Frequently Asked Questions about create-spec

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

FAQPage Schema
How do I turn feature planning conversations into actionable task files for parallel implementation?

Wave-based planning organizes tasks into parallelizable work streams by defining dependencies and concurrent execution waves, ensuring multiple agents can implement tasks simultaneously without conflicts.

What is wave-based planning for parallel agent execution?

Wave-based planning organizes tasks into parallelizable work streams by defining dependencies and concurrent execution waves, ensuring multiple agents can implement tasks simultaneously without conflicts.

Does task decomposition for parallel agents require GitHub integration?

To decompose a feature plan into self-contained task files, you run the specification generation flow to create a structured specs/{feature}/ directory containing individual task files, a dependency graph, and wave-based organization.

How do I decompose a feature plan into self-contained task files?

Specifications generated for parallel agent implementation include a dependency graph mapping task relationships and wave-based organization defining concurrent work streams, keeping all decisions captured as actionable tasks.

What structure do generated specifications use to organize parallel work streams?

Specifications generated for parallel agent implementation include a dependency graph mapping task relationships and wave-based organization defining concurrent work streams, keeping all decisions captured as actionable tasks.