design/ mention that tools can help automate creation

Change-Id: Ia02f7b637c5da39d111ce901696339ad5ad2fa12
Trust: Michael Matloob <>
Run-TryBot: Michael Matloob <>
Reviewed-by: Michael Matloob <>
diff --git a/design/ b/design/
index f64819c..397ef2f 100644
--- a/design/
+++ b/design/
@@ -380,7 +380,9 @@
 Our goal is that when there are several tightly coupled modules in the same
 repository, users would choose to create `` files defining the workspace
 using the modules in those repositories instead of adding `replaces` in the
-`go.mod` files. These `` files should not be checked into the
+`go.mod` files. Perhaps the creation of the file can be automated by an external
+tool that scans for all the `go.mod` files recursively contained in a directory.
+These `` files should not be checked into the
 repositories so that they don't override the workspaces users explicitly define.
 Checking in `` files could also lead to CI/CD systems not testing the
 actual set of version requirements on a module and that version requirements