Merge pull request #54149 from ChrisHowd/GH-Spec-Kit-Greenfield-adding-videos

Court72 · web-flow · commit f26a96bdd264 · 2026-04-08T13:31:56.000-06:00
GitHub Spec Kit Greenfield - Adding Video Options
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/1-introduction.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/1-introduction.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 3
+  zone_pivot_groups: video-or-text
+durationInMinutes: 2
 content: |
-  [!include[](includes/1-introduction.md)]
+  [!include[](includes/1-introduction.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/10-knowledge-check.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/10-knowledge-check.yml
@@ -8,7 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 10
+durationInMinutes: 7
 quiz:
   title: "Check your knowledge"
   questions:
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/11-summary.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/11-summary.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 2
+  zone_pivot_groups: video-or-text
+durationInMinutes: 1
 content: |
   [!include[](includes/11-summary.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/2-what-spec-driven-development.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/2-what-spec-driven-development.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 7
+  zone_pivot_groups: video-or-text
+durationInMinutes: 3
 content: |
   [!include[](includes/2-what-spec-driven-development.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/3-examine-spec-driven-development-principles-processes.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/3-examine-spec-driven-development-principles-processes.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 6
+  zone_pivot_groups: video-or-text
+durationInMinutes: 3
 content: |
   [!include[](includes/3-examine-spec-driven-development-principles-processes.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/4-compare-spec-driven-development-other-methodologies.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/4-compare-spec-driven-development-other-methodologies.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 10
+  zone_pivot_groups: video-or-text
+durationInMinutes: 3
 content: |
   [!include[](includes/4-compare-spec-driven-development-other-methodologies.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/5-examine-spec-driven-development-workflow-phases.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/5-examine-spec-driven-development-workflow-phases.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 12
+  zone_pivot_groups: video-or-text
+durationInMinutes: 3
 content: |
   [!include[](includes/5-examine-spec-driven-development-workflow-phases.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/6-introduction-github-spec-kit.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/6-introduction-github-spec-kit.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 9
+  zone_pivot_groups: video-or-text
+durationInMinutes: 3
 content: |
   [!include[](includes/6-introduction-github-spec-kit.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/7-examine-github-spec-kit-environment-installation.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/7-examine-github-spec-kit-environment-installation.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 9
+  zone_pivot_groups: video-or-text
+durationInMinutes: 3
 content: |
   [!include[](includes/7-examine-github-spec-kit-environment-installation.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/8-examine-github-spec-kit-commands-results.yml b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/8-examine-github-spec-kit-commands-results.yml
@@ -8,6 +8,7 @@ metadata:
   author: chrishowd
   ms.author: cahowd
   ms.topic: unit
-durationInMinutes: 13
+  zone_pivot_groups: video-or-text
+durationInMinutes: 4
 content: |
   [!include[](includes/8-examine-github-spec-kit-commands-results.md)]
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/1-introduction.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/1-introduction.md
@@ -1,3 +1,11 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=2afe5e39-7c2d-462c-916f-3d6422cae20e]
+
+::: zone-end
+
+::: zone pivot="text"
+
 Spec-driven development (SDD) is a structured approach to software development that treats specifications as executable sources of truth rather than throwaway planning documents. When you use SDD with AI coding assistants like GitHub Copilot, the specification guides code generation directly, ensuring the implementation matches your intended behavior from the start.
 
 Imagine you're a software developer working for a consulting firm that uses AI-assisted development tools. You need to build a new greenfield application for a client. Rather than iteratively prompting the AI with fragmentary instructions and discovering requirements as you go, you want a more structured approach. With spec-driven development and GitHub Spec Kit, you can transform project documentation into specification files, technical plans, and implementation tasks that GitHub Copilot uses to generate aligned, production-ready code.
@@ -18,5 +26,10 @@ After completing this module, you'll be able to:
 - Use GitHub Spec Kit commands to create the constitution.md, spec.md, plan.md, and tasks.md files.
 - Implement a greenfield application from start to finish using GitHub Spec Kit's AI-assisted workflows.
 
+::: zone-end
+
+> [!NOTE]
+> We recognize that different people like to learn in different ways. You can choose to complete this module in video-based format or you can read the content as text and images. The text contains greater detail than the videos, so in some cases you might want to refer to it as supplemental material to the video presentation.
+>
 > [!IMPORTANT]
 > To complete this GitHub Copilot training, you must have an active subscription for GitHub Copilot in your personal GitHub account (includes the GitHub Copilot Free plan), or you must be assigned to a subscription managed by an organization or enterprise. Module activities might include GitHub Copilot suggestions that match public code. If you're a member of an organization on GitHub Enterprise Cloud who is assigned to a GitHub Copilot subscription through your organization, the setting for suggestions matching public code might be inherited from your organization or enterprise. If your account blocks suggestions that match public code, module activities might not work as expected.
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/11-summary.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/11-summary.md
@@ -1,5 +1,18 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=e38a4541-c57b-4209-a469-522f011757f4]
+
+::: zone-end
+
+::: zone pivot="text"
+
 In this module, you learned how to implement a spec-driven development (SDD) methodology using GitHub Spec Kit. You used the SDD workflow to develop a greenfield application by defining specifications upfront rather than iteratively prompting the AI with fragmentary instructions.
 
 The main takeaway from this module is the ability to implement a spec-driven development process, which allows you to use AI tools like GitHub Copilot to generate code based on structured specifications. This approach enables you to focus on defining clear requirements and technical plans before implementation begins, ensuring that generated code aligns with intended behaviors from the start. You also learned how to compare SDD with other methodologies, set up your environment for GitHub Spec Kit, and use commands like `/speckit.constitution`, `/speckit.specify`, `/speckit.plan`, and `/speckit.tasks` to generate the artifacts that guide implementation. These skills are essential for effectively using AI-driven tools in a structured, enterprise-ready workflow.
 
 You can apply the knowledge gained in this module to build greenfield applications with confidence, maintain consistency across AI-assisted development sessions, and reduce the gap between specifications and implementation. By practicing spec-driven development with GitHub Spec Kit, you can enhance your productivity and deliver higher-quality software that meets stakeholder requirements.
+
+::: zone-end
+
+> [!NOTE]
+> See the **Text and images** tab for more details!
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/2-what-spec-driven-development.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/2-what-spec-driven-development.md
@@ -1,3 +1,11 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=fbce6121-62bd-4e19-aeda-a6ff8aab9196]
+
+::: zone-end
+
+::: zone pivot="text"
+
 In traditional software development, we often treat code as the ultimate source of truth. Specifications serve code - they're the scaffolding we build and then discard once the "real work" of coding begins. We write Product Requirements Documents (PRDs) to guide development, create design docs to inform implementation, and draw diagrams to visualize architecture. But these documents are always subordinate to the code itself. As code moves forward, specs rarely keep pace.
 
 With the rise of powerful AI coding assistants like GitHub Copilot, this code-first approach evolved into what we now call "vibe coding." Unfortunately, the vibe coding approach often involves submitting a high-level prompt that returns a chunk of code that "looks right" but might miss the intent or have errors. It can be fast, but sometimes it's misaligned. Each chat session operates in isolation, lacking awareness of previous decisions or overall project requirements.
@@ -47,3 +55,8 @@ For enterprise teams especially, SDD addresses persistent pain points: miscommun
 ## Summary
 
 Spec-driven development represents a fundamental shift in how we build software. By making specifications the primary artifact that drives code generation, SDD eliminates the gap between intent and implementation. This approach uses AI capabilities to automate the mechanical translation from precise specs to working systems, enabling teams to maintain velocity amid complexity and change. As software development continues to evolve, embracing spec-driven development is crucial for teams aiming to deliver high-quality products efficiently.
+
+::: zone-end
+
+> [!NOTE]
+> See the **Text and images** tab for more details!
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/3-examine-spec-driven-development-principles-processes.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/3-examine-spec-driven-development-principles-processes.md
@@ -1,3 +1,11 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=1ba83ea3-0604-481b-ade2-dbd3106032d0]
+
+::: zone-end
+
+::: zone pivot="text"
+
 The spec-driven development (SDD) methodology provides a phased approach to software development that emphasizes clarity, structure, and adaptability. By breaking down the development process into four distinct phases—Specify, Plan, Tasks, and Implement—SDD ensures that each step is well-defined and builds upon the previous one. This structured workflow not only enhances communication among stakeholders but also allows for continuous refinement and adaptation of the software being developed.
 
 ## Workflow phases in spec-driven development
@@ -64,3 +72,8 @@ The key insight is that humans provide direction and verification, while AI prov
 ## Summary
 
 Spec-driven development is a structured approach that transforms ideas into working software through a four-phase workflow: Specify, Plan, Tasks, and Implement. Each phase builds on the previous one, with clear outputs that guide the next steps. The living nature of SDD artifacts allows for continuous adaptation and improvement, aligning well with Agile principles. Additionally, SDD pairs effectively with AI collaboration, where developers steer the process while AI generates detailed outputs, enabling rapid iteration and high-quality software development.
+
+::: zone-end
+
+> [!NOTE]
+> See the **Text and images** tab for more details!
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/4-compare-spec-driven-development-other-methodologies.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/4-compare-spec-driven-development-other-methodologies.md
@@ -1,3 +1,11 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=013e3314-ad82-4e87-a65f-b4ef5bea6b92]
+
+::: zone-end
+
+::: zone pivot="text"
+
 Understanding how spec-driven development (SDD) relates to other software development methodologies helps you see where it fits in your existing practices. Rather than replacing what you already know, SDD can complement and enhance established approaches, especially when you're using AI-assisted development tools.
 
 ## Methodology comparison overview
@@ -112,3 +120,8 @@ The key is recognizing SDD as a tool in your toolkit, not a silver bullet for ev
 ## Summary
 
 Spec-driven development offers a structured, adaptable approach that complements and enhances existing methodologies. When you focus on clear specifications, living artifacts, and AI collaboration, SDD provides a reliable framework for building high-quality software in complex scenarios. Understanding when and how to apply SDD alongside other methodologies allows you to use its strengths effectively while maintaining flexibility in your development practices.
+
+::: zone-end
+
+> [!NOTE]
+> See the **Text and images** tab for more details!
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/5-examine-spec-driven-development-workflow-phases.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/5-examine-spec-driven-development-workflow-phases.md
@@ -1,3 +1,11 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=3b505e76-1885-4287-945d-fccda6499882]
+
+::: zone-end
+
+::: zone pivot="text"
+
 Each phase of the Spec-Driven Development (SDD) workflow plays a crucial role in transforming ideas into working software. Developers who understand the purpose, content, and output of each phase can apply SDD effectively to their own projects.
 
 > [!NOTE]
@@ -157,3 +165,8 @@ Writing all these artifacts by hand might sound laborious, but AI tools like Git
 ## Summary
 
 The four phases of spec-driven development - Specify, Plan, Tasks, and Implement - provide a structured workflow that transforms ideas into working software. Each phase produces artifacts that guide the next step, ensuring alignment between requirements and implementation. The living nature of these artifacts allows for continuous adaptation, while the systematic checkpoints maintain quality and coherence throughout the process.
+
+::: zone-end
+
+> [!NOTE]
+> See the **Text and images** tab for more details!
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/6-introduction-github-spec-kit.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/6-introduction-github-spec-kit.md
@@ -1,3 +1,11 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=058fcbad-7d91-4991-80bc-1b8d102e97c1]
+
+::: zone-end
+
+::: zone pivot="text"
+
 GitHub Spec Kit is an open-source toolkit developed by GitHub to facilitate spec-driven development. It's designed to integrate with AI coding assistants like GitHub Copilot and orchestrate the SDD workflow through structured commands, templates, and persistent artifacts.
 
 Think of GitHub Spec Kit as a copilot for your copilot - it guides the AI through a structured process, ensuring consistent, high-quality output at each phase of development.
@@ -119,3 +127,8 @@ GitHub Spec Kit empowers you to accomplish in minutes what might otherwise take
 ## Summary
 
 GitHub Spec Kit is an open-source toolkit that operationalizes spec-driven development by providing a structured workflow, persistent artifacts, and AI integration. It guides you through the SDD phases of Specify, Plan, Tasks, and Implement using commands and templates, enabling efficient, consistent, and high-quality software development. With multi-agent support and enterprise readiness, GitHub Spec Kit empowers teams to apply AI effectively while maintaining control over project requirements and design principles.
+
+::: zone-end
+
+> [!NOTE]
+> See the **Text and images** tab for more details!
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/7-examine-github-spec-kit-environment-installation.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/7-examine-github-spec-kit-environment-installation.md
@@ -1,3 +1,11 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=1487ed15-c87a-4616-b5f2-2792a846e2cb]
+
+::: zone-end
+
+::: zone pivot="text"
+
 Before you can use GitHub Spec Kit to practice spec-driven development, you need to set up your environment. This unit covers the prerequisites, installation process, and configuration steps to get GitHub Spec Kit running in your development environment.
 
 ## Prerequisites and system requirements
@@ -198,3 +206,8 @@ For issues beyond these common problems, consult the GitHub Spec Kit README and
 ## Summary
 
 GitHub Spec Kit supports various development environments and AI coding assistants. Core requirements include Python 3.11+, Git, and the `uv` tool. You can install the `specify` CLI globally or use it one-time via `uvx`. Visual Studio Code with GitHub Copilot is a common setup, but other AI tools are supported as well. Verifying your installation with `specify check` helps ensure everything is configured correctly.
+
+::: zone-end
+
+> [!NOTE]
+> See the **Text and images** tab for more details!
diff --git a/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/8-examine-github-spec-kit-commands-results.md b/learn-pr/wwl-azure/spec-driven-development-github-spec-kit-greenfield-intro/includes/8-examine-github-spec-kit-commands-results.md
@@ -1,3 +1,11 @@
+::: zone pivot="video"
+
+>[!VIDEO https://learn-video.azurefd.net/vod/player?id=dbecd5b0-a226-402d-8ad6-3e384a455fe1]
+
+::: zone-end
+
+::: zone pivot="text"
+
 With GitHub Spec Kit installed, you're ready to use its commands to practice spec-driven development. This unit walks through each command in the workflow, explaining what it does, what output it produces, and how to work with the results. Understanding this process prepares you for the hands-on lab exercise.
 
 ## Command overview
@@ -281,3 +289,8 @@ There are several best practices to follow when using GitHub Spec Kit:
 ## Summary
 
 GitHub Spec Kit provides a structured set of commands that operationalize spec-driven development. By following the workflow from project initialization through constitution, specification, planning, task generation, and implementation, you can systematically transform ideas into working software. Each command produces artifacts that guide the next steps, ensuring alignment and quality throughout the process. Optional enhancement commands help clarify requirements and verify consistency, while best practices ensure effective use of AI assistance. With this understanding, you're ready to apply GitHub Spec Kit in your development projects.
+
+::: zone-end
+
+> [!NOTE]
+> See the **Text and images** tab for more details!
