Search everything...

Stats

Actions

Available In

spec-driven-development

Name: spec-driven-development
Author: ririnto

By ririnto

Spec-first workflow: research unknowns, write abstract requirements in SPEC.md, get approval, implement, verify completeness.

npx claudepluginhub ririnto/sinon --plugin spec-driven-development

Popularity

Stars

Med: 0·Avg: 285

Installs

Med: 0·Avg: 1

What's Inside

Agents1

spec-driven-development

/spec-driven-development

Use this agent when the user wants a spec-first workflow, needs `SPEC.md` artifacts authored or revised before implementation, wants research and contract notes captured alongside the spec, or needs implementation checked against an approved specification. Examples: <example> Context: A feature should be designed before any code changes user: "Write the spec for this feature before we implement it" assistant: "I'll use the spec-driven-development agent to produce the spec artifacts and gate implementation on approval." <commentary> The user is explicitly asking for the ordinary spec-first workflow. </commentary> </example> <example> Context: Existing spec artifacts need refinement user: "Revise SPEC.md and CONTRACT.md for the billing retry work" assistant: "I'll use the spec-driven-development agent to tighten the spec artifacts before implementation continues." <commentary> Updating the specification set is part of the core role. </commentary> </example> <example> Context: Code needs verification against an approved spec user: "Check whether this implementation still matches the approved SPEC.md" assistant: "I'll use the spec-driven-development agent to compare the implementation with the approved specification and report drift." <commentary> Verification against an approved spec is a standard use case. </commentary> </example>

Skills1

spec-driven-development

/spec-driven-development

Drive implementation through a SPEC.md-first workflow covering research, review gates, approved-spec execution, and completeness verification. Use this skill when the user explicitly asks to follow a spec-driven workflow, write a SPEC.md before implementing, create a specification, define requirements before coding, or use a spec-first approach. Covers the full lifecycle: research external unknowns, author SPEC.md, pass review gates, implement against the approved spec, and verify completeness. Activated only on explicit user request, not automatically.

Stats

Version1.0.0

LanguagePython

Stars0

MaintenanceExcellent

LicenseApache-2.0

Last CommitApr 24, 2026

AddedApr 24, 2026

Actions

View on GitHub View README Plugin Marketplace JSON Homepage

Own this plugin?

Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).

Available In

sinon

Safety Signals

Caution

Uses power tools

Uses Bash, Write, or Edit tools

README

Sinon is a universal AI plugin marketplace repository.

This repository uses the official marketplace paths for Claude Code and Codex, with plugins stored under plugins/.

Purpose

Publish curated marketplace catalogs from a Git repository.
Represent plugins for multiple AI runtimes without splitting plugin source trees.
Store installable plugin packages in a consistent directory layout.
Keep runtime-specific marketplace metadata and plugin manifests aligned.

Repository Structure

README.md: repository overview and contribution context.
.gitignore: development ignore rules.
.markdownlint.jsonc: Markdown lint configuration.
.claude-plugin/marketplace.json: Claude marketplace catalog.
.agents/plugins/marketplace.json: Codex marketplace catalog.
plugins/: plugins maintained in this repository.

Marketplace Layout

Plugins are stored under plugins/.

Each plugin directory can expose one or more runtime manifests from the same plugin root.

.claude-plugin/plugin.json: Claude plugin manifest.
.codex-plugin/plugin.json: Codex plugin manifest. Optional plugin assets such as README.md, .mcp.json, .app.json, commands/, agents/, skills/, and assets/ live beside those manifests at the plugin root.

The repository keeps separate official marketplace catalogs per runtime.

Current Plugins

This list describes the plugins currently published through the repository marketplace catalogs.

plugins/git-workflow: Git workflow plugin with practical guidance for commit readiness, Conventional Commit drafting, staged-change hygiene, and template-aware GitHub pull request or GitLab merge request body drafting.
plugins/java: Java development plugin with practical skills for syntax boundaries, language design, testing workflows, dependency decisions, performance analysis, and JDTLS-assisted editing.
plugins/jvm: JVM development assistant with shared skills for tooling workflows, runtime diagnostics, and garbage-collection guidance.
plugins/kotlin: Kotlin development plugin with practical skills for idiomatic language design, coroutines and Flow decisions, Kotlin testing workflows, and kotlin-lsp-assisted editing.
plugins/spring: Spring development plugin with practical skills for Spring Boot, Web, Data, transactions, observability, Batch, Integration, Cloud, and Kafka workflows.
plugins/observability-assets: Prometheus and Grafana plugin with practical skills for alert-rule design, recording-rule support, promtool validation, dashboard JSON authoring, and Grafana mixin workflows for version-controlled observability assets.
plugins/reactor: Project Reactor plugin with practical skills for Flux and Mono composition, scheduler selection, Sinks and ConnectableFlux hot-source design, and reactor-test workflows with StepVerifier, TestPublisher, PublisherProbe, and virtual time.
plugins/netty: Netty and Reactor Netty plugin with practical skills for high-performance network applications, bootstrap and pipeline design, ByteBuf and codec handling, and reactive HTTP/TCP/UDP workflows with Reactor Netty.

Publishing Model

.claude-plugin/marketplace.json is the Claude marketplace catalog.

.agents/plugins/marketplace.json is the Codex marketplace catalog.

Individual plugin directories remain the source of truth for plugin-specific runtime manifests and bundled assets.

Bundled upstream plugins may support only a subset of runtimes. In some cases, this repository may add minimal runtime metadata such as .codex-plugin/ while leaving the upstream plugin content otherwise intact.

Registering This Marketplace in Claude Code

Claude Code supports registering marketplaces from GitHub repositories, generic git URLs, direct URLs to marketplace.json, and local paths.

For this repository, use a GitHub repository, git URL, or local path. Sinon currently uses relative plugin sources such as ./plugins/java inside .claude-plugin/marketplace.json, so a direct HTTP URL to the catalog file is not a safe distribution path for this marketplace.

The Claude marketplace catalog for this repository is:

.claude-plugin/marketplace.json

Interactive registration

/plugin marketplace add /path/to/sinon

/plugin marketplace add ririnto/sinon

/plugin marketplace add https://github.com/ririnto/sinon.git

After Claude Code registers the sinon marketplace, install a plugin from it with:

/plugin install <plugin>@sinon

Examples:

View full README on GitHub

spec-driven-development

Popularity

What's Inside

Confidence

README

Purpose

Repository Structure

Marketplace Layout

Current Plugins

Publishing Model

Registering This Marketplace in Claude Code

Interactive registration

Similar Plugins

feature-dev

nature-skills

ecc

context7-plugin

More by ririnto

kotlin

jvm

harness-engineering

netty

spring

Purpose

Repository Structure

Marketplace Layout

Current Plugins

Publishing Model

Registering This Marketplace in Claude Code

Interactive registration

Popularity

Health & Quality

More by ririnto

kotlin

jvm

harness-engineering

netty

spring

Similar Plugins

feature-dev

nature-skills

ecc

context7-plugin