spec-driven-dev

Redirects deprecated spec-driven development workflows to the unified spec skill commands.

1|Updated Jul 2, 2026

Search Tags:#specification #spec #spec-driven development #deprecated #redirect #workflow migration

Ready to run

npx skills add https://github.com/tarabakz25/my-skills --skill spec-driven-dev-tarabakz25

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/tarabakz25/my-skills/tree/main/spec-driven-dev
Command: npx skills add https://github.com/tarabakz25/my-skills --skill spec-driven-dev-tarabakz25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill prevents confusion for users still referencing the old multi-skill spec pipeline by redirecting them to the current unified spec skill for creating, reviewing, and building specifications. ## Core Features & Use Cases - Deprecation Notice: Clearly marks the old spec-driven-dev workflow as deprecated and merged into the unified /spec skill. - Command Mapping: Maps legacy workflows to new commands, such as spec creation to /spec create, spec review to /spec review, and implementation to /spec build. - Use Case: A user with old documentation referencing /spec-creator or /spec-reviewer loads this Skill and learns to use the unified /spec skill instead. ## Quick Start Ask the agent to load the spec skill at ~/.skills/spec/SKILL.md and run /spec create for your new specification.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema

How do I create a specification with the new spec skill?▼

Use the /spec create command with a slug and optional type argument, for example /spec create my-feature. This replaces the old /spec-creator workflow from the deprecated pipeline.

What happened to the spec-creator and spec-reviewer skills?▼

They were merged into a single unified spec skill located at ~/.skills/spec/SKILL.md. The old multi-skill pipeline is deprecated and should no longer be followed.

How do I review an existing specification?▼

Run /spec review followed by the spec identifier, such as /spec review <spec-id>. This command replaces the standalone spec-reviewer skill from the previous workflow.

Should I still use the spec-driven-dev skill for new projects?▼

No, this skill is deprecated and only exists as a redirect. Load the unified spec skill instead, which handles create, review, and build workflows in one place.