← Reddit

I built an open-source Claude Code plugin that forces a spec-driven workflow (interview → spec → plan → tasks → code)

Reddit · Murilo776 · June 14, 2026
A developer created Specsmith, an open-source Claude Code plugin designed to enforce a structured workflow that guides development through interview, specification, planning, task definition, and code generation phases. The v0.1 plugin includes prompt-grill for creating unambiguous specifications, a method runner that executes the full workflow pipeline, and dev-lifecycle features for git management including branch handling and conventional commits. The MIT-licensed tool is available for installation through Claude Code and on GitHub, with the creator actively seeking user feedback for refinement.

Detailed Analysis

A developer identified as murilobauck has released Specsmith, an open-source plugin for Claude Code that imposes a structured, specification-driven development workflow before any code generation occurs. The plugin enforces a sequential pipeline — interview, specification, plan, task decomposition, then code — addressing what the author identified as a fundamental failure mode in AI-assisted coding: ambiguous prompts that cause the model to fill in gaps with guesses rather than correctly inferred intent. The core mechanism, `prompt-grill`, interrogates the user with targeted questions until a vague feature request can be rendered as an unambiguous specification document, stored at `specs/<feature>/spec.md`. Subsequent stages convert that spec into a plan, then discrete tasks, and finally code, with each task receiving its own commit. A companion skill, `dev-lifecycle`, manages the Git workflow, enforcing Conventional Commits, branch hygiene off a develop branch, CI/test gates, and a PR that pauses for human approval rather than auto-merging.

The plugin's design philosophy reflects a meaningful diagnosis of why AI coding assistants frequently produce tangled or misaligned output. The author's observation — that more verbose prompting does not fix ambiguity, but structural process does — aligns with a broader pattern of practitioner experience with large language models. Claude and similar models are highly capable of reasoning and code generation, but their outputs are bounded by the clarity of input. When asked to "build feature X," the model must make numerous implicit architectural and behavioral choices; Specsmith front-loads the disambiguation process, converting those implicit choices into explicit, human-approved decisions before the model commits to any implementation path.

This approach connects directly to a growing movement in the AI development tooling ecosystem toward what might be called "agentic scaffolding" — structured frameworks that constrain and sequence LLM behavior rather than relying on single-shot prompting. Claude Code itself, Anthropic's terminal-based agentic coding tool, is designed to handle multi-step autonomous tasks, but without external guardrails, it remains susceptible to the same prompt ambiguity problems the author describes. Plugins like Specsmith represent community-driven efforts to layer engineering rigor — requirements management, version control discipline, human-in-the-loop checkpoints — on top of the raw capability that Claude Code provides.

The release is explicitly positioned as a v0.1 minimum viable artifact, prioritizing method validation over feature completeness. This staged approach is notable because it mirrors software product development best practices applied to developer tooling itself: ship the core loop, observe where it breaks in real use, and iterate. The MIT license and public GitHub repository lower the barrier to inspection and contribution, suggesting the author is building toward community validation rather than proprietary lock-in. The plugin's two-command installation via Claude Code's plugin marketplace also indicates that Anthropic's tooling ecosystem has matured to a point where third-party workflow extensions can be distributed and installed with minimal friction.

Specsmith's existence points to a broader tension in AI-assisted software development: as models become more capable of writing production-quality code, the limiting factor increasingly shifts from model intelligence to human specification quality. The proliferation of such workflow-enforcement tools suggests that practitioners are arriving independently at the same conclusion — that the most impactful productivity gains from AI coding assistants come not from better models alone, but from better-structured human-model collaboration protocols. Whether community-built plugins like Specsmith eventually influence the default behavior of tools like Claude Code remains to be seen, but they serve as practical experiments in what rigorous agentic software development workflows can look like.

Read original article →