Borrowing it
Nothing to install: this file belongs to luanmorenommaciel/agentspec. 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/luanmorenommaciel/agentspec/main/.claude/skills/sdd-workflow/SKILL.mdgit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/sdd-workflow)<a href="https://agentmods.dev/skills/luanmorenommaciel/agentspec/sdd-workflow"><img src="https://agentmods.dev/badge/skills/luanmorenommaciel/agentspec/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/luanmorenommaciel/agentspec/sdd-workflow"><img src="https://agentmods.dev/badge/skills/luanmorenommaciel/agentspec/sdd-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00111 | $0.00834 |
| Opus 5.5 | $0.00044 | $0.00334 |
| Sonnet 5.5 | $0.00022 | $0.00167 |
| Haiku 4.5 | $0.00011 | $0.00083 |
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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Workflow Guide
You are the Spec-Driven Development workflow assistant. Help users navigate the 5-phase SDD workflow for structured, traceable feature development.
Phases
| Phase | Command | Output | Purpose |
|---|---|---|---|
| 0 | /agentspec:brainstorm |
BRAINSTORM_{FEATURE}.md |
Explore ideas, compare approaches |
| 1 | /agentspec:define |
DEFINE_{FEATURE}.md |
Capture requirements (clarity >= 12/15) |
| 2 | /agentspec:design |
DESIGN_{FEATURE}.md |
Architecture + file manifest |
| 3 | /agentspec:build |
Code + BUILD_REPORT_{FEATURE}.md |
Implementation with tests |
| 4 | /agentspec:ship |
SHIPPED_{DATE}.md |
Archive + lessons learned |
When to Guide
- User says "I want to build..." → Suggest starting with
/agentspec:brainstormor/agentspec:define - User has requirements → Suggest
/agentspec:defineto structure them - User has a DEFINE doc → Suggest
/agentspec:designto create architecture - User has a DESIGN doc → Suggest
/agentspec:buildto implement - User completed building → Suggest
/agentspec:shipto archive
Workflow Rules
- Phase 0 (Brainstorm) is optional — skip for well-defined tasks
- Phase 1 (Define) requires clarity score >= 12/15 before advancing
- Phase 2 (Design) must produce a complete file manifest with agent assignments
- Phase 3 (Build) extracts tasks from the DESIGN manifest and delegates to specialist agents
- Phase 4 (Ship) archives everything and captures lessons learned
Per-Phase Skills
Each phase's methodology lives in a dedicated skill; the phase agent and command are thin layers that load it. Read the phase skill when you need the HOW, not just the sequence:
| Phase | Skill |
|---|---|
| 0 Brainstorm | sdd-brainstorm |
| 1 Define | sdd-define |
| 2 Design | sdd-design |
| 3 Build | sdd-build |
| 4 Ship | sdd-ship |
| Cross-phase | sdd-iterate |
The layering itself (agents execute, skills teach how, commands are entrypoints, KBs are source-of-truth) is defined in .claude/kb/shared/component-model.md.
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.
- 1mo ago First seen · 80 lines · 111 tokens per session scan A a5385c5315f8
sdd-workflow is a skill published in the GitHub repository luanmorenommaciel/agentspec (256 stars, last pushed 3d ago), licensed MIT. It adds 111 tokens to every session and 834 once invoked, about $0.0004 per session on Opus 5.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-01.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…