Nprbst Speck
nprbst-speck is a Claude Code plugin for the Build phase that brings spec-kit-style specifications, planning, and spec-aware code review into agent-driven development.
by nprbst · github.com/nprbst/speck
Install Speck when you want github/spec-kit-style specs, planning, and PR-aware reviews wired into Claude Code instead of ad-hoc prompts.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install nprbst-speck@nprbst/speckBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:nprbst/speck") and the paste-ready config with skillselion.get_install_config("plugin:nprbst/speck").
What it does
Speck is an opinionated, extensible derivative of github/spec-kit built for Claude Code builders 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 solo and small-team builders 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.
Highlights
- 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
Why builders use it
Agents and PRs drift from agreed feature intent because specs live in docs while coding happens in unstructured chat.
After you add Speck, features stay tied to structured specs, walkthroughs, and review context so implementation and merges reflect what was actually planned.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 3 stars, 0 votes.
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.
Comments
Share how you use nprbst-speck, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.