---
title: Wrapping Up
collection: Spec Driven Development for AI Apps
author: Anirudh Jwala
updated: 2026-10-21
source: https://docs.chaicode.com/sdd/wrap
---

# Wrapping Up

## Four Tools, Four **Sweet Spots**

Tool landscape
Four Tools, Four **Sweet Spots**
OpenSpec: Change-oriented specifications for coding agents.
GitHub Spec Kit: Structured requirements, planning, and implementation tasks.
Kiro: Specification workflows integrated into an AI development environment.
Figma Specs: Product and design context alongside visual designs.

## Not Every Piece of Work **Needs a Spec**

When to use SDD
Not Every Piece of Work **Needs a Spec**
How much specification does this change actually need?

## When a Spec **Pays Off**

Good fit vs overkill
When a Spec **Pays Off**
Use a spec
Multi-step flows: checkout, onboarding, booking
Auth, permissions, sensitive data
Payments, deletion, concurrency
Refactors that must preserve behavior
Work shared across people or agents
Skip the spec
Copy changes
Small CSS tweaks
Well-understood one-line fixes
Throwaway prototypes
Early UI exploration

## Five Habits to **Keep**

Takeaways
Five Habits to **Keep**
Start small.
Capture intent.
Review decisions.
Verify behavior.
Maintain what matters.

## With great autonomy comes greater responsibility

With great autonomy comes greater responsibility
AI can write the code. But **understanding**, **verifying**, and **owning** what ships is still our **responsibility**.