a9a7a328e6
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.
23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
---
|
|
id: 148
|
|
title: Smart Entry Launcher
|
|
group: v1.43.0 Features
|
|
---
|
|
|
|
**Command:** `/msd-next`
|
|
|
|
**Tool:** `msd-tools smart-entry [--json]`
|
|
|
|
**Purpose:** Provide a state-aware front door that reads project/workflow state, classifies the user's situation, presents a short menu, and dispatches exactly one existing MSD command.
|
|
|
|
**Requirements:**
|
|
- REQ-SMART-ENTRY-01: Detection MUST be read-only and deterministic; classification lives in `msd-tools smart-entry`.
|
|
- REQ-SMART-ENTRY-02: The launcher MUST never perform project work directly; it only displays a menu and dispatches one command.
|
|
- REQ-SMART-ENTRY-03: The workflow MUST fall back to `/msd-progress` if detection fails.
|
|
- REQ-SMART-ENTRY-04: Each classified situation MUST provide exactly one recommended action and valid slash commands.
|
|
- REQ-SMART-ENTRY-05: Text-mode runtimes MUST receive a numbered-list fallback instead of being stranded by interactive UI assumptions.
|
|
|
|
**Situations:** no project, paused, blocked, verify failed, needs first phase, planning, executing, verify pending, idle stranded, complete, unknown.
|
|
|
|
**Reference:** [Smart Entry Design](superpowers/specs/2026-06-27-msd-smart-entry-design.md)
|