Stefan Cho contributor

Devstefancho Claude Plugins

Run spec-driven development in Claude Code—from brainstorm and specs through tasks, implementation, tests, PR, and desktop alerts when the agent needs you.

Overview

devstefancho-claude-plugins is a plugin marketplace for the build phase that bundles thirteen Claude Code plugins for spec-driven planning, task graphs, tested implementation, git/PR automation, and session notifications

What is this marketplace?

  • 13 plugins covering spec search, task decomposition, implement-with-test, and PR automation
  • writing-specs-plugin: spec-driven dev with search, conflict detection, and reporting
  • writing-tasks-plugin: persistent task files, dependency graph, parallel lanes, progress tracking
  • test-commit-push-pr-clean-plugin: lint, test, commit, push, PR, and worktree cleanup
  • stop-notification-plugin: macOS TTS plus modal/tmux when Claude stops or needs attention
  • Marketplace lists 13 distinct plugins.
  • Named plugins include stop-notification, test-commit-push-pr-clean, writing-specs, writing-tasks, computer-use, implemen

Compatible agents: Claude Code, any compatible agent

Community signal: 10 GitHub stars.

What problem does it solve?

One-person shops lose thread between brainstorm notes, specs, tasks, tests, and PRs when every step is a different manual habit in the terminal.

Who is it for?

Solo builders on macOS-friendly setups who want spec-driven Claude Code workflows with optional Computer Use testing and hands-off git hygiene.

Skip if: Builders who only want a single niche skill, teams without git PR workflows, or non-macOS users who rely solely on stop-notification-plugin.

What do I get? / Deliverables

After registration you can wire a repeatable spec→task→implement→test→PR path and get alerted when Claude Code stops or blocks on you.

  • Searchable specs with conflict reports and structured tasks on disk
  • Implemented code paths covered by tests from specs or direct requests
  • Linted commits, pushed branches, opened PRs, and optional worktree cleanup

Plugins in this marketplace

13 plugins — install individually after you add the marketplace.

Recommended Marketplaces

Journey fit

The canonical shelf is build/pm because the bundle’s spine is specs, tasks, and implementation orchestration that carries work from idea to merge. pm subphase captures decompose-specs, task graphs, and delivery workflow—not a single lint or test utility.

How it compares

Full SDLC-oriented plugin suite, not a single harness-design or UI component marketplace.

Common Questions / FAQ

Who is Devstefancho Claude Plugins for?

It is for indie developers using Claude Code who want structured specs, tasks, implementation with tests, and automated commit/PR steps in one marketplace.

When should I use Devstefancho Claude Plugins?

Use it when you are committing to spec-driven delivery—especially across scope, build, and ship—and want plugins instead of ad hoc prompts for each step.

How do I add Devstefancho Claude Plugins to my agent?

Add the devstefancho/claude-plugins marketplace in Claude Code, enable the plugins you need (specs, tasks, implement-with-test, etc.), and run them from the plugin commands in your repo.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.