094459/sdd-workshop — Summary

A self-guided, hands-on workshop teaching spec-driven development using the Kiro IDE as the primary tool. The workshop is structured as five sequential labs covering the SDD lifecycle: requirements, design, and tasks — for both greenfield (new project) and brownfield (existing codebase) scenarios. It does not ship prompts, CLI tools, or runnable scripts; its entire value is in the workshop Markdown narrative and the accompanying Kiro walkthrough instructions.

Target audience is AWS-adjacent developers attending a facilitated session or working through it self-service. The repo is a documentation/tutorial repository, not a methodology framework with installable components. It ships zero slash commands, zero skills, zero hooks, and zero MCP servers.

As a teaching artifact for Kiro's SDD implementation, it sits closest to the Kiro seed in archetype (Archetype 5 — closed IDE with proprietary primitives), but functions only as a companion tutorial rather than an independent framework. It differs from spec-kit (Archetype 2) and openspec (Archetype 2) in having no installable components whatsoever, and from spec-driver (Archetype 1) in not shipping any skills or CLI.

094459/sdd-workshop — Overview

Origin

Created by an AWS Developer Advocate (GitHub handle 094459) as a companion workshop to the Kiro IDE launch. The repository description is "A hands on, self guided tutorial to help you get started with specification driven development." It was published in 2025 alongside Kiro's public availability.

Philosophy

The workshop teaches SDD as a disciplined practice centered on three documents: requirements, design, and tasks. It treats these documents as the "spec" and defines a spec lifecycle (create, iterate, update). The framing is pedagogical: the content explains why each phase matters before asking students to try it.

Manifesto-style quotes

From workshop/02-getting-started.md:

"Spec driven development (SDD) is a systematic approach to software feature development that emphasizes thorough planning, clear documentation, and structured implementation. This methodology transforms rough feature ideas into well-defined, implementable solutions through a three-phase process that ensures quality, maintainability, and successful delivery."

On steering documents:

"Providing the right context is key to getting the best out of AI coding assistants, and steering documents help provide context... Instead of explaining your conventions in every chat, steering files ensure your AI coding assistant consistently follows your established patterns, libraries, and standards."

On context hygiene:

"Edit your context files ruthlessly so that they are as small as you can make them."

Structure

Five workshop modules:

1. 01-intro.md — Historical evolution from raw AI to SDD
2. 02-getting-started.md — SDD concepts: spec structure, steering docs, inclusion modes
3. 03-greenfield.md — Building new applications end-to-end with Kiro
4. 04-brownfield.md — Applying SDD to existing codebases
5. 05-tools-and-resources.md — Kiro deep-dive and additional resources

Target audience

Workshop attendees (in-person or self-service) who want a structured introduction to Kiro's SDD workflow. The author is AWS DevRel; the workshop references an AWS survey link.

094459/sdd-workshop — Architecture

Distribution

• Type: Methodology documentation / tutorial repository
• Install: No installation required. Clone or browse on GitHub.
• Install complexity: clone-and-configure (clone + open Kiro IDE)

Directory tree

sdd-workshop/
├── README.md            ← Entry point + lab navigation
├── images/              ← Workshop screenshots (header, kiro UI, lifecycle diagrams)
├── updates/
│   └── changelog.md
└── workshop/
    ├── 01-intro.md          ← History and motivation
    ├── 02-getting-started.md ← SDD concepts + steering docs
    ├── 03-greenfield.md     ← Hands-on lab: new application
    ├── 04-brownfield.md     ← Hands-on lab: existing codebase
    └── 05-tools-and-resources.md ← Kiro features + resources

Dependencies

• Required runtime: None (documentation only)
• Required tooling: Kiro IDE (proprietary, downloadable from kiro.dev), Python 3.10+, uv (for the lab exercises), git

Target AI tools

• Primary: Kiro IDE (the only tool used in the workshop)
• Other: None — the workshop does not reference Claude Code, Cursor, or any other agent

Config files

None — the repo ships no config files for any AI framework. The .kiro/steering/ directory is created by the student during the lab exercises, not by the repo.

Notes

The workshop is a Kiro-specific tutorial. Students install Kiro, follow the lab instructions, and produce the standard Kiro SDD artifacts (requirements.md, design.md, tasks.md) within the Kiro IDE UI. The repository itself contains only the tutorial narrative.

094459/sdd-workshop — Components

Commands

None. The repo ships zero slash commands.

Skills

None.

Subagents

None.

Hooks

None.

MCP Servers

None.

Scripts

None.

Templates

None shipped as reusable templates. The workshop Markdown files describe what artifacts students will create during the hands-on labs (requirements.md, design.md, tasks.md), but the repo does not provide those as blank templates.

Workshop Modules (the only shipped primitives)

Summary

The framework's entire component inventory is five Markdown tutorial files and one image directory. This is a documentation-only repository with no executable, installable, or programmatic primitives.

094459/sdd-workshop — Uniqueness

differs_from_seeds

This repo is closest to the kiro seed — it is literally a tutorial for Kiro's native SDD implementation. The architectural delta is that it adds zero framework machinery: no skills, no commands, no hooks, no CLI, and no templates. Where kiro itself is the tool (Archetype 5 — closed IDE with proprietary primitives), 094459/sdd-workshop is a teaching companion that walks students through using that tool. It differs from spec-kit (Archetype 2 — mirror commands+skills) by having no installable components, and from spec-driver (Archetype 1 — skills-only behavioral framework) by being purely documentation. It is arguably the most minimal entry in the entire corpus: 5 Markdown files and a set of images, shipping nothing a machine can execute.

Positioning

Occupies a unique position as a certified tutorial rather than an independent methodology. AWS DevRel published it to accelerate Kiro adoption. It teaches the same requirements→design→tasks three-document pattern seen across many seeds (agent-os, kiro, spec-kit, openspec) but delegates all implementation to Kiro's proprietary IDE.

For teams evaluating Kiro, this is the most direct on-ramp. For teams not using Kiro, the workshop provides zero value (everything requires the IDE).

Observable failure modes

1. 100% Kiro dependency: The entire workshop fails without Kiro access. No fallback methodology exists.
2. No standalone prompts: Students cannot apply the methodology with Claude Code, Cursor, or any non-Kiro tool — the repo provides no CLAUDE.md templates or slash commands.
3. Stale content risk: Workshop was created at Kiro launch; as Kiro's UI evolves, screenshots and step-by-step instructions may diverge from actual Kiro behavior.
4. No validation gates: All phase reviews are purely manual with no automated checks.
5. Low reusability: Because the repo is pedagogical prose rather than reusable components, practitioners cannot build on top of it programmatically.