gsd-list-workspaces

Workspace status checking works by scanning a designated directory for workspace folders containing WORKSPACE.md manifests, then executing a predefined reference workflow to extract details like repository count and strategy into a summary table.

Automated workspace scanning requires Bash and Read tool access to execute the predefined workflow and generate a summary table with workspace name, path, repository count, strategy, and GSD project status.

Yes, you need Bash and Read tool access to scan GSD workspaces, as the status checking process executes a predefined reference workflow that reads WORKSPACE.md manifests from the ~/gsd-workspaces/ directory.

The GSD workspace summary table includes the workspace name, file path, repository count, project strategy, and current GSD project status, all extracted automatically from the WORKSPACE.md manifests found during the directory scan.

Your workspace status check fails to return project details if the scanned directories do not contain the required WORKSPACE.md manifests, which the predefined workflow reads to extract the repository count and strategy.