Verified:GitHub

feature-pipeline

Delegates end-to-end feature delivery to the sdd-pipeline spec-driven workflow.

Updated Sep 8, 2026

Search Tags:#workflow #planning #implementation #feature delivery #sdd #spec-driven development #alias

One-click install

npx skills add https://github.com/FarooqProProgrammer/the-magician --skill feature-pipeline-farooqproprogrammer

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: feature-pipeline
Source: https://github.com/FarooqProProgrammer/the-magician/tree/main/.cursor/skills/feature-pipeline
Command: npx skills add https://github.com/FarooqProProgrammer/the-magician --skill feature-pipeline-farooqproprogrammer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need a consistent, repeatable path from a feature idea to implemented code, and this Skill provides a single entry point that routes all feature work through the Spec-Driven Development pipeline. ## Core Features & Use Cases - Alias for SDD Workflow: Acts as a shortcut for /feature requests, delegating execution to the sdd-pipeline Skill. - Full Delivery Loop: Follows the sequence constitution → specify → clarify → plan → tasks → implement → converge. - Use Case: When a developer types /feature to start new work, this Skill ensures the request is handled by the standard spec-driven process rather than ad-hoc implementation. ## Quick Start Ask the assistant to start a new feature using the feature pipeline and describe the feature you want to build.

Frequently Asked Questions about feature-pipeline

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

FAQPage Schema

How do I start a new feature with the feature pipeline?▼

Invoke the /feature command or ask for end-to-end feature work. The Skill delegates to sdd-pipeline, which runs the loop: constitution, specify, clarify, plan, tasks, implement, converge.

What is the difference between feature-pipeline and sdd-pipeline?▼

feature-pipeline is an alias that delegates all work to sdd-pipeline. It exists so /feature requests route into the same spec-driven delivery loop without duplicating instructions.

What stages does the spec-driven feature workflow include?▼

The workflow runs constitution, specify, clarify, plan, tasks, implement, and converge. Each stage builds on the previous one to take a feature from idea to implemented code.

When should I not use the feature pipeline?▼

Avoid it for small bug fixes or one-off edits that do not need a full specification cycle. The pipeline is designed for end-to-end feature delivery, not trivial changes.