Optional Agentic Copilot scaffold for `Initialize-NovaModule` / `nova init`

[stiwicourage]

Problem

Initialize-NovaModule / nova init can scaffold a module, but they do not currently offer an opinionated way to add the
repository-local Agentic Copilot workflow that NovaModuleTools now uses itself.

Users who want that setup must add it manually after scaffold creation, and the learning path between the example scaffold
and a real new project is less consistent than it should be.

Why this change

We want users to be able to opt into a Nova-style Agentic Copilot workflow from day one, while keeping the feature optional
and preserving a clean default scaffold for users who do not want it.

Scope

Add an optional interactive init question to both the minimal and example scaffold flows.

Use this exact prompt design:

• Label: Agentic Copilot setup
• Question: Do you want Nova to add Agentic Copilot setup files to this project?
• Default: No

Behavior rules:

• ask in both Initialize-NovaModule and nova init
• ask in both minimal and example scaffold flows
• place the question after the Git question
• keep the feature interactive-only in v1

When the user answers Yes, generate the same Copilot-specific starter package for both flows through one shared
post-scaffold step.

Generated package

• root:
  • AGENTS.md
  • README.md
  • CONTRIBUTING.md
  • CHANGELOG.md
  • RELEASE_NOTE.md
• .github/:
  • copilot-instructions.md
  • pull_request_template.md
• .github/agents/:
  • architect.agent.md
  • powershell-developer.agent.md
  • test-engineer.agent.md
  • reviewer.agent.md
  • release-manager.agent.md
• .github/instructions/:
  • powershell-coding-standards.instructions.md
  • testing-policy.instructions.md
  • release-policy.instructions.md
• .github/skills/:
  • markdown-authoring/SKILL.md
  • powershell-module-development/SKILL.md
  • pester-testing/SKILL.md
  • release-and-changelog/SKILL.md
• .github/prompts/:
  • design-change.prompt.md
  • implement-issue.prompt.md
  • review-change.prompt.md
  • improve-test-coverage.prompt.md
  • prepare-release.prompt.md

Template model

• Store the starter package under src/resources/agentic-copilot/ as one mirrored tree.
• Use a dedicated helper to resolve that template root.
• Treat generated .github/ files as inherited from Nova’s maintained core template set.
• Keep the starter package mostly generic, with only limited project-specific substitution.
• Keep the generated content limited to surfaces that exist in a fresh scaffold.

Root-file starter direction

• README.md
  • short repo description first
  • ## Agentic Copilot workflow
  • numbered 1-4 flow with correct agent + prompt pairings
  • ## Start here follows
• AGENTS.md
  • thin landing page only
  • ## Workflow with step names only
  • soft transition to ## Authoritative files
  • points to README.md, CONTRIBUTING.md, and the relevant .github/ surfaces
• CONTRIBUTING.md
  • normal contribution guide first
  • later ## Agentic Copilot workflow
  • short recommended 4-step flow
• CHANGELOG.md
  • clean starter file with intro text, ## [Unreleased], and all six official section headings
• RELEASE_NOTE.md
  • clean starter file with intro text, ## [Unreleased], all six official section headings, and the exact placeholder
    under ### Added:
    • No public API or workflow changes in this release. Internal maintenance only.

Out of scope

For v1, do not include:

• docs-site agent/skill
• github-actions skill
• documentation-separation instruction
• CodeScene-specific skills
• CI-failure prompt
• GitHub issue templates
• provider-neutral or Claude-first setup
• non-interactive switches/flags for this feature
• a separate example-only Agentic package baked into src/resources/example

Acceptance criteria

• Initialize-NovaModule and nova init both ask the new Agentic Copilot question.
• The question is asked in both minimal and example flows.
• The question defaults to No.
• The question appears after the Git question.
• A Yes answer generates the same Copilot starter package in both flows.
• The generated package uses the latest Nova-owned starter templates shipped with the installed Nova version.
• The generated content is limited to surfaces that exist in a fresh scaffold.
• The starter package is sourced from src/resources/agentic-copilot/ through a dedicated helper.
• The example README is handled through a small merge strategy instead of being flattened into a generic file.
• Help/docs/tests are updated to reflect the new init behavior.

Validation

• Add targeted Pester coverage for:
  • question-set ordering
  • default behavior
  • minimal flow generation
  • example flow generation
  • generated file set
• Run the normal repository quality loop:
  • pwsh -NoLogo -NoProfile -File ./run.ps1

Open questions

• None at the feature-scope level.

[stiwicourage]

● Implementeringen er færdig. Jeg kører nu maintainability-safeguard og laver den sidste lille polish på cmdlet-overfladen, hvis den mangler hjælp/metadata.

✗ pre_commit_code_health_safeguard (MCP: codescene) · git_repository_path: "/Users/stiwi.courage/workspace/couragedk/TestCopilot"
└ MCP server 'codescene': Error: CS CLI exited with code 1: git execution failed: fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.

[stiwicourage]

agentic flow should build the code based on which "PowerShellHostVersion": "7.4",