feat(#194): add short-name prompt for agentic scaffolds

 Prompt for a project short name when Agentic Copilot is enabled so
 generated scaffold guidance can replace placeholders such as
 Invoke-<ShortName>*.

Author: stiwicourage

CHANGELOG.md

@@ -13,7 +13,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
     - Example scaffolds now merge the existing example README with the Agentic starter README instead of flattening the example guide into the generic starter file.
     - The starter tree is now generated from a filtered mirror of Nova's own agentic `.github/` files, with a dedicated sync script and drift test so future scaffolds and `dist` stay aligned with the maintained source guidance.
     - The generated architect/design prompt now requires final design packages and issue/work item drafts to be returned as copy-ready Markdown using the project Markdown authoring guidance.
-  - The generated guidance now explicitly keeps Agentic Copilot projects on the Nova build model, treats `.psm1` / `.psd1` files as generated `dist` output, requires PlatyPS-compatible help for public commands/classes, expects one focused source-mirrored test file for every new or changed `src/**/*.ps1` file, and tells agents to honor `project.json` `Manifest.PowerShellHostVersion` when writing PowerShell code and tests.
+  - The generated guidance now explicitly keeps Agentic Copilot projects on the Nova build model, treats `.psm1` / `.psd1` files as generated `dist` output, requires PlatyPS-compatible help for public commands/classes, expects one focused source-mirrored test file for every new or changed `src/**/*.ps1` file, tells agents to honor `project.json` `Manifest.PowerShellHostVersion` when writing PowerShell code and tests, and now asks for a short project name so placeholders such as `Invoke-<ShortName>*` can be replaced in the generated starter files.
   - The generated guidance now keeps local `run.ps1` quality loops ordered as ScriptAnalyzer, `Invoke-NovaBuild`, then `Test-NovaBuild`, and tells agents to fix ScriptAnalyzer findings instead of excluding or suppressing rules.
 
 ### Changed

README.md

@@ -506,7 +506,7 @@ Packaged resources that ship with the module, including:
 - the packaged example project under `src/resources/example/`
 - the Agentic Copilot starter package under `src/resources/agentic-copilot/`
 
-The example project is both a shipped resource and a maintained working reference. The Agentic Copilot starter package is generated from Nova's repository-local agentic guidance, including Nova build/test/package expectations, `project.json` `Manifest.PowerShellHostVersion` compatibility guidance, generated `dist` module files, command-help ownership, and source-mirrored test guidance. Run
+The example project is both a shipped resource and a maintained working reference. The Agentic Copilot starter package is generated from Nova's repository-local agentic guidance, including Nova build/test/package expectations, `project.json` `Manifest.PowerShellHostVersion` compatibility guidance, generated `dist` module files, command-help ownership, and source-mirrored test guidance. When the init flow adds that starter package, it also asks for a short project name so scaffolded guidance can replace placeholders such as `Invoke-<ShortName>*`. Run
 `./scripts/build/Sync-AgenticCopilotScaffold.ps1` after changing `.github/agents/`, `.github/instructions/`,
 `.github/skills/`, `.github/prompts/`, or `.github/copilot-instructions.md` so future scaffolds and `dist` stay in sync.
 

RELEASE_NOTE.md

@@ -11,7 +11,7 @@ changes will be included in the next **stable** release!
 - `Initialize-NovaModule` and `% nova init` now offer an optional Agentic Copilot starter package in both the minimal and example interactive scaffold flows.
     - The starter package follows a filtered mirror of Nova's maintained agentic guidance so newly scaffolded projects receive a broader Nova-style agentic baseline without Nova-specific CodeScene or docs-site surfaces.
     - Generated architect/design guidance now requires final design packages and issue/work item drafts to be returned as copy-ready Markdown using the project Markdown authoring guidance.
-  - Generated implementation/test guidance now keeps projects on Nova build/test/package workflows, treats `.psm1` / `.psd1` files as generated output, calls out PlatyPS help plus one focused source-mirrored test file for every new or changed `src/**/*.ps1` file, and tells agents to honor `project.json` `Manifest.PowerShellHostVersion` when writing PowerShell code and tests.
+  - Generated implementation/test guidance now keeps projects on Nova build/test/package workflows, treats `.psm1` / `.psd1` files as generated output, calls out PlatyPS help plus one focused source-mirrored test file for every new or changed `src/**/*.ps1` file, tells agents to honor `project.json` `Manifest.PowerShellHostVersion` when writing PowerShell code and tests, and now asks for a short project name so placeholders such as `Invoke-<ShortName>*` can be replaced in the generated starter files.
   - Generated quality-loop guidance now keeps ScriptAnalyzer first and tells agents to fix ScriptAnalyzer findings instead of excluding or suppressing rules.
 
 ### Changed

docs/NovaModuleTools/en-US/Initialize-NovaModule.md

@@ -27,15 +27,15 @@ PS> Initialize-NovaModule [-Path <string>] [-Example] [-WhatIf] [-Confirm] [<Com
 
 `Initialize-NovaModule` creates a new project folder, the standard `src/` layout, and a starter `project.json` file.
 
-The command collects project details interactively, including the module name, description, version, author, minimum PowerShell version, Git initialization, and an optional Agentic Copilot starter package. The Agentic package follows Nova's maintained agentic guidance through a filtered starter mirror, including Nova build/test/package expectations, `project.json` `Manifest.PowerShellHostVersion` compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated `dist` module files, command-help ownership, and source-mirrored test guidance. For the standard scaffold, the interactive flow also includes optional basic Pester support.
+The command collects project details interactively, including the module name, description, version, author, minimum PowerShell version, Git initialization, and an optional Agentic Copilot starter package. When you enable the Agentic package, Nova also asks for a project short name used in generated guidance placeholders such as `Invoke-<ShortName>*`; for NovaModuleTools the short name is `Nova`, but it could also have been `NMT`. The Agentic package follows Nova's maintained agentic guidance through a filtered starter mirror, including Nova build/test/package expectations, `project.json` `Manifest.PowerShellHostVersion` compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated `dist` module files, command-help ownership, and source-mirrored test guidance. For the standard scaffold, the interactive flow also includes optional basic Pester support.
 
 If you enter an invalid answer during the interactive flow, `Initialize-NovaModule` reports the validation problem immediately and retries that prompt before it continues to the next question.
 
 Use this command when you want to start a new module in the NovaModuleTools structure without hand-creating the project layout.
 
 Use `-Path` when you want to create the project under a specific base directory. Positional path syntax is no longer supported.
 
-Use `-Example` when you want the scaffold to start from the packaged example project instead of the minimal default layout. The example flow keeps the example source, resource, and test files, skips the Pester enable/disable question, and applies the interactive metadata values to the copied `project.json`. The standard and example flows share the same inline validation and retry behavior for interactive answers, including the optional Agentic Copilot setup prompt after the Git question. When you answer `Yes`, Nova adds the same starter package to either scaffold style and merges the example README instead of replacing it with the generic starter README outright.
+Use `-Example` when you want the scaffold to start from the packaged example project instead of the minimal default layout. The example flow keeps the example source, resource, and test files, skips the Pester enable/disable question, and applies the interactive metadata values to the copied `project.json`. The standard and example flows share the same inline validation and retry behavior for interactive answers, including the optional Agentic Copilot setup prompt after the Git question. When you answer `Yes`, Nova asks for the short project name, adds the same starter package to either scaffold style, and merges the example README instead of replacing it with the generic starter README outright.
 
 This command supports `-WhatIf` and `-Confirm` through PowerShell `SupportsShouldProcess`. Use `-WhatIf` to preview the scaffold target after the interactive answers have been collected, without creating folders, writing `project.json`, or initializing Git.
 

docs/commands.html

@@ -181,6 +181,9 @@ <h3>Start a new project</h3>
                             compatibility guidance, strict ScriptAnalyzer guidance without excluded rules, generated
                             <code>dist</code> module files, command-help ownership, and source-mirrored test guidance.
                         </p>
+                        <p>If you enable the Agentic package, Nova also asks for a short project name used in generated
+                            guidance placeholders such as <code>Invoke-&lt;ShortName&gt;*</code>. For NovaModuleTools the
+                            short name is <code>Nova</code>, but it could also have been <code>NMT</code>.</p>
                         <ul class="plain-list">
                             <li><strong>Use when:</strong> you are creating a fresh NovaModuleTools project</li>
                             <li data-command-visibility="command-line" hidden><strong>Remember:</strong> pass the target path

docs/core-workflows.html

@@ -130,6 +130,9 @@ <h2>Create the project</h2>
                     <code>Manifest.PowerShellHostVersion</code> compatibility guidance, strict ScriptAnalyzer guidance
                     without excluded rules, generated <code>dist</code> module files, command-help ownership, and
                     source-mirrored test guidance.</p>
+                <p>When you answer <code>Yes</code>, Nova also asks for a short project name used in generated guidance
+                    placeholders such as <code>Invoke-&lt;ShortName&gt;*</code>. For NovaModuleTools the short name is
+                    <code>Nova</code>, but it could also have been <code>NMT</code>.</p>
                 <p>Use the example scaffold when you want the shortest path to understanding a real project layout, test
                     suite, and package configuration. Use the minimal scaffold when you already know the structure you
                     want.</p>

docs/getting-started.html

@@ -201,6 +201,9 @@ <h2>4. Scaffold the packaged example</h2>
                     without excluded rules, generated <code>dist</code> module files, command-help ownership, and
                     source-mirrored test guidance.
                     Nova then creates a project folder under the path you selected.</p>
+                <p>If you enable the Agentic package, Nova also asks for a short project name used in generated guidance
+                    placeholders such as <code>Invoke-&lt;ShortName&gt;*</code>. For NovaModuleTools the short name is
+                    <code>Nova</code>, but it could also have been <code>NMT</code>.</p>
                 <div class="notice" data-command-visibility="command-line" hidden>
                     <strong>CLI caveat:</strong>
                     <p>Use <code>% nova init --path ~/Work</code> or <code>% nova init -p ~/Work</code>, not positional
@@ -311,8 +314,9 @@ <h2>7. Start from the minimal scaffold instead</h2>
                     </div>
                 </div>
                 <p>The minimal scaffold still asks for the same core project metadata, including the optional Agentic
-                    Copilot setup question, but it gives you a smaller starter layout than the example project. When
-                    enabled, the Agentic package uses the same filtered starter mirror as the example scaffold.</p>
+                    Copilot setup question and the follow-up short-name prompt when you answer Yes, but it gives you a
+                    smaller starter layout than the example project. When enabled, the Agentic package uses the same
+                    filtered starter mirror as the example scaffold.</p>
                 <p>Use the example scaffold when you want the fastest learning path. Use the minimal scaffold when you
                     want the leanest new project.</p>
             </section>

scripts/build/Sync-AgenticCopilotScaffold.psd1

@@ -64,7 +64,7 @@
         }
         @{
             Old = '- Keep `docs/*.html`, `docs/NovaModuleTools/en-US/*.md`, and contributor docs clearly separated by audience and syntax.'
-            New = '- Keep command help, contributor docs, and release history clearly separated by audience and syntax.'
+            New = '- Keep command help `docs/{{ProjectName}}/en-US/*.md`, contributor docs, and release history clearly separated by audience and syntax.'
         }
         @{
             Old = '- CI-parity coverage flow: `./scripts/build/ci/Invoke-NovaModuleToolsCI.ps1 -OutputDirectory ./artifacts`'
@@ -116,11 +116,11 @@
         }
         @{
             Old = '- `docs/NovaModuleTools/en-US/` - command help source'
-            New = '- `docs/<ProjectName>/en-US/` - command help source, when present'
+            New = '- `docs/{{ProjectName}}/en-US/` - command help source'
         }
         @{
             Old = '- `project docs` - end-user GitHub Pages content'
-            New = '- `docs/` - project documentation, when present'
+            New = '- `docs/` - project documentation'
         }
         @{
             Old = '- `.github/instructions/documentation.instructions.md`'
@@ -232,7 +232,7 @@
         }
         @{
             Old = '- project docs - end-user GitHub Pages content'
-            New = '- `docs/` - project documentation, when present'
+            New = '- `docs/` - project documentation'
         }
         @{
             Old = 'applyTo: "tests/**/*.ps1,scripts/build/**/*.ps1,"'
@@ -252,7 +252,7 @@
         }
         @{
             Old = '-Nova*'
-            New = '-<function>*'
+            New = '-{{ShortName}}*'
         }
         @{
             Old = ', and the `nova` CLI routing model.'

src/private/scaffold/GetNovaModuleQuestions.ps1

@@ -1,16 +1,33 @@
-function Get-NovaModuleProjectNameValidation {
+function Get-NovaModuleSingleWordValidation {
+    [CmdletBinding()]
+    param(
+        [Parameter(Mandatory)][string]$Pattern,
+        [Parameter(Mandatory)][string]$Message,
+        [Parameter(Mandatory)][string]$ErrorId
+    )
+
+    $validationPattern = $Pattern
+
     return @{
-        Test = {
+        Test = ({
             param($Value)
 
-            return $Value -match '^[A-Za-z][A-Za-z0-9_.]*$'
-        }
-        Message = 'Module name is invalid. Use a single word that starts with a letter and contains only letters, numbers, underscores, or periods.'
-        ErrorId = 'Nova.Validation.ScaffoldProjectNameInvalid'
+            return $Value -match $validationPattern
+        }).GetNewClosure()
+        Message = $Message
+        ErrorId = $ErrorId
         Category = [System.Management.Automation.ErrorCategory]::InvalidData
     }
 }
 
+function Get-NovaModuleProjectNameValidation {
+    return Get-NovaModuleSingleWordValidation -Pattern '^[A-Za-z][A-Za-z0-9_.]*$' -Message 'Module name is invalid. Use a single word that starts with a letter and contains only letters, numbers, underscores, or periods.' -ErrorId 'Nova.Validation.ScaffoldProjectNameInvalid'
+}
+
+function Get-NovaModuleProjectShortNameValidation {
+    return Get-NovaModuleSingleWordValidation -Pattern '^[A-Za-z][A-Za-z0-9]*$' -Message 'Project short name is invalid. Use a short word that starts with a letter and contains only letters or numbers.' -ErrorId 'Nova.Validation.ScaffoldProjectShortNameInvalid'
+}
+
 function Get-NovaModuleBaseQuestionSet {
     return [ordered]@{
         ProjectName = @{
@@ -83,6 +100,21 @@ function Get-NovaModuleAgenticCopilotQuestion {
     }
 }
 
+function Get-NovaModuleAgenticCopilotProjectShortNameQuestion {
+    return @{
+        Caption = 'Project short name'
+        Message = 'Enter a short project name for generated guidance placeholders such as Invoke-<ShortName>*. For NovaModuleTools the short name is Nova, but it could also have been NMT.'
+        Prompt = 'ProjectShortName'
+        Default = 'MANDATORY'
+        Validation = Get-NovaModuleProjectShortNameValidation
+        Condition = {
+            param([System.Collections.IDictionary]$Answer)
+
+            return $Answer.Contains('EnableAgenticCopilot') -and $Answer['EnableAgenticCopilot'] -eq 'Yes'
+        }
+    }
+}
+
 function Get-NovaModuleQuestionSet {
     [CmdletBinding()]
     param(
@@ -91,6 +123,7 @@ function Get-NovaModuleQuestionSet {
 
     $questions = Get-NovaModuleBaseQuestionSet
     $questions.EnableAgenticCopilot = Get-NovaModuleAgenticCopilotQuestion
+    $questions.ProjectShortName = Get-NovaModuleAgenticCopilotProjectShortNameQuestion
 
     if (-not $Example) {
         $questions.EnablePester = Get-NovaModulePesterQuestion

src/private/scaffold/InitializeNovaModuleAgenticCopilotScaffold.ps1

@@ -1,3 +1,16 @@
+function Get-NovaModuleAgenticCopilotProjectShortName {
+    [CmdletBinding()]
+    param(
+        [Parameter(Mandatory)][hashtable]$Answer
+    )
+
+    if (-not $Answer.ContainsKey('ProjectShortName') -or [string]::IsNullOrWhiteSpace($Answer.ProjectShortName)) {
+        Stop-NovaOperation -Message 'Project short name is required when Agentic Copilot setup is enabled.' -ErrorId 'Nova.Validation.AgenticCopilotProjectShortNameMissing' -Category InvalidData -TargetObject 'ProjectShortName'
+    }
+
+    return $Answer.ProjectShortName
+}
+
 function Get-NovaModuleAgenticCopilotTemplateTokenMap {
     [CmdletBinding()]
     param(
@@ -12,6 +25,7 @@ function Get-NovaModuleAgenticCopilotTemplateTokenMap {
 
     return [ordered]@{
         '{{ProjectName}}' = $Answer.ProjectName
+        '{{ShortName}}' = Get-NovaModuleAgenticCopilotProjectShortName -Answer $Answer
         '{{ProjectDescription}}' = $description
         '{{StartHereBody}}' = @'
 Use this repository as the starting point for your module.