Разработка по спецификации до написания кода

★ 8.7 · documentation

spec-driven-development is a Claude Code skill that produces a structured specification before any code is written, turning vague requirements into a shared source of truth agreed upon by the engineer and stakeholder. The workflow runs through four gated phases — Specify, Plan, Tasks, Implement — each requiring explicit human approval before proceeding. When a single request bundles several independently testable capabilities, an optional Phase 0 Scope Check kicks in: Claude proposes a capability map with a module table, dependency direction, and build order, then recurses through the full four-phase cycle for each module. The resulting spec document covers objective and acceptance criteria, full executable build and test commands, project structure, code style illustrated with real snippets, testing strategy, and a three-tier boundary system (always do / ask first / never do). Teams use this skill when starting a new project or feature, working from incomplete requirements, or facing architectural decisions that touch multiple files or modules.