Book-Reader-Assist/library/Spec Driven Development/Front-Matter/Front-Matter-source-text.md

Spec Driven Development — Front-Matter: Front matter (cover, title, contents)

• Source: /library/Spec Driven Development/source-file.pdf
• PDF pages: 1–10
• Pages without text: 1

---

Spec Driven Development J.C. Ködel

Spec Driven Development

1. About the author
2. 0 - Why SDD is essential in the age of AI
3. The thesis: knowledge and specification are leverage
4. The three arguments: judge, decide, answer
5. The 70% and the 30%
6. What SDD is, in plain language
7. SDD is not exactly new
8. The next step
9. 0b - Trilogy map: what lives in each volume
10. 1 - Fundamentals: where SDD comes from
11. Waterfall: the right instinct, the wrong cost
12. The agile turn: learning to iterate cheaply
13. Scrum, the pillar; XP and Kanban, the support
14. What each method taught us
15. SDD: the synthesis that only now became viable
16. Why AI needs specification
17. The cycle, now with a name
18. The next step
19. 2 - Anatomy of a specification
20. From vague intent to a blueprint
21. What a spec is (and what it isn't)

1. The why part: problem and intent
2. The scope part: in, out, and non-goals
3. The behavior part: scenarios, rules, and acceptance criteria
4. The edges: exceptions, assumptions, and dependencies
5. The whole blueprint and what makes a spec good
6. The next step
7. 2b - Requirement Language: Writing What the AI Executes Without Guessing
8. The Blueprint Is Right, the Handwriting Is Not
9. Where Specifications Come From
10. Before Anything: Functional or Technical
11. EARS: The Syntax That Will Not Let the Condition Stay Implicit
12. Given/When/Then: Behavior as a Scene
13. Design by Contract: What Holds Before, After and Always
14. ATDD: The Acceptance Criterion Written First
15. Which to Use, and When
16. What a Badly Formed Sentence Costs an Agent
17. 2c - The Scope of a Spec: How Much Fits in One Specification
18. The Question That Comes Before Writing
19. The Criterion: A Spec Is What Fits in One Lap
20. Completing and Reopening Fit Together; Creating and Deleting Do Not
21. When the Feature Is Too Big
22. When the Method Does Not Pay Off
23. What You Take From Here
24. 3 - Hands on: the SDD tools

1. From the blueprint to the wall
2. Three ways of doing the same thing
3. The cycle is the same, the incarnation changes
4. The honest comparison
5. The choice and why
6. Lean setup and first contact
7. The bridge to the full cycle
8. 4 - speckit constitution: the rules before the first move
9. The rules before the first move
10. What a project constitution is
11. What goes in and what stays out
12. Running the constitution step on the To-Do
13. The To-Do's constitution, principle by principle
14. Why the stack stays out
15. Living artifact and the bridge to the first spec
16. 4.5 - Appendix: the To-Do constitution
17. To-Do Constitution
18. Core Principles
19. Engineering Standards
20. Workflow
21. Governance
22. 5 - The complete SDD cycle
23. Before the first specify , a map
24. What you're learning is the cycle, not the app
25. The feature lives on a branch: main → branch → merge
26. The map in a single figure

1. The constitution sits above the loop
2. The loop, step by step
3. The artifacts talk to each other; that's why you clear the context
4. The map is drawn: the bridge to Ch. 6
5. 6 - Create and list tasks: the first complete loop
6. From the map to the ground: the first feature
7. One feature at a time: the backlog
8. Spotlight: specify in action
9. The anatomy from Ch. 2, actually filled in
10. What is spec and what is plan : the boundary
11. The rest of the loop, at a follow-along pace
12. Commit, merge, and the bridge to Ch. 7
13. 6.5 - Creating and listing tasks in practice: the whole loop, file by file
14. How to read this chapter
15. The input: the /speckit-specify prompt
16. What specify and clarify returned: spec.md
17. The requirements check: checklists/requirements.md
18. What plan decided: plan.md
19. The plan ‘s design artifacts
20. The execution list from tasks : tasks.md
21. The code implement generated
22. The portrait of the lap
23. 6b - Specification Anti-Patterns: Six Ways to Get It Wrong, Over and Over
24. Six Defects, All Taken From This App

1. 1. A Rule Inherited by Reference
2. 1. Initial State Left Undeclared
3. 1. A Verb With Two Owners
4. 1. A Repeated Edge With No Answer
5. 1. Scope That Grows Out of Convenience
6. 1. Fixing at the End of the Chain
7. The Checklist, in Six Questions
8. 7 - Completing a Task: When the Obvious Hides Decisions
9. The state of git, again
10. The feature of the moment, and specify at a light pace
11. “Completing” seems obvious. It is not.
12. The answers go back into the spec
13. What changes down the line
14. How to distrust the obvious
15. End of the loop and the bridge to Ch. 8
16. 7.5 - Completing and Reopening a Task in Practice: the Whole Loop, File by File
17. How to read this chapter
18. The input: the /speckit-specify prompt
19. What specify and clarify returned: spec.md
20. What plan decided: plan.md
21. The plan ‘s state model: data-model.md
22. The tasks execution list: tasks.md
23. The code implement generated
24. The portrait of the lap
25. 8 - Filtering Tasks: The Spotlight on plan and checklist
26. The third loop starts on main

specify and clarify , at a light pace 3. The what is already decided; the how is missing 4. Spotlight: plan decides the how 5. The constitution check has teeth 6. Spotlight: checklist as a quality gate 7. Closing the loop, at a light pace 8. The bridge to Ch. 9 9. 8.5 - Filtering Tasks in Practice: the Whole Loop, File by File

1. How to read this chapter
2. The input: the /speckit-specify prompt
3. What specify and clarify returned: spec.md
4. The requirements review: checklists/requirements.md
5. What plan decided: plan.md
6. The plan ‘s view model: data-model.md
7. The tasks execution list: tasks.md
8. The code implement generated
9. The portrait of the lap
10. 9 - Deleting a Task: The Spotlight on tasks and analyze
11. The fourth loop starts: 004-excluir-tarefa
12. The early steps, at a light pace

tasks : the plan turns into a list of steps 4. Why this order: TDD and layers 5. analyze : reading the three artifacts together 6. A real conflict: the deletion against “completing” 7. Fix at the source, and the cascade it triggers 8. From the branch to the merge, and the bridge to Ch. 10 21. 9.5 - Deleting a Task in Practice: the Whole Loop, File by File

1. How to Read This Chapter
2. The Input: the /speckit-specify Prompt
3. What specify and clarify Returned: spec.md
4. The Completeness Check: checklists/requirements.md
5. What plan Decided: plan.md
6. The analyze Report: analyze-report.md
7. The plan ‘s Model of the Operation: data-model.md
8. The tasks Execution List: tasks.md
9. The Code implement Generated
10. The Portrait of the Lap
11. 10 - Edit Task: The Spotlight on implement
12. The Last Loop Starts on main
13. From specify to analyze , at a Light Pace

implement Reads the Artifacts, Not the Chat 4. Red, Green, Refactor 5. Reviewing What the Agent Wrote 6. Loop Closed, App Complete 3. 10.5 - Editing a Task in Practice: the Whole Loop, File by File

1. How to Read This Chapter
2. The Input: the /speckit-specify Prompt
3. What specify and clarify Returned: spec.md
4. The Completeness Check: checklists/requirements.md
5. What plan Decided: plan.md
6. The analyze Report: analyze-report.md
7. The plan ‘s Model of the Operation: data-model.md
8. The tasks Execution List: tasks.md
9. The Code implement Generated

1. The Second Iteration, in the Order It Happened
2. The Portrait of the Lap, and of the Five
3. 10b - Iterative Refinement: The Spec After It Already Exists
4. No Document Is Born Finished
5. Four Doors the Change Comes Through
6. The Chain, in the Order Things Move
7. What Changes and What Does Not
8. When the Spec Stops Being Trustworthy
9. The Document That Outlives the Project
10. 11 - The Whole App Was Born From Five Loops
11. Stop and Look Back
12. The Whole App Is Five Merges Into main
13. The Timeline in One Figure
14. Each Feature Lit a Spotlight
15. Together, They Covered the Whole Cycle
16. One Constitution Governed the Five Loops
17. The Cycle Is Yours Now
18. What If I Did This Without SDD?
19. The To-Do Was the Vehicle; the Process Was the Protagonist
20. Canonical Glossary
21. Terms
22. Rules