sdd-pipeline

Orchestrates spec-driven development from constitution through specification, planning, tasks, and implementation.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/FarooqProProgrammer/the-magician --skill sdd-pipeline-farooqproprogrammer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-pipeline
Source: https://github.com/FarooqProProgrammer/the-magician/tree/main/.cursor/skills/sdd-pipeline
Command: npx skills add https://github.com/FarooqProProgrammer/the-magician --skill sdd-pipeline-farooqproprogrammer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams that jump straight into coding often produce inconsistent, scope-creeping features with no traceable requirements. This Skill enforces a Spec-Driven Development workflow where every feature moves through constitution, specification, planning, task breakdown, implementation, and convergence stages, with per-module constitutions guarding architectural boundaries. ## Core Features & Use Cases - Staged SDD Pipeline: Runs the full sequence of /constitution, /specify, /clarify, /plan, /tasks, /analyze, /implement, and /converge, writing structured artifacts (spec.md, plan.md, tasks.md) under specs/###-slug folders. - Module Constitutions: Requires a constitution.md for every module registered in modules.md, and loads root plus affected module constitutions before planning or implementing. - Convergence Loop: Repeats implementation and gap analysis until the feature is marked Converged, with tasks carrying exact file paths and [USn] story tags. - Use Case: When asked to add a new feature, the Skill creates specs/001-feature-slug/spec.md focused on what and why, derives an architecture plan, generates executable tasks, implements only from tasks.md, and iterates until convergence. ## Quick Start Ask the assistant to run /specify for a new feature and then follow the pipeline through /plan, /tasks, /implement, and /converge.

Frequently Asked Questions about sdd-pipeline

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

FAQPage Schema
How do I run a spec-driven development workflow without Spec Kit CLI?▼

Use the staged commands /constitution, /specify, /plan, /tasks, /implement, and /converge in order. Each command writes structured artifacts like spec.md, plan.md, and tasks.md under a specs/###-slug folder, replicating Spec Kit behavior natively.

What is the correct order of SDD commands for a new feature?▼

Start with /constitution, then /specify (optionally /clarify), followed by /plan, /tasks, and optionally /analyze. Then run /implement and repeat /converge until the feature is marked Converged.

Why does /plan or /implement fail with a missing constitution error?▼

Every module must have a constitution.md at its root and be listed in .magician/memory/modules.md. A missing module constitution is a blocker; create one with /constitution module=<name> before planning or implementing.

Can I skip the full SDD pipeline for a small bugfix?▼

Yes, a one-line bugfix with an obvious file can skip the full pipeline via the tiny escape hatch. You must still honor module boundaries and avoid touching secrets.

What belongs in spec.md versus plan.md in spec-driven development?▼

The spec.md file captures what and why, focusing on requirements and clarifications without technology choices. Stack, architecture, research, and data models belong in plan.md and its optional companion files.