vidtheque.

read-only demo

Videos IddXPepIAS4

Using Spec-Driven Development for Production Workflows - Erik Hanchett, AWS

index_state ready data_status ok

AI Engineer· published 2026-06-28· 0:17:47· en-US· indexed 2026-08-11 08:05

Open on YouTube

Scene timeline

  1. Shot 0, 0:00 to 0:09, 1 of 1 keyframes kept
  2. Shot 1, 0:09 to 0:31, 1 of 1 keyframes kept
  3. Shot 2, 0:31 to 1:02, 1 of 1 keyframes kept
  4. Shot 3, 1:02 to 1:13, 1 of 1 keyframes kept
  5. Shot 4, 1:13 to 1:45, 1 of 1 keyframes kept
  6. Shot 5, 1:45 to 2:17, 0 of 1 keyframes kept
  7. Shot 6, 2:17 to 2:44, 1 of 1 keyframes kept
  8. Shot 7, 2:44 to 3:03, 1 of 1 keyframes kept
  9. Shot 8, 3:03 to 3:36, 1 of 1 keyframes kept
  10. Shot 9, 3:36 to 4:08, 1 of 1 keyframes kept
  11. Shot 10, 4:08 to 4:41, 1 of 1 keyframes kept
  12. Shot 11, 4:41 to 5:07, 1 of 1 keyframes kept
  13. Shot 12, 5:07 to 5:32, 1 of 1 keyframes kept
  14. Shot 13, 5:32 to 5:57, 1 of 1 keyframes kept
  15. Shot 14, 5:57 to 6:23, 1 of 1 keyframes kept
  16. Shot 15, 6:23 to 7:02, 1 of 1 keyframes kept
  17. Shot 16, 7:02 to 7:51, 1 of 1 keyframes kept
  18. Shot 17, 7:51 to 8:26, 1 of 1 keyframes kept
  19. Shot 18, 8:26 to 8:37, 1 of 1 keyframes kept
  20. Shot 19, 8:37 to 9:08, 1 of 1 keyframes kept
  21. Shot 20, 9:08 to 9:40, 1 of 1 keyframes kept
  22. Shot 21, 9:40 to 9:52, 1 of 1 keyframes kept
  23. Shot 22, 9:52 to 10:20, 1 of 1 keyframes kept
  24. Shot 23, 10:20 to 10:47, 1 of 1 keyframes kept
  25. Shot 24, 10:47 to 11:25, 1 of 1 keyframes kept
  26. Shot 25, 11:25 to 12:06, 1 of 1 keyframes kept
  27. Shot 26, 12:06 to 12:12, 1 of 1 keyframes kept
  28. Shot 27, 12:12 to 12:54, 1 of 1 keyframes kept
  29. Shot 28, 12:54 to 13:00, 1 of 1 keyframes kept
  30. Shot 29, 13:00 to 13:22, 1 of 1 keyframes kept
  31. Shot 30, 13:22 to 13:51, 1 of 1 keyframes kept
  32. Shot 31, 13:51 to 14:16, 1 of 1 keyframes kept
  33. Shot 32, 14:16 to 14:44, 1 of 1 keyframes kept
  34. Shot 33, 14:44 to 14:47, 1 of 1 keyframes kept
  35. Shot 34, 14:47 to 15:21, 1 of 1 keyframes kept
  36. Shot 35, 15:21 to 15:29, 1 of 1 keyframes kept
  37. Shot 36, 15:29 to 15:32, 1 of 1 keyframes kept
  38. Shot 37, 15:32 to 15:35, 1 of 1 keyframes kept
  39. Shot 38, 15:35 to 15:38, 1 of 1 keyframes kept
  40. Shot 39, 15:38 to 15:45, 1 of 1 keyframes kept
  41. Shot 40, 15:45 to 16:04, 1 of 1 keyframes kept
  42. Shot 41, 16:04 to 16:06, 0 of 1 keyframes kept
  43. Shot 42, 16:06 to 16:09, 1 of 1 keyframes kept
  44. Shot 43, 16:09 to 16:12, 1 of 1 keyframes kept
  45. Shot 44, 16:12 to 16:15, 1 of 1 keyframes kept
  46. Shot 45, 16:15 to 16:18, 1 of 1 keyframes kept
  47. Shot 46, 16:18 to 16:21, 1 of 1 keyframes kept
  48. Shot 47, 16:21 to 16:23, 1 of 1 keyframes kept
  49. Shot 48, 16:23 to 16:31, 1 of 1 keyframes kept
  50. Shot 49, 16:31 to 16:33, 0 of 1 keyframes kept
  51. Shot 50, 16:33 to 16:48, 1 of 1 keyframes kept
  52. Shot 51, 16:48 to 16:51, 1 of 1 keyframes kept
  53. Shot 52, 16:51 to 16:52, 1 of 1 keyframes kept
  54. Shot 53, 16:52 to 16:55, 1 of 1 keyframes kept
  55. Shot 54, 16:55 to 17:00, 1 of 1 keyframes kept
  56. Shot 55, 17:00 to 17:09, 1 of 1 keyframes kept
  57. Shot 56, 17:09 to 17:10, 1 of 1 keyframes kept
  58. Shot 57, 17:10 to 17:28, 1 of 1 keyframes kept
  59. Shot 58, 17:28 to 17:35, 1 of 1 keyframes kept
  60. Shot 59, 17:35 to 17:45, 1 of 1 keyframes kept
  61. Shot 60, 17:45 to 17:46, 0 of 1 keyframes kept

61 shot(s).

keyframes kept every frame deduplicated

What was stored

cues
223
whisperx 223
chunks
33
from 223 cues
keyframes
57
kept of 61 captured
frames with text
57
2,972 lines read
chapters
0
from the source metadata
keyframe bytes
9.5 MB
word timings on 223 cues

Provenance

Each pipeline stage, its state and the model that produced it
stage state model started took
fetch done — 2026-08-11 08:01 1m 51s
stt done — 2026-08-11 08:02 19s
chunk done — 2026-08-11 08:03 0s
text_embed done — 2026-08-11 08:03 0s
keyframe done — 2026-08-11 08:03 1m 10s
ocr done — 2026-08-11 08:04 57s
frame_embed done — 2026-08-11 08:05 9s

Frames, and what the machine read

  • 0:04 #0 done6 line(s)

    shot 0·sharpness 886.5

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR · SF0.95
    3. spec.md1.00
    4. Spec-Driven1.00
    5. Development1.00
    6. build1.00

  • 0:16 #1 done10 line(s)

    shot 1·sharpness 1215.4

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR · SF0.95
    3. spec.md0.99
    4. What is Spec-Driven1.00
    5. Development?1.00
    6. And how can it make code1.00
    7. faster?1.00
    8. aws1.00
    9. © 2026, Amazon Web Servicesinc. or its affliates. All rights reserved.0.93
    10. build1.00

  • 0:41 #2 done10 line(s)

    shot 2·sharpness 1650.5

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR · SF0.96
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. Structured specifications1.00
    6. are created before any1.00
    7. code is written.1.00
    8. aws1.00
    9. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.96
    10. build1.00

  • 1:06 #3 done8 line(s)

    shot 3·sharpness 850.8

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR· SF0.96
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. why?0.97
    6. aws1.00
    7. © 2026, Amazon Web Services, Inc. or its afflites. All rights reserved.0.94
    8. build1.00

  • 1:19 #4 done9 line(s)

    shot 4·sharpness 1095.4

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR · SF0.95
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. Al Intern0.94
    6. AI0.82
    7. aws1.00
    8. © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved.0.97
    9. build1.00

  • 2:10 #5 skipped

    shot 5·duplicate of #4

  • 2:40 #6 done10 line(s)

    shot 6·sharpness 1507.3

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR· SF0.96
    3. spec.md0.98
    4. Erik Hanchett1.00
    5. Senior Developer Advocate1.00
    6. 15+ Software Development1.00
    7. Connect with me on LinkedIn!0.98
    8. aws1.00
    9. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.95
    10. build1.00

  • 2:59 #7 done10 line(s)

    shot 7·sharpness 1470.6

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR · SF0.96
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. Can't the latest0.99
    6. frontier models1.00
    7. do everything?0.98
    8. aws1.00
    9. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.95
    10. build1.00

  • 3:10 #8 done10 line(s)

    shot 8·sharpness 1474.1

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR· SF0.97
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. Can't the latest0.99
    6. frontier models1.00
    7. do everything?0.98
    8. aws1.00
    9. © 2026, Amazon Web Services, Inc. or its afflates. All rights reserved.0.94
    10. build1.00

  • 3:52 #9 done11 line(s)

    shot 9·sharpness 1535.2

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR · SF0.96
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. Let's keep a few0.99
    6. things in mind1.00
    7. before we get0.99
    8. too far!1.00
    9. aws1.00
    10. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.96
    11. build1.00

  • 4:19 #10 done9 line(s)

    shot 10·sharpness 1090.1

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR· SF0.97
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. Too much context!1.00
    6. Models get confused!1.00
    7. aws1.00
    8. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.96
    9. build-0.94

  • 4:47 #11 done9 line(s)

    shot 11·sharpness 1244.8

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR · SF0.97
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. AGENTS.md1.00
    6. Steering1.00
    7. aws1.00
    8. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.96
    9. build1.00

  • 5:27 #12 done11 line(s)

    shot 12·sharpness 1144.3

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR · SF0.94
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. Too much1.00
    6. Trust!0.99
    7. Are we code1.00
    8. reviewing?1.00
    9. aws1.00
    10. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.96
    11. build-0.93

  • 5:35 #13 done11 line(s)

    shot 13·sharpness 1176.2

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR · SF0.97
    3. spec.md0.96
    4. Spec-Driven Development1.00
    5. Too much1.00
    6. Trust!0.99
    7. Are we code1.00
    8. reviewing?1.00
    9. aws1.00
    10. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.96
    11. build1.00

  • 6:08 #14 done10 line(s)

    shot 14·sharpness 1388.5

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR· SF0.97
    3. spec.md1.00
    4. Spec-Driven Development1.00
    5. Setup_ AI Code0.98
    6. Reviews As1.00
    7. We110.96
    8. aws1.00
    9. © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved.0.96
    10. build0.99

  • 6:39 #15 done7 line(s)

    shot 15·sharpness 810.5

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR · SF0.94
    3. spec.md1.00
    4. History lesson...0.99
    5. aws1.00
    6. © 2026, Amazon Web Services inc. or its affliates. All rights reserved.0.91
    7. build1.00

  • 7:26 #16 done11 line(s)

    shot 16·sharpness 1301.0

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR· SF0.96
    3. spec.md1.00
    4. Introducing Kiro1.00
    5. Kiro is a new Al IDE coding assistant,0.99
    6. 08000.75
    7. +@0×0.79
    8. Let's build0.99
    9. aws0.98
    10. © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved.0.98
    11. build1.00

  • 8:05 #17 done16 line(s)

    shot 17·sharpness 1212.5

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR· SF0.97
    3. spec.md1.00
    4. Website! Kiro.dev1.00
    5. ()0.75
    6. COAMGELOG0.83
    7. PRICING0.88
    8. 00cs0.90
    9. Alongside you from concept to1.00
    10. production1.00
    11. Kiro is an AI IDIt thwt helps you0.90
    12. ①0.51
    13. +800.70
    14. aws1.00
    15. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.94
    16. build0.99

  • 8:29 #18 done8 line(s)

    shot 18·sharpness 965.2

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR · SF0.96
    3. spec.md1.00
    4. How do you do this without1.00
    5. Kiro?1.00
    6. aws1.00
    7. © 2026, Amazon Web Services inc. or its affliates. All rights reserved.0.92
    8. buitd-0.99

  • 8:58 #19 done10 line(s)

    shot 19·sharpness 1649.1

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR · SF0.96
    3. spec.md1.00
    4. What do you need to tell your IDE?1.00
    5. Tell the Al IDE what it should do0.98
    6. Include the following:1.00
    7. User Requirements1.00
    8. aws1.00
    9. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.95
    10. build1.00

  • 9:36 #20 done13 line(s)

    shot 20·sharpness 2496.1

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR· SF0.96
    3. spec.md1.00
    4. What do you need to tell your IDE?1.00
    5. Tell the Al IDE what it should do0.98
    6. Include the following:1.00
    7. User Requirements1.00
    8. Design Document1.00
    9. Implementation details1.00
    10. https://github.com/github/spec-kit1.00
    11. aws1.00
    12. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.95
    13. buitd-0.96

  • 9:43 #21 done25 line(s)

    shot 21·sharpness 1268.1

    1. SPEC-DRIVEN DEVELOPMENT0.98
    2. AIE WORLD'S FAIR· SF0.96
    3. spec.md0.99
    4. Features1.00
    5. New Session X0.92
    6. Spec-Driven Development1.00
    7. Let's build1.00
    8. Plan, search, or build anything0.99
    9. Vibe1.00
    10. Spec1.00
    11. Chat first, then build.0.98
    12. Plan first, then build.0.98
    13. Explore ideas and0.99
    14. Create requirements1.00
    15. iterate as you1.00
    16. and design before1.00
    17. discover needs.1.00
    18. coding starts.1.00
    19. Great for:1.00
    20. • Thinking through features in-depth0.98
    21. • Projects needing upfront planning0.97
    22. • Building features in a structured way0.98
    23. aws1.00
    24. © 2026, Amazon Web Services, Inc. or its affliates. Al rights reserved.0.94
    25. build1.00

  • 10:06 #22 done30 line(s)

    shot 22·sharpness 1903.5

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR· SF0.96
    3. spec.md1.00
    4. Ask it to begin!0.97
    5. New Session X0.95
    6. “Build a Movie MCP0.97
    7. *0+0.63
    8. server to keep track0.99
    9. Let's build1.00
    10. Plan, search, or build anything1.00
    11. of movies I’ve0.97
    12. Vibe1.00
    13. 目0.92
    14. Spec1.00
    15. watched"0.99
    16. Chat first, then build.0.99
    17. Plan first, then build.1.00
    18. Explore ideas and0.99
    19. Create requirements0.99
    20. iterate as you1.00
    21. and design before1.00
    22. discover needs.1.00
    23. coding starts.1.00
    24. Great for:1.00
    25. • Thinking through features in-depth0.98
    26. • Projects needing upfront planning0.97
    27. • Building features in a structured way0.98
    28. aws1.00
    29. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.94
    30. build1.00

  • 10:41 #23 done29 line(s)

    shot 23·sharpness 1914.9

    1. SPEC-DRIVEN DEVELOPMENT1.00
    2. AIE WORLD'S FAIR· SF0.97
    3. spec.md1.00
    4. Ask it to begin!0.97
    5. New Session ×0.95
    6. “Build a Movie MCP0.98
    7. server to keep track1.00
    8. Let's build1.00
    9. Plan, search, or build anything1.00
    10. of movies I’ve0.98
    11. Vibe1.00
    12. 目0.85
    13. Spec1.00
    14. watched"1.00
    15. Chat first, then build.1.00
    16. Plan first, then build.1.00
    17. Explore ideas and0.99
    18. Create requirements0.98
    19. iterate as you1.00
    20. and design before0.98
    21. discover needs.1.00
    22. coding starts.1.00
    23. Great for:1.00
    24. • Thinking through features in-depth0.98
    25. • Projects needing upfront planning0.98
    26. • Building features in a structured way0.98
    27. aws1.00
    28. © 2026, Amazon Web Services, Inc. or its affliates. All rights reserved.0.95
    29. buitd-0.95

Transcript

223 cues· 3,199 words· 17,093 chars

  1. 0:00 Hey everyone, my name is Eric Hanchett and today I want to tell you guys all about spec driven development and how you might use it in your workflows today.
  2. 0:09 So there's a couple of things we want to talk about.
  3. 0:11 First, what is spec driven development?
  4. 0:14 And then how can it make you a better and faster coder?
  5. 0:18 So we just don't want you to code faster, but we want you to actually create higher quality
  6. 0:24 code from it.
  7. 0:25 And I think really spec driven development helps you with this.
  8. 0:28 And I'm going to explain why and how.
  9. 0:31 It's a structured specifications are created before any code is written.
  10. 0:35 That's the definition of really the specs or the requirements of this spec driven development.
  11. 0:41 And it goes to the heart of what it is.
  12. 0:43 So what we're doing is we are writing these markdown files, we're writing the specifications and the design document before any of the code is written.
  13. 0:54 And this actually works really, really well with large language models and our coding assistants that we use.
  14. 0:59 And I'm going to show you exactly how that works.
  15. 1:02 Now, a question I sometimes get is why?
  16. 1:05 Like, why should we use this spec-driven development workflow?
  17. 1:09 And then how can we do it?
  18. 1:11 So to answer that why question, I kind of like to think about our coding assistants, our large language models that we're using every day as sort of like AI interns.
  19. 1:23 You need to really prompt them.
  20. 1:24 You really need to push them the right way.
  21. 1:26 No pun intended with the prompting.
  22. 1:28 So you really need to...
  23. 1:30 guide them, because if you give them just a little bit of leeway, they will go off the rails.
  24. 1:37 And really, the spectrum of development helps guide them in the right direction.
  25. 1:41 I remember when I was an intern and one of my first jobs, we had a VP that would walk around and he would just come up with random ideas off the top of his head.
  26. 1:50 And when he told me it, I would drop everything and work on it.
  27. 1:54 And then later, my boss would be like, Hey, Eric, why did you drop everything?
  28. 1:58 Well, the VP said something.
  29. 2:00 And then I learned about, well, you got to take his information that he gives you, write it down, put it in your schedule, talk to my manager about it.
  30. 2:09 So I was a little too eager.
  31. 2:10 And this is what AI interns or basically these large language models do nowadays.
  32. 2:14 And we got to be careful about it.
  33. 2:18 I didn't really give you too much of an introduction, so I'll give it to you now.
  34. 2:22 My name is Eric Hanchett.
  35. 2:23 I'm a senior developer advocate at AWS.
  36. 2:27 I have over 15 plus years of software development experience.
  37. 2:31 And if you want to connect with me, you can check out LinkedIn.
  38. 2:34 That's probably the best place to go.
  39. 2:38 Just look for Eric Hanchett and yeah, talk to me, follow me.
  40. 2:41 I'd love to talk to you more about it.
  41. 2:44 Another question that people often ask me about spec-driven development is, can't the latest frontier models just do everything for us already?
  42. 2:53 Why do we need this?
  43. 2:55 And while I do say that the models are getting better and better every year and every release, sometimes incrementally, sometimes by leaps and bounds, it's still not perfect.
  44. 3:04 And giving the large language model these models more context is actually really important.
  45. 3:10 because it does help guide it in the right direction.
  46. 3:13 And with our software always changing and with the requirements always changing and with new paradigms and shifts, you always need to kind of guide it where it needs to go.
  47. 3:23 Some large language models, some harnesses are starting to think more about this and adding in a little bit more of a
  48. 3:30 thinking or planning mode before it jumps into when it writes code.
  49. 3:34 But there's nothing better than actually having those documents created and having you be in the middle before it jumps into that next part with it creating code.
  50. 3:46 So let's keep a few things in mind before we get too far.

Open at this second