@JK_Kross (in answer to your question on a different thread).
At the moment Workspace presumes a package, but you can still temporarily add a dummy Package.swift to any repository in order to describe its structure. The package does not need to build successfully for Workspace to scan it for documentation. Workspace already contains the scanned interfaces of the standard and core libraries for the sake of inheritance, so you could look at that scanning code to figure out what paths the manifest needs to point at, and what files need to be generated first, such as with GYB. If you do scan the Swift project documentation that way, make sure not to publish the result anywhere without sorting out the whatever licensing might be involved, since it wasn’t you that wrote those documentation comments.