Agent Plugins Marketplace
All plugins

sdd-toolkit

v0.40.0

Experimental Codex adapter for the existing SDD Toolkit skills and shared artifact workflow.

CodexClaude Code14 Skills

By Jose Gascon0 GitHub starsUpdated 3 hours ago

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
14 skill or MCP entries
Source updated
Aug 28, 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 plugin

Installs for the current user
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add sdd-toolkit@agent-plugin-marketplace

Paste and run these commands in a terminal with Codex. 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/hardcode83/sdd-toolkit

Clone 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

sdd-toolkit/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
├── skills/archive/SKILL.md
├── skills/auto/SKILL.md
├── skills/design/SKILL.md
├── skills/diagram/SKILL.md
├── skills/doctor/SKILL.md
├── skills/history/SKILL.md
├── skills/init/SKILL.md
├── skills/new/SKILL.md
├── skills/review/SKILL.md
├── skills/reviewer-panel/SKILL.md
├── skills/run/SKILL.md
├── skills/ship/SKILL.md
├── skills/status/SKILL.md
└── skills/tasks/SKILL.md

Included Skills14

archiveskills/archive/SKILL.md

Archive a merged SDD change after objectively verifying its Pull Request, then update living specs, roadmap, metrics, and history. Use when the user runs /sdd:archive after the associated PR is merged.

autoskills/auto/SKILL.md

Run SDD features through local implementation, review, READY_FOR_PR, and Pull Request creation without archiving before merge. Uses one branch+PR per feature and a BLOCKED queue for human decisions. Use when the user runs /sdd:auto, optionally with a count or feature name.

designskills/design/SKILL.md

Write the technical design for an SDD change (sdd/changes/<feature>/design.md) - decisions, affected files, risks. Use when the user runs /sdd:design after the proposal is approved.

diagramskills/diagram/SKILL.md

This skill should be used when the user asks to "generate a diagram", "draw an architecture diagram", "create a flowchart", "make a sequence diagram", "diagram this infrastructure", or mentions diagrams, flowcharts, architecture visualization, C4 diagrams, AWS infrastructure diagrams, Mermaid, PlantUML, or any visual representation of systems, flows, or relationships.

doctorskills/doctor/SKILL.md

Validate SDD state consistency without modifying files. Checks roadmap structure and its dependency graph (cycles, unknown dependencies, order violations), changes, requirements, tasks, archives, blockers, local references, lifecycle metadata, and PR/merge evidence. Use when the user runs /sdd:doctor or asks to diagnose the SDD workspace.

historyskills/history/SKILL.md

Query the project's SDD archive - timeline of completed changes, the full record of one change (decisions, rejected alternatives, cost, commits), or free-form questions about why things are the way they are, answered with citations and a validity check. Use when the user runs /sdd:history or asks why a past decision was made, what a past change did, or what has shipped.

initskills/init/SKILL.md

Bootstrap the SDD (Spec-Driven Development) workflow in this project - generates steering docs, optionally seeds from a planning document, creates a spec baseline for existing codebases, and interactively enables optional MCPs, LSPs and usage metrics. Use when the user runs /sdd:init or asks to set up SDD in a project.

newskills/new/SKILL.md

Start a new SDD change - creates sdd/changes/<feature>/proposal.md with the why, scope, and EARS requirements. Use when the user runs /sdd:new or asks to spec out a feature.

reviewskills/review/SKILL.md

Detect drift between sdd/specs/ and code, or validate an implemented change locally and mark it READY_FOR_PR. Use when the user runs /sdd:review, asks whether specs are up to date, or wants a spec-vs-implementation check.

reviewer-panelskills/reviewer-panel/SKILL.md

Shared logical reviewer planning, Claude compatibility dispatch, native Codex panel dispatch, and fail-closed result validation.

runskills/run/SKILL.md

Implement an SDD change by executing its tasks.md in order, checking tasks off as they are verified. Use when the user runs /sdd:run after tasks are approved.

shipskills/ship/SKILL.md

Publish a change that is READY_FOR_PR - sync the base into its branch, push it, open the Pull Request and record the PR evidence in STATE.md. Use when the user runs /sdd:ship, or accepts the offer at the end of /sdd:review.

statusskills/status/SKILL.md

Show the state of SDD changes - active changes, phase, task progress, and the roadmap as derived views (what is workable now in parallel, dependency waves, critical path per stage, dependency graph). With a feature name, drills into that change's tasks.md - full plan, or filtered by section/pending/done/requirement, for surgical navigation of large task lists. Use when the user runs /sdd:status or asks where a change/the roadmap/a specific task stands, or what can be worked on next.

tasksskills/tasks/SKILL.md

Break an SDD change into an implementation checklist (sdd/changes/<feature>/tasks.md) of small, verifiable tasks referencing the requirements. Use when the user runs /sdd:tasks after proposal (and design, if any) are approved.

Plugin manifests2

.codex-plugin/plugin.json
{
  "name": "sdd-toolkit",
  "version": "0.40.0",
  "description": "Experimental Codex adapter for the existing SDD Toolkit skills and shared artifact workflow.",
  "author": {
    "name": "Jose Gascon",
    "url": "https://github.com/hardcode83"
  },
  "homepage": "https://github.com/hardcode83/sdd-toolkit",
  "repository": "https://github.com/hardcode83/sdd-toolkit",
  "keywords": [
    "sdd",
    "spec-driven-development",
    "codex"
  ],
  "skills": "./skills/",
  "interface": {
    "displayName": "SDD Toolkit",
    "shortDescription": "Approval-gated spec-driven development workflows",
    "longDescription": "Experimental Codex access to the existing SDD Toolkit skills while preserving the Claude Code plugin and shared sdd/ artifacts.",
    "developerName": "Jose Gascon",
    "category": "Developer Tools",
    "capabilities": [
      "Interactive",
      "Write"
    ],
    "websiteURL": "https://github.com/hardcode83/sdd-toolkit",
    "defaultPrompt": [
      "Show the current SDD status.",
      "Start a new SDD change.",
      "Continue the active change with its next SDD phase."
    ]
  }
}
.claude-plugin/plugin.json
{
  "name": "sdd",
  "description": "Spec-Driven Development workflow: proposal → design → tasks → run → review → PR → merge-gated archive, with living specs, deterministic state diagnostics (/sdd:doctor), a multi-agent review panel, autonomous PR creation, a BLOCKED queue, metrics, and queryable history.",
  "version": "0.40.0",
  "author": {
    "name": "Jose Gascon"
  },
  "homepage": "https://github.com/hardcode83/sdd-toolkit",
  "repository": "https://github.com/hardcode83/sdd-toolkit",
  "displayName": "SDD Toolkit"
}

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[sdd-toolkit on Agent Plugins Marketplace](https://pluginsmp.com/plugins/sdd-toolkit)