Roadmap: keep dotnet-template a minimal, current, low-friction .NET scaffold

[devantler]

🤖 Generated by the Daily AI Assistant

Roadmap: keep dotnet-template a minimal, current, low-friction .NET scaffold

First strategy review for dotnet-template (the repo had no roadmap label and no open issues). This epic sets the north-star and tracks the small set of theme-level work; actionable children link back here and close with Fixes #N. It deliberately mirrors the sibling go-template roadmap epic #104 — the two scaffolds should advance in lockstep.

Where the product is

A deliberately minimal, batteries-included .NET scaffold: an Example.slnx solution wiring one library project (src/Example, a single documented ExampleClass.Add member) to a matching xUnit test project (tests/Example.Tests, on xunit.v3), the house defaults baked into every project (Nullable, ImplicitUsings, AnalysisMode=All, EnforceCodeStyleInBuild, GenerateDocumentationFile, TreatWarningsAsErrors), a ci.yaml required-checks aggregator with the actual build/test enforced by the org-required reusable workflow, semantic-release → NuGet publish on v* tags, daily Dependabot, and agent tooling (AGENTS.md + .claude/skills/maintain). It is healthy and current (net10.0, SDK floor 10.0.300 with rollForward: latestFeature).

Where it should be

The bias is minimal, idiomatic, current — not feature-rich. So "advancing" this product means reducing friction and drift, never adding product features. Three themes:

1. Onboarding friction. Creating a project from the template still requires manual, error-prone steps: the README asks the adopter to rename the solution, the library project, the namespace, and the test project from Example, then replace ExampleClass. ✅ DELIVERED on main — scripts/rename-placeholders.sh (a two-pass type-then-project rename) personalises the scaffold in one shot, and the README Use this template section documents the adopt-and-delete checklist (direct parity with go-template #107).
2. Toolchain & scaffold currency. The SDK floor (global.json 10.0.300, rollForward: latestFeature) and the net10.0 TFM are bumped ad-hoc; the rationale (why this floor, when to raise it) lives nowhere. ✅ DELIVERED on main — AGENTS.md carries the Toolchain-floor policy section and the Toolchain-floor freshness maintenance task (parity with go-template chore(deps): Bump devantler-tech/reusable-workflows/.github/workflows/ci-dotnet-test.yaml from 1.31.1 to 1.32.0 #106); the SDK floor lives only in global.json as the single source of truth.
3. Template-suite parity (portfolio concern). go-template, dotnet-template, and the other templates should stay aligned on what they can share — agent files, label sets, Dependabot/cooldown policy, CI structure, README shape, and onboarding ergonomics. Divergence is drift. Tracked here as a theme; concrete reconciliation lands as additive PRs (and may graduate to a monorepo holistic-review item). In flight: PR #242 adds the copilot-setup-steps workflow for parity with go-template/platform-template (both already ship it; dotnet-template and gitops-tenant-template did not).

Rough size

Small. 2–3 focused children, each independently shippable; no large structural change. Respect the minimal-by-design constraint — reject feature-creep proposals here.

---

Refreshed 2026-06-23 (strategy review against live main): themes 1 (onboarding script) and 2 (toolchain-floor policy + freshness) marked delivered — the body previously implied they were unstarted (the 319th stale-roadmap trap). The stale .github/copilot-instructions.md reference was dropped (no longer maintained — Copilot reads AGENTS.md directly). Theme 3 (suite parity) is the lone open direction; PR #242 is its first reconciliation.

[devantler]

🤖 Generated by the Daily AI Assistant

Decomposed into actionable children (each independently shippable, closes with Fixes #218):

• Onboarding: add a rename-placeholders script to repoint Example → project name in one shot #219 — Onboarding: add a rename-placeholders script (theme 1; direct parity with go-template chore(deps): Bump devantler-tech/reusable-workflows/.github/workflows/release.yaml from 1.31.1 to 1.32.0 #107) — ready, highest-value
• docs: document the .NET toolchain-floor policy (SDK floor + TFM) #220 — docs: document the .NET toolchain-floor policy (theme 2; parity with go-template chore(deps): Bump devantler-tech/reusable-workflows/.github/workflows/ci-dotnet-test.yaml from 1.31.1 to 1.32.0 #106)
• Theme 3 (template-suite parity) stays tracked on this epic; reconciliation lands as additive PRs and may graduate to a monorepo holistic-review item.

[devantler]

🤖 Generated by the Daily AI Assistant

Roadmap reconciliation — themes 1 & 2 are delivered; theme 3 in progress

A status pass against main shows this epic's body is now stale on its two concrete themes:

• Theme 1 — onboarding friction (rename script): ✅ DELIVERED. scripts/rename-placeholders.sh
  shipped in feat(scripts): add rename-placeholders.sh #221 (commit fed70630, 2026-06-10) — direct parity with go-template's #107. It
  renames Example across the .slnx, .csprojs, .cs files and README (PascalCase-derives the name
  from the origin remote when no argument is given), handles the dotted-name → type-token case, uses
  git mv to preserve history, and is idempotent. Deliberately leaves AGENTS.md /
  .github/copilot-instructions.md for the adopter to adapt. The body still says "dotnet-template has
  no equivalent → child issue" — that's no longer true.

• Theme 2 — toolchain-floor policy: ✅ DELIVERED. The body says the SDK-floor/TFM rationale "lives
  nowhere"; it now lives in AGENTS.md ## Maintenance as an explicit Toolchain-floor policy
  (track latest GA, advance the global.json SDK floor + net10.0 TFM in lockstep, only when a new
  .NET GA / tooling / security / EOL reason forces it, record the trigger in the PR body) plus a
  matching Toolchain-floor freshness task-menu item that names every copy to keep in sync
  (both *.csproj, global.json, the copilot-instructions.md prose). This mirrors go-template #106.

• Theme 3 — template-suite parity: in progress. Closing one concrete divergence now:
  .github/CODEOWNERS (* @devantler) was present in dotnet-template, platform-template and ksail but
  missing from go-template → chore: add .github/CODEOWNERS for template-suite parity go-template#117 adds it (byte-identical). After that
  merges the suite is aligned on CODEOWNERS. (The remaining go-template-only copilot-setup-steps.yml
  is intentionally not propagated here — it serves the GitHub Copilot coding agent, which is not
  in this maintainer's toolchain.) Theme 3 stays open as the standing portfolio-parity tracker.

Net: the only remaining open work under this epic is the ongoing theme-3 parity sweep — themes 1 & 2
can be considered complete. Leaving this note rather than editing the epic body so the history is
visible; happy to fold the corrections into the body if preferred.