Borrowing it
Nothing to install: this file belongs to LionelHuanSi/awesome-ai-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LionelHuanSi/awesome-ai-agent-skills/main/.agents/skills/sdd-workflow/SKILL.mdgit clone --depth 1 https://github.com/LionelHuanSi/awesome-ai-agent-skillsWrote 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.
[](https://agentmods.dev/skills/lionelhuansi/awesome-ai-agent-skills/sdd-workflow)<a href="https://agentmods.dev/skills/lionelhuansi/awesome-ai-agent-skills/sdd-workflow"><img src="https://agentmods.dev/badge/skills/lionelhuansi/awesome-ai-agent-skills/sdd-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lionelhuansi/awesome-ai-agent-skills/sdd-workflow"><img src="https://agentmods.dev/badge/skills/lionelhuansi/awesome-ai-agent-skills/sdd-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00040 | $0.00577 |
| Opus 5 | $0.00020 | $0.00289 |
| Sonnet 5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
sdd-workflow 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development (SDD) & Subagent Workflow Skill
This skill implements the Spec-Driven Development methodology sourced from GitHub Spec Kit combined with Claude Code Subagent Parallel Delegation.
Core Principles
- Specification is the Source of Truth: Code is a generated artifact of specifications, not the primary document.
- Intent-Driven Engineering: Shift from ad-hoc "vibe coding" to structured, intent-based software engineering.
- Repository-Native Artifacts: Specifications live in markdown files alongside the codebase.
Workflow Progression & Commands
1. Project Constitution (/constitution)
Establish non-negotiable project principles in .specify/constitution.md.
- Scope: Architecture rules, security boundaries, performance budgets, tech stack constraints.
- Rule: Every code generation task must comply with
constitution.md.
2. High-Level Specification (/specify)
Create feature specifications in .specify/spec.md.
- Focus purely on What needs to be built and Why it matters to users.
- Avoid technical implementation details (no framework choices or DB schema details in spec.md).
- Define unambiguous Acceptance Criteria.
3. Specification Clarification (/clarify)
Audit .specify/spec.md for gaps, ambiguity, and edge cases.
- Identify missing error handling, rate limits, edge conditions, or security boundaries.
- Formulate explicit clarifying questions for human stakeholders.
- Update
spec.mdwith resolved answers.
4. Technical Blueprint & Planning (/plan)
Generate technical design in .specify/plan.md.
- Map specifications to technical components: API endpoints, data models, CORS policy, state management.
- Define explicit contracts and interfaces.
5. Task Breakdown (/tasks)
Decompose implementation into small, atomic, verifiable work items.
- Each task must have a clear verification test or criteria.
- Order tasks logically by dependency order.
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.
- 12d ago First seen · 52 lines · 40 tokens per session scan A 50b16472cb56
sdd-workflow is a skill published in the GitHub repository LionelHuanSi/awesome-ai-agent-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 577 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…