sdd-design
v0.1.0Spec-driven design workflow for designers: setup, explore, brief, make (with an independent reviewer loop), wrap-up. Pure Markdown, no dependencies, no telemetry.
By Robin QuinteroLicense: MIT0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 6 skill or MCP entries
- Source updated
- Oct 2, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install sdd-design for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install sdd-design@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/rohaquinlop/spec-driven-designmentClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .claude-plugin/plugin.json├── skills/brief/SKILL.md├── skills/explore/SKILL.md├── skills/make/SKILL.md├── skills/setup/SKILL.md├── skills/wrap-up/SKILL.md└── .mcp.json
Included Skills5
Start a piece of design work by writing a brief — goal, audience, output, references, and acceptance criteria — and a checklist of deliverables. Use when the designer is ready to commit to a direction. Takes a name or idea, e.g. "/sdd-design:brief pricing page".
Thinking partner for designers to investigate an idea, problem, or direction before starting a brief. Use before /sdd-design:brief when the designer wants to discuss options, research, or compare approaches, not produce design work yet.
Produce the design work for a brief, have an independent reviewer check it against the brief and the design rules, and fix what it finds, in rounds, before asking the designer to approve. Use once a brief exists. Optionally takes the brief name, e.g. "/sdd-design:make pricing-page".
Set up or update a project's design rules for sdd-design — sources of truth (such as a Figma library), colors, typography, layout, components, voice, and accessibility. Use the first time a designer works in a folder, or when the design system or brand changes. Optionally takes one area to update, e.g. "/sdd-design:setup colors", or "figma" to re-sync from the Figma library.
Close a finished, designer-approved brief — add the rule changes the designer confirms to the project's design rules and move the brief to the archive. Optionally takes the brief name, e.g. "/sdd-design:wrap-up pricing-page".
MCP servers1
- url
- https://mcp.figma.com/mcp
Plugin manifests1
{
"name": "sdd-design",
"description": "Spec-driven design workflow for designers: setup, explore, brief, make (with an independent reviewer loop), wrap-up. Pure Markdown, no dependencies, no telemetry.",
"version": "0.1.0",
"author": {
"name": "Robin Quintero"
},
"homepage": "https://github.com/rohaquinlop/spec-driven-designment",
"repository": "https://github.com/rohaquinlop/spec-driven-designment",
"license": "MIT"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[sdd-design on Agent Plugins Marketplace](https://pluginsmp.com/plugins/sdd-design)