이미지: r/LocalLLaMA 화면 갈무리
Summary
- GitHub has released the open-source project Spec Kit, reportedly earning more than 126K stars
- It provides a six-step command flow that forces AI agents to write a structured spec before writing any code
- It is reportedly compatible with 25+ agents, including Claude Code, Cursor, Copilot, Codex, and Gemini CLI
- 공개 주체
- GitHub
- 저장소 인기
- 126,000개 이상 스타, 8,000개 이상 포크로 알려짐
- 명령어 흐름
- /constitution → /specify → /clarify → /plan → /tasks → /implement
- 호환 에이전트
- Claude Code, Cursor, Copilot, Codex, Gemini CLI 등 25개 이상
- 라이선스
- 오픈소스
What was released
GitHub has released the open-source project Spec Kit. It reportedly gathered more than 126K stars and 8K forks in a short span of time. Spec Kit is a workflow that forces coding agents to write a structured spec first, rather than jumping straight into writing code. The commands flow through six steps. /constitution sets the rules and standards, /specify defines what to build, and /clarify resolves any remaining questions before starting. Then /plan lays out the architecture and tech stack, /tasks breaks the work into an ordered sequence, and /implement moves into execution. It's reportedly compatible with 25+ agents, including Claude Code, Cursor, Copilot, Codex, and Gemini CLI.
What this means
Vibe coding — building apps through natural-language instructions without knowing how to code — often starts from a single short prompt. The problem is a recurring one: the agent grasps only half of the user's intent, churns out code anyway, and the project's structure turns out to be off only after the fact. The concept of spec-first development itself has long existed in software engineering, but efforts to force this habit onto AI agents rather than human developers have only recently gained real momentum. Spec Kit focuses on making agents pause and ask clarifying questions and document things the way a human would before writing code, improving the consistency of the output. GitHub has recently been expanding its agent ecosystem, including releasing a Copilot SDK for Java developers that supports a BYOK approach not tied to any specific model. Spec Kit fits the same pattern, aiming for a standard workflow that spans multiple agents rather than being locked to a single tool.
Why it matters
With an agent-agnostic spec workflow now available as open source, it's become considerably easier for teams to establish shared ground rules when adopting coding agents. Rather than developers simply firing off prompts and waiting for results, a process of first clarifying what's being built and why is more likely to become standard practice. Combined with GitHub's recent string of SDK and agent-tooling releases, this reads as a signal that the next competitive battleground in agentic coding is shifting from raw model performance to workflow standardization.
