Files
msd-core/docs/features/ui-phase-auto-detection.md
Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.
2026-10-06 01:47:40 +02:00

879 B

id, title, group
id title group
54 UI Phase Auto-Detection v1.28 Features

Part of: /msd-new-project and /msd-progress

Purpose: Automatically detect UI-heavy projects and surface /msd-ui-phase recommendation.

Requirements:

  • REQ-UI-DETECT-01: System MUST detect UI signals in project description (keywords, framework references)
  • REQ-UI-DETECT-02: System MUST annotate ROADMAP.md phases with ui_hint when applicable
  • REQ-UI-DETECT-03: System MUST suggest /msd-ui-phase in next steps for UI-heavy phases
  • REQ-UI-DETECT-04: System MUST NOT make /msd-ui-phase mandatory

Process:

  1. Detect — Scan project description and tech stack for UI signals (keywords, framework references)
  2. Annotate — Add ui_hint markers to applicable phases in ROADMAP.md
  3. Surface — Include /msd-ui-phase recommendation in next steps for UI-heavy phases