Developer shares a spec-driven development workflow with Claude Code

On October 19, 2026, the Chinese developer site Juejin published an article by a developer describing a spec-driven development (SDD) workflow that runs on Claude Code without relying on any third-party framework. The author defines a spec as a short functional brief that answers three questions: what to build, what not to build, and what counts as done. In AI-assisted coding, the argument goes, a spec gains a second reader beyond humans, one that reads carefully and follows instructions closely.

The workflow puts that brief into a spec document stored in a specs/ directory. Custom Claude Code commands then generate a technical plan and a task list in sequence, with a human confirming each step. The author uses adding tag filtering to a to-do list API as the worked example and publishes spec, plan, and tasks command templates that readers can copy directly. The article also notes that GitHub's open-source Spec Kit and Amazon's Kiro promote similar ideas with differing details, and that their common backbone can be summarized in four steps. Splitting business concerns from technical ones into separate stages, the author says, keeps the two from blurring together.

The piece contrasts SDD with vibe coding: writing the documents costs roughly ten extra minutes, but saves hours of back-and-forth, and every line of code carries a recorded reason for existing, which helps with review, handover, and debugging. The material ends there, with the workflow presented as one developer's personal practice and templates; no further developments are reported.