Spec-driven development in reverse: write the code, keep the receipt

Описание и применение

SlimSpec упрощает процесс разработки, сокращая токенов и удаляя лишние спецификации, ускоряя цикл и уменьшая количество коммитов.

Задача

Developers were forced to generate extensive spec artifacts that modern LLMs could ignore, leading to slow, token‑heavy workflows and unnecessary git commits.

Результат

SlimSpec reduces token consumption by ~35%, eliminates unnecessary spec files from git, and speeds up the development cycle by removing redundant steps.

Рабочий процесс

• 1. Explore: a scanner subagent reads module specs and code, producing a brief in explore.md (goal, non‑goals, decisions, risks).
• 2. Gate: main session reviews explore.md and decides to proceed.
• 3. Plan: planner creates tasks.md with waves and lanes, writing first failing tests.
• 4. Gate: main session reviews plan.
• 5. Apply: implementers work through lanes, reporting red/green per task.
• 6. Verify: reviewer checks against plan and design, auto‑fixes bugs, patches explore.md for design questions.
• 7. Ground: final review and merge.

Доказательства

On a real project a comparable change cost it 29.7M tokens versus 45.7M for OpenSpec, and not a single line of process files ended up in git.

Источник

SlimSpec keeps the parts of SDD that work and throws out the rest.

Источник