using-sddpro

Route software development requests through the SDDPro framework workflow.

140|20|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/zekiriabd/SDD-Pro --skill using-sddpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-sddpro
Source: https://github.com/zekiriabd/SDD-Pro/tree/main/.sdd/skills/using-sddpro
Command: npx skills add https://github.com/zekiriabd/SDD-Pro --skill using-sddpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents ad-hoc software development by routing development requests through the SDDPro framework's canonical workflow, ownership rules, and validation gates.

Core Features & Use Cases

  • Intent Routing: Maps feature requests, questions, failures, status checks, and code audits to the appropriate SDDPro command.
  • Pipeline Guidance: Enforces the progression from feature and user-story definition through development, QA, and two-stage review.
  • Guardrails: Applies source-first development, file ownership checks, stack constraints, anti-derive rules, and standardized error handling.
  • Use Case: When a user asks to add a feature or fix a development issue, use this Skill to recommend the correct SDDPro command before making changes.

Quick Start

Use the using-sddpro skill to assess the user's development intent and recommend the appropriate SDDPro workflow command.

Frequently Asked Questions about using-sddpro

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

FAQPage Schema
How do I prevent ad-hoc implementation when routing software development requests?

SDDPro provides a canonical development workflow that maps feature requests, debugging, and code audits to appropriate commands, enforcing stack compliance, anti-derive safeguards, and two-stage review gates instead of ad-hoc implementation.

What is source-first planning in software development workflows?

Source-first planning is a guardrail that requires development requests to pass through framework-defined workflow routing and ownership validation before implementation, preventing unstructured code changes.

How do I apply two-stage review gates for code reviews and debugging?

Route code reviews and debugging tasks through the SDDPro pipeline to enforce progression from feature definition through development and QA, applying two-stage review gates before final approval.

Does SDDPro workflow routing support feature development and user-story creation?

SDDPro workflow routing maps feature development and user-story creation intents to specific commands, enforcing stack compliance and file ownership rules throughout the development pipeline.

What are the limitations of ad-hoc implementation compared to structured development guardrails?

Ad-hoc implementation lacks file ownership validation, stack compliance checks, and anti-derive safeguards, leading to unstructured code changes that bypass standardized error classification and two-stage review gates.

When should I use workflow routing instead of direct code changes for debugging?

Use workflow routing for debugging when you need standardized error classification, source-first planning, and ownership validation to ensure fixes comply with framework guardrails before implementation.