spec-pipeline

Orchestrate a three-stage product specification pipeline with sequential stage execution.

2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/onejaejae/skills --skill spec-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-pipeline
Source: https://github.com/onejaejae/skills/tree/main/plugins/ai-registry/common/spec-pipeline/skills/spec-pipeline
Command: npx skills add https://github.com/onejaejae/skills --skill spec-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the entire process of creating a product specification, from initial idea to a review-ready document, automating tedious steps and ensuring consistency.

Core Features & Use Cases

  • Orchestrates a 3-stage pipeline: spec-interview, spec-generator, and spec-reviewer.
  • Automated Input Handling: Automatically passes outputs from one stage as inputs to the next.
  • Flexible Starting Points: Can begin from scratch (interview) or jump into specific stages if prior work exists.
  • Use Case: When you have a new feature idea, you can run this pipeline to generate requirements, then a detailed spec, and finally get it reviewed, all with minimal manual intervention.

Quick Start

Initiate the full spec pipeline from the beginning.

Frequently Asked Questions about spec-pipeline

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

FAQPage Schema
How do I automate end-to-end product specification generation from requirements gathering to review?

You can automate product specification generation by running an orchestrated pipeline that sequentially handles requirement extraction, spec document generation, and automated review. This workflow passes outputs from each stage as inputs to the next, minimizing manual intervention.

Can I start the spec generation workflow from an intermediate stage if I already have requirement documents?

Yes, the workflow supports flexible starting points based on existing artifacts. You can jump directly into the spec-generator or spec-reviewer stages instead of starting from the initial interview phase if prior work exists.

What is the best way to structure a review process for product development workflows?

The best way to structure a review process for product development is using a sequential pipeline architecture. It separates requirement extraction, document generation, and review into distinct automated stages, ensuring consistency and thorough feedback.

Does the pipeline handle passing extracted requirements directly into the document generation phase?

Yes, the pipeline handles automated input passing by feeding the extracted requirements directly into the document generation phase. It orchestrates the stages sequentially, using the output of the interview phase as the input for the generator.

Are there limitations when initiating a full spec pipeline from scratch without any prior artifacts?

When initiating from scratch, the pipeline begins with the spec-interview stage to gather requirements. There are no stated limitations for this approach; it is designed to handle the entire process from initial idea to review-ready document natively.