Verified:GitHub

spec-pipeline

Execute a requirement-to-implementation pipeline using sequential subagents for brainstorming, grilling, planning, and execution.

Updated Apr 8, 2026

Search Tags:#feature development #implementation #pipeline #workflows #requirement management

Ready to run

npx skills add https://github.com/sadie100/claude-dotfiles --skill spec-pipeline-sadie100

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-pipeline
Source: https://github.com/sadie100/claude-dotfiles/tree/main/skills/spec-pipeline
Command: npx skills add https://github.com/sadie100/claude-dotfiles --skill spec-pipeline-sadie100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the issue of navigating from an initial idea or requirement through design, stress-testing, planning, and implementation without manual transitions between separate tools.

Core Features & Use Cases

End-to-End Workflow: Runs a comprehensive pipeline, including brainstorming, grilling, planning, and executing.
Subagent Architecture: Utilizes four subagents to handle different phases, ensuring clean context for each.
Artifact-Driven: Transfers only the produced document between phases, maintaining clear context.

Quick Start

Start the spec pipeline for a new feature by running the skill with the feature's name: spec-pipeline <feature-name>.

Frequently Asked Questions about spec-pipeline

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

FAQPage Schema

How do I automate the feature development pipeline from requirement to implementation?▼

Automating the feature development pipeline requires sequentially invoking subagents for brainstorming, grill-me, writing-plans, and executing-plans to handle each phase without manual transitions. This interconnected workflow transfers only the produced document between phases, maintaining clear context.

What is a subagent architecture for requirement management workflows?▼

A subagent architecture for requirement management utilizes four distinct subagents to handle different phases of the pipeline, ensuring clean context for each stage. It transfers only the produced artifact between phases, preventing context bleed across the brainstorming, grilling, planning, and executing stages.

How do I start a spec pipeline for a new feature?▼

To start the spec pipeline for a new feature, run the skill with the feature's name by executing the command `spec-pipeline <feature-name>`. This initiates the comprehensive pipeline, automatically progressing through brainstorming, grilling, planning, and executing phases.

Does the spec-pipeline workflow require any dependencies?▼

The spec-pipeline workflow does not require any external dependencies to execute the requirement-to-implementation pipeline. It internally coordinates multiple stages and artifacts using its built-in scripts and subagent architecture.

What is the best way to stress-test a feature design before writing implementation plans?▼

The best way to stress-test a feature design before writing implementation plans is using the integrated grilling phase within the pipeline. It sequentially stress-tests the brainstorming output by passing only the artifact to the grill-me subagent, ensuring the design is validated before planning.

When should I not use an end-to-end pipeline for feature implementation?▼

An end-to-end pipeline for feature implementation should not be used when you only need to execute an isolated phase like brainstorming or planning, rather than a complete, integrated process. It is designed for users seeking a full workflow with coordinated artifacts across all stages.