Workspace Structure Visualisation
Use Case
Changed on:
31 Mar 2026
Problem
Potential Problems:- No quick way to orient in a complex workspace: After multiple sessions of scaffolding, deploying, and analysing, the workspace accumulates many files and directories that are difficult to navigate without a structured overview.
- Wasted time reconstructing context at the start of a session: Returning to a workspace after time away often means spending the first several minutes figuring out what exists and where things stand before any productive work can begin.
- Uncertainty about what has actually been generated: After running multiple tools across a session, it is not always obvious which reports, analyses, and source files have been produced and are available to reference or build on.
- Difficulty communicating workspace scope to new team members: Onboarding someone to a complex workspace is harder without a single, annotated view that shows what has been built, where it lives, and what state each feature is in.
- No visibility into version and scale of deployed assets: Knowing that a module exists is one thing; knowing it contains 97 rules at version 1.4.0 versus 3 rules at version 1.0.0 is the kind of detail that matters when planning changes or estimating effort.
Example
You want to see what's in the workspace — features, workflows, source code, reports — with counts and annotations.
