diff --git a/docs/3-AI-Engineering/3.3.1-agentic-best-practices.md b/docs/3-AI-Engineering/3.3.1-agentic-best-practices.md
index 341ec260..c53aa290 100644
--- a/docs/3-AI-Engineering/3.3.1-agentic-best-practices.md
+++ b/docs/3-AI-Engineering/3.3.1-agentic-best-practices.md
@@ -26,6 +26,14 @@ For an alternative recording with additional perspectives, see [this version](ht
 
 The four-stage SDD workflow below applies these principles to real-world development. These practices work for both greenfield and brownfield projects, though brownfield implementations focus the planning phase on the specific task at hand rather than full system design.
 
+### Liatrio's `spec-driven-workflow` Tool
+
+[Repo](https://github.com/liatrio-labs/spec-driven-workflow)  
+
+This tool will provide the prompts used for SDD (explained in greater detail below). This provides a bit more automation and is nicer to work with than copy pasting the prompts from this page into the prompt window. For example, to generate a specification you would type `/sdd` into the prompt window then select `SDD-1-generate-spec`.
+
+![Slash Command Example](img3/slash-command-example-claude.png ":size=600 :alt=Slash Command Example")
+
 ### 1. Generate Specification (SDD Stage 1)
 
 The first stage of Spec-Driven Development transforms a high-level idea into a comprehensive, developer-ready specification. This specification becomes the source of truth for your implementation, defining goals, requirements, constraints, and success criteria before any code is written.
diff --git a/docs/3-AI-Engineering/img3/slash-command-example-claude.png b/docs/3-AI-Engineering/img3/slash-command-example-claude.png
new file mode 100644
index 00000000..5bcc4d90
Binary files /dev/null and b/docs/3-AI-Engineering/img3/slash-command-example-claude.png differ