This year Kiro introduced AWS’ take on Spec-Driven Development to world. But what is SDD? Does it work? And should you care?In this interactive session we’ll investigate through experimentation. We’ll collaborate as a group on our Kiro prompts as we attempt to build a miniature event-driven, serverless image processing system on AWS... without writing any code ourselves.Will this work? I genuinely don’t know. Let’s find out together!

Similar to Lets Build a Serverless Function with Kiro

More from Chris Bingham

Recently uploaded

Lets Build a Serverless Function with Kiro

• 1.
  © Fujitsu 20251© Fujitsu 20251Let's Build aServerlessFunctionwith KiroChris BinghamAWS Ambassador & CTO SwitzerlandAWS User Group Zürich 24.11.25
• 2.
  © Fujitsu 20252WARNING:Interactive Content Ahead!This is an interactive, collaborative session.We’ll attempt to build and deploy aserverless solution together using Kiro.Which is very much an experiment!
• 3.
  © Fujitsu 20253ImprotantNote:Everything we do today will be with:●Claude Sonnet 4.5●Spec Mode●Autopilot
• 4.
  © Fujitsu 20254SolutionStarting PointAn S3 bucket, which image files get uploaded to.How could we process those images?Ideas time!+ =
• 5.
  © Fujitsu 20256PromptEngineering
• 6.
  © Fujitsu 20257TopTips for Effective Prompting●Based on my experience so far…●Best practices could change with the next model version●Top Tips:1. Avoid ambiguity – be clear & specific2. Include both context and constraints3. Empasise the MUST and MUST NOT with block caps4. Format with Markdown5. Draft your prompt outside the chat boxPrompt writing time!
• 7.
  © Fujitsu 20259SteeringDocs
• 8.
  © Fujitsu 202510Whatare Steering Docs?●Provide cross-session solution consistency●Specific to each solution●Formatted with Markdown●Yep, that’s a theme!●Define:●Your vision for the solution●Purposes●Goals●Audience●Constraints●General guardrails for the decisions and actions the AI will take
• 9.
  © Fujitsu 202511SteeringDoc Structure●Could be organised in any way●Defaults to three documents:●product.md●Describes the product we’re trying to build with Kiro●Purpose, audience, business constraints●structure.md●Describes the code & repository structure and conventions●Design principles for the solution●tech.md●Describes specific technical decisions the solution must adhere to●E.g. tooling to use, AWS services to use/avoid, templates for specificbuild commands, etc.
• 10.
  © Fujitsu 202512RequirementsDoc
• 11.
  © Fujitsu 202513What’sthe Requirements Doc?●Describe the intended outcomes●In business terms, -ish●Typically contains:●General description of the solution●Glossary of key terms●Another mechanism to add consistency across sessions●Numbered requirements●User story●Testable acceptance criteria
• 12.
  © Fujitsu 202514Let’slook at ourrequirements doc!
• 13.
  © Fujitsu 202515DesignDoc
• 14.
  © Fujitsu 202516What’sthe Design Doc?●Contents is highly solution dependant… duh!●Typically describes●Listing of key design decisions●High-level architecture of the solution●Description of each component in the architecture●Description of how errors will be handled by the solution●Strategy for testing the solution
• 15.
  © Fujitsu 202517Let’slook at ourdesign doc!
• 16.
  © Fujitsu 202518TasksList
• 17.
  © Fujitsu 202519What’sthe Task List●Does exactly what it says on the tin!●Breaks down implementation of the design●Number tasks and sub tasks●Each referencing the requirements it’s linked to●Each with a “Start Task” option●Each task is executed in a separate session (context window)●Actively manages the scope of information fed to the model●Which improves the quality of results●By focusing the model on narrow, clearly defined goals
• 18.
  © Fujitsu 202520Let’slook at our task list!
• 19.
  © Fujitsu 202521Deploymenttime?
• 20.
  © Fujitsu 202522© Fujitsu 202522Q&ASlides here >
• 21.
  © Fujitsu 202523© Fujitsu 202523Thank you