What is using-sddpro?

A guide for using the SDDPro software-development workflow, with commands for defining features, writing requirements, building them, testing them, and reviewing code.

Use it to plan features, check project status, run development and quality stages, and investigate failed builds.

It helps teams follow a consistent process instead of jumping into code without agreed requirements and review steps.

using-sddpro — Skill for Claude Code and Codex by zekiriabd

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add zekiriabd/SDD-Pro --skill using-sddpro

Clone the repo

git clone --depth 1 https://github.com/zekiriabd/SDD-Pro

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zekiriabd/sdd-pro/using-sddpro.svg)](https://agentmods.dev/skills/zekiriabd/sdd-pro/using-sddpro)

Your own site

<a href="https://agentmods.dev/skills/zekiriabd/sdd-pro/using-sddpro"><img src="https://agentmods.dev/badge/skills/zekiriabd/sdd-pro/using-sddpro.svg" alt="Measured on agentmods" height="20"></a>

Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,140 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00082	$0.01140
Opus 5	$0.00041	$0.00570
Sonnet 5	$0.00016	$0.00228
Haiku 4.5	$0.00008	$0.00114

Measured 3d ago against content hash 64d4b9c446d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

using-sddpro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.sdd/skills/using-sddpro/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill — Using SDDPro

Auto-trigger pattern (emprunt superpowers v5.1) : ce skill se charge au début de chaque session ET dès qu'une intention dev est détectée. Coût : ~1 KB context. Bénéfice : Claude propose une commande SDD_Pro adaptée au lieu de coder direct.

Quand ce skill s'active

Signal utilisateur	Action recommandée
"Je veux ajouter une fonctionnalité X"	`/feat-generate X` (cadrage 3-6 questions)
"Comment je fais Y ?"	`/sdd-help "Y"` (FAQ contextuelle)
"Que fait ce projet ?"	`/sdd-status` (tree ASCII)
"Ça plante" / "Mon build échoue"	`/sdd-help {n}` puis `query_console_db.py feat-stats --feat {n} --format md`
"Je veux refaire ce code"	Lire l'US source d'abord, jamais re-coder à l'aveugle
"Audit le code"	`/sdd-review {n}` (two-stage : spec gate → quality batch)

Pipeline canonique à respecter

0 (opt)  Discovery (.sdd/templates/{product-brief,prfaq}.template.md)
   ↓
1-2      /feat-generate → /us-generate → /feat-validate
   ↓
4        /dev-run (arch+DB → backend → API gate → frontend)
   ↓
5        /qa-generate → /sdd-review (two-stage v7.0.0+)

Conventions load-bearing à ne JAMAIS violer

Source-first : tout dans .md versionnés (FEATs, US, plans, ADRs). Pas de mémoire opaque dans le LLM.
File ownership matrix (@.sdd/rules/ownership.md) : un seul owner par path. Avant tout Write/Edit sous workspace/src/, vérifier qui possède le path.
Two-stage auditor (v7.0.0+) : spec-compliance-reviewer est un gate (Stage A) qui tourne SEUL. Si 🔴 RED, les 3 autres reviewers (code, security, arch) sont skippés — pas de gaspillage à reviewer du code qui sera réécrit.
Stack .md = SSoT secrets (⚠️ fichier versionné — placeholders ${VAR} uniquement) : DB_PASSWORD, JWT secrets, etc. Code lit via IConfiguration / @Value / Settings(). Jamais process.env direct (sinon [SEC_ENV_VAR_FORBIDDEN]).
Anti-derive : refuser scope hors US, lib hors §2.4 du stack, refactor non demandé. STOP + ERROR avec préfixe [CLASS] (cf. @.sdd/rules/error-classification.md).

Read the full file on GitHub · 84 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 84 lines · 82 tokens per session scan A 64d4b9c446d3

Subscribe to this mod's changes

using-sddpro is a skill published in the GitHub repository zekiriabd/SDD-Pro (191 stars, last pushed 4d ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,140 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Building agents Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens