sdd-development

Redirect sdd-development invocations to the canonical sdd-dev skill.

13|6|Updated Apr 14, 2026

Search Tags:#workflow #development #spec-driven #alias #redirect #sdd-dev

Ready to run

npx skills add https://github.com/baekenough/second-brain --skill sdd-development-baekenough

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-development
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/sdd-development
Command: npx skills add https://github.com/baekenough/second-brain --skill sdd-development-baekenough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aliases the sdd-development invocation to the canonical sdd-dev skill to ensure a consistent Spec-Driven Development process.

Core Features & Use Cases

Alias redirection to the sdd-dev skill to unify workflow and prompts.
Maintains invocation semantics so existing prompts and task descriptions work unchanged.
Suitable for teams adopting a standard spec-driven development process across tools.

Quick Start

Invoke the sdd-development alias to run the sdd-dev workflow.

Frequently Asked Questions about sdd-development

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

FAQPage Schema

What is spec-driven development and how does it structure a coding workflow?▼

Spec-driven development is a workflow that uses formal specifications to guide the implementation process. It unifies prompts and task descriptions to ensure a consistent development process across tools.

How do I start a spec-driven development workflow for my project?▼

To start spec-driven development, invoke the alias to run the canonical workflow. It redirects your invocation to the main implementation while preserving your existing prompts and task descriptions unchanged.

Can I use this alias if my team already has existing spec-driven development prompts?▼

Yes, you can use this alias with existing prompts. It maintains invocation semantics so existing task descriptions work unchanged, redirecting to the canonical skill for execution without altering your inputs.

Why do I need an alias for a spec-driven development workflow instead of the main skill?▼

You need an alias to unify the workflow under a standard name. It ensures team members invoking different names are redirected to the same canonical spec-driven development process.

Does this spec-driven development alias require any specific dependencies to run?▼

The spec-driven development alias requires no specific dependencies to run. It relies solely on the target skill for execution, redirecting the invocation to the canonical implementation file.

What are the limitations of using an alias for spec-driven development?▼

The limitation of this alias is that it does not execute tasks itself. It purely redirects invocations to the canonical skill, meaning the target skill must be present for the workflow to function.