Refactor workspace command: extract project types into ProjectCliCommand, add ConfigCliCommand stub

- Update README example to use workspace explain
- Clarify component parameter wording in CopilotInstructionsManager
- Extract project type documentation from WorkspaceCliCommand into new ProjectCliCommand
- Add ConfigCliCommand stub for future config validation feature
- Minor whitespace cleanup in ComponentParameterListCliCommand

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: TomProkop

README.md

@@ -113,9 +113,9 @@ dotnet restore
 dotnet build
 ```
 
-**Run the CLI directly (for example, to test the data transform server):**
+**Run the CLI directly:**
 ```sh
-dotnet run --project src/TALXIS.CLI -- data transform server start
+dotnet run --project src/TALXIS.CLI -- workspace explain
 ```
 
 ---

src/TALXIS.CLI.MCP/CopilotInstructionsManager.cs

@@ -47,7 +47,7 @@ public class CopilotInstructionsManager
    - Avoid speculation about functionality not confirmed by txc-mcp
 
 6. **Default Values to use unless specified**
-   - You must always pass `SolutionRootPath=Declarations` when calling the tool for creating components
+   - You must always pass `SolutionRootPath=Declarations` component parameter when calling the tool for creating components
 
 ## Project Structure and Naming Conventions
 

src/TALXIS.CLI.Workspace/ComponentParameterListCliCommand.cs

@@ -26,13 +26,13 @@ public int Run()
             return 0;
         }
         Console.WriteLine($"Parameters for template '{ShortName}':");
-        
+
         // Always show the mandatory output parameter first
         Console.WriteLine("--output (Project folder path)  (text)  <required>");
         Console.WriteLine("    Specifies the target project folder path where the component will be created.");
         Console.WriteLine("    Required for both creating new projects (solution, plugin, PCF, etc.) and adding components to existing projects.");
         Console.WriteLine("    Format: \"src\\Solutions.DataModel\"");
-        
+
         foreach (var p in parameters)
         {
             Console.Write($"--{p.Name}");
@@ -42,7 +42,7 @@ public int Run()
             if (!string.IsNullOrEmpty(p.DefaultValue?.ToString()))
                 Console.Write($"  [default: {p.DefaultValue}]");
             // Check if parameter is required
-            if (p.Precedence.IsRequired || 
+            if (p.Precedence.IsRequired ||
                 p.Precedence.PrecedenceDefinition == Microsoft.TemplateEngine.Abstractions.PrecedenceDefinition.Required)
                 Console.Write("  <required>");
             if (p.Choices != null && p.Choices.Count > 0)

src/TALXIS.CLI.Workspace/ConfigCliCommand.cs

@@ -0,0 +1,27 @@
+using DotMake.CommandLine;
+
+namespace TALXIS.CLI.Workspace;
+
+[CliCommand(
+    Description = "Configure and troubleshoot this tool"
+)]
+public class ConfigCliCommand
+{
+    public void Run(CliContext context)
+    {
+        context.ShowHelp();
+    }
+
+    [CliCommand(
+            Description = "Run checks to determine if this local machine is correctly set up, validate connections and settings",
+            Name = "validate")]
+    public class ConfigValidateCliCommand
+    {
+        public void Run(CliContext context)
+        {
+            Console.WriteLine(
+      @"Hello"
+            );
+        }
+    }
+}

src/TALXIS.CLI.Workspace/ProjectCliCommand.cs

@@ -0,0 +1,48 @@
+using DotMake.CommandLine;
+
+namespace TALXIS.CLI.Workspace;
+
+[CliCommand(
+    Description = "Work with MSBuild projects in your workspace (solutions, plugins, libraries, controls...)",
+    Alias = "p"
+)]
+public class ProjectCliCommand
+{
+    public void Run(CliContext context)
+    {
+        context.ShowHelp();
+    }
+
+    [CliCommand(
+            Description = "Provides a summary of MSBuild/.NET project types which can be created in the workspace, how componets should be segmented between them, their structure and references. Use this tool whenever the user asks about projects in the workspace.",
+            Name = "explain")]
+    public class ProjectExplainCliCommand
+    {
+        public void Run(CliContext context)
+        {
+            Console.WriteLine(
+      @"Use of projects in this repository
+
+Project Types Supported:
+  • Dataverse Solution (.cdsproj or .csproj): Used for defining Dataverse components and metadata. Build artifact is solution ZIP file.
+  • Dataverse Package (.csproj): Bundles multiple solutions and custom logic for deployment; references other projects to form a unit of deployment. Build artifact is package ZIP file which contains all solutions, import config, data and deployment automation/migration code.
+  • Dataverse Plugin (.csproj): Contains custom business logic, event handlers, and automation for Dataverse. Build artifact is a plugin DLL file.
+  • Power Apps Component Framework control (.csproj): Implements custom controls for Power Apps. Build artifact is a PCF control bundle JS.
+  • Power Apps Script Library (.csproj): Provides reusable scripts for Power Platform solutions. Build artifact is a script bundle JS file.
+  • Power Platform Connector (.csproj): Defines custom connectors for Power Platform integrations.
+  • Code App (.csproj): Builds fully custom frontend SPA hosted in Power Apps.
+  • Other .NET-based projects (.csproj, .xproj): Any additional supporting libraries or tools.
+
+To find information how repository should be organized, consult 'workspace explain' command/tool.
+  
+Development and Build:
+  • All projects are added to the single solution file (.sln) which is placed in the root directory
+  • MSBuild (dotnet build) is used to build all project types
+  • Solution projects can have ProjectReferences to plugin, script, PCF, and Code App project types. When the solution is built, it pulls outputs of the referenced projects and places them into the solution artifact (the build output of the solution project).
+  • Multiple solutions can be added as ProjectReferences to the package project. When the package is built, it composes ImportConfig.xml with the list of solutions and the order in which they are imported to Dataverse upon deployment.
+  • Package project type can contain C# migration and deployment automation/infra code. Dataverse packages can also contain configuration and test data which needs to be deployed with the code/definitions.
+"
+            );
+        }
+    }
+}

src/TALXIS.CLI.Workspace/WorkspaceCliCommand.cs

@@ -3,11 +3,12 @@
 namespace TALXIS.CLI.Workspace;
 
 [CliCommand(
-    Description = "Develop solutions in your local workspace",
+    Description = "Implement software in your local computer workspace (Git repository)",
     Alias = "ws",
     Children = new[]
     {
-        typeof(ComponentCliCommand)
+        typeof(ComponentCliCommand),
+        typeof(ProjectCliCommand)
     })]
 public class WorkspaceCliCommand
 {
@@ -16,6 +17,7 @@ public void Run(CliContext context)
         context.ShowHelp();
     }
 
+
     [CliCommand(
         Description = "Provides a summary of repository structure, build system, project types, components, and how they are organized for development and deployment. Use this tool whenever the user asks about organizing or understanding the workspace. This includes details about the monorepo layout, use of .NET project and solution files, supported project types (such as Dataverse solutions, plugins, packages, Power Apps components, and custom code apps), and how projects are managed and built using MSBuild. The summary also explains how solution and package projects reference and compose other components for deployment, offering flexibility in organizing code for various scenarios.",
         Name = "explain")]
@@ -24,22 +26,16 @@ public class WorkspaceExplainCliCommand
         public void Run(CliContext context)
         {
             Console.WriteLine(
-@"Repository Structure Overview
+      @"Repository Structure Overview
 
 This repository is organized as a monorepo based on the .NET project system. It uses a Visual Studio solution file (.sln) to track all projects, and each project is defined by its own project file (.csproj, .cdsproj, or other .(x)proj formats). All projects are built using MSBuild.
 
+Rules for repository root unless user explicitly instructs to do it differently:
+
   • The root contains essential files such as README.md, .gitignore, and the .sln solution file
   • The src/ directory holds all source code, organized into folders for different project types
 
-Project Types Supported:
-  • Dataverse Solution (.cdsproj or .csproj): Used for defining Dataverse components and metadata. Build artifact is solution ZIP file.
-  • Dataverse Package (.csproj): Bundles multiple solutions and custom logic for deployment; references other projects to form a unit of deployment. Build artifact is package ZIP file which contains all solutions, import config, data and deployment automation/migration code.
-  • Dataverse Plugin (.csproj): Contains custom business logic, event handlers, and automation for Dataverse. Build artifact is a plugin DLL file.
-  • Power Apps Component Framework control (.csproj): Implements custom controls for Power Apps. Build artifact is a PCF control bundle JS.
-  • Power Apps Script Library (.csproj): Provides reusable scripts for Power Platform solutions. Build artifact is a script bundle JS file.
-  • Power Platform Connector (.csproj): Defines custom connectors for Power Platform integrations.
-  • Code App (.csproj): Builds fully custom frontend SPA hosted in Power Apps.
-  • Other .NET-based projects (.csproj, .xproj): Any additional supporting libraries or tools.
+You can find supported project types with 'workspace project explain' command/tool.
 
 Repository Initialization Sequence:
   The Visual Studio solution file (.sln) and src folder MUST be initialized before creating any solutions or projects.**
@@ -50,14 +46,7 @@ The Visual Studio solution file (.sln) and src folder MUST be initialized before
   3. **Create Visual Studio solution file: dotnet new sln --name [ProjectName]**
   4. Create src/ directory: mkdir src
   
-Development and Build:
-  • All projects are added to the single solution file (.sln) which is placed in the root directory
-  • MSBuild (dotnet build) is used to build all project types
-  • Solution projects can have ProjectReferences to plugin, script, PCF, and Code App project types. When the solution is built, it pulls outputs of the referenced projects and places them into the solution artifact (the build output of the solution project).
-  • Multiple solutions can be added as ProjectReferences to the package project. When the package is built, it composes ImportConfig.xml with the list of solutions and the order in which they are imported to Dataverse upon deployment.
-  • Package project type can contain C# migration and deployment automation/infra code. Dataverse packages can also contain configuration and test data which needs to be deployed with the code/definitions.
-
-This structure is flexible and does not enforce a specific layering or project type arrangement. Developers are free to organize solutions, plugins, packages, and other projects as needed for their scenario. The .NET project system and solution file provide a unified way to manage, build, and deploy all components in the repository."
+This structure is flexible and does not enforce a specific segmentation, layering or project arrangement. Developers are free to organize solutions, plugins, packages, and other projects as needed for their scenario. The .NET project system and Visual Studio solution file provide a unified way to manage, build, and deploy all components in the repository."
             );
         }
     }