Nprbst Speck
- 4 repo stars
- Updated December 11, 2025
- nprbst/speck
nprbst-speck is a Claude Code plugin that brings spec-kit-style specifications, planning, and spec-aware code review into agent-driven development.
About
Speck is an opinionated, extensible derivative of github/spec-kit built for Claude Code developers who treat written specifications as the source of truth for features. Rather than jumping straight into code, you use it to keep planning, implementation context, and review aligned so agents and humans share the same definition of done. It targets and small-team developers shipping structured products where PRs need reviewer-grade walkthroughs and spec-linked rationale. Keywords in the bundle—spec-aware workflows, feature management, planning, and code review—signal that Speck is less about one-off codegen and more about governing how work enters the repo. If you already rely on spec-driven development or want to graduate from prompt chaos to repeatable feature rituals, Speck packages that discipline as installable Claude Code plugins you can extend as your process matures.
- Opinionated spec-kit derivative tuned for Claude Code sessions and tooling
- Spec-aware context for implementation and structured change walkthroughs
- Feature-management and planning hooks across the dev workflow
- Pull-request and code-review oriented reviewer flows
- Extensible framework with 2 bundled plugins in the marketplace entry
Nprbst Speck by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install nprbst-speck@nprbst/speckAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 4 |
|---|---|
| Last updated | December 11, 2025 |
| Repository | nprbst/speck ↗ |
What it does
Install Speck when you want github/spec-kit-style specs, planning, and PR-aware reviews wired into Claude Code instead of ad-hoc prompts.
Who is it for?
Best when you're adopting spec-driven development and want Claude Code to honor github/spec-kit patterns end to end.
Skip if: Hackathon throwaway repos or teams that refuse written specs and only want fast snippet generation without review gates.
What you get
After you add Speck, features stay tied to structured specs, walkthroughs, and review context so implementation and merges reflect what was actually planned.
- Spec-aligned agent context during implementation
- Structured review and walkthrough patterns for changes
- Extensible two-plugin bundle as the foundation for your Speck workflow
By the numbers
- Plugin bundle lists 2 plugins
- Catalog metadata reports 3 GitHub stars on nprbst/speck
- Described as an extensible derivative of github/spec-kit optimized for Claude Code
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
Spec-driven development framework for Claude Code, not a generic MCP connector or a single lint skill.
FAQ
Who is Nprbst Speck for?
It is for Claude Code users who want spec-kit-like planning, feature context, and structured reviews instead of improvising every task.
When should I use Nprbst Speck?
Use it when scoping a feature, while implementing against a written spec, or before merging when you need spec-aware PR walkthroughs.
How do I add Nprbst Speck to my agent?
Install the nprbst/speck plugin marketplace entry in Claude Code, enable its two bundled plugins, and wire your repo to your existing spec-kit or Speck workflow conventions.