msd-core/commands/msd/manager.md at next

Files

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

1.6 KiB

Raw Permalink Blame History

name, description, argument-hint, allowed-tools, requires

name

description

argument-hint

allowed-tools

requires

msd:manager

Interactive command center for managing multiple phases from one terminal

[--analyze-deps]

Read

Write

Bash

Glob

Grep

AskUserQuestion

Skill

Agent

phase

Single-terminal command center for managing a milestone. Shows a dashboard of all phases with visual status indicators, recommends optimal next actions, and dispatches work — discuss runs inline, plan/execute run as background agents.

Designed for power users who want to parallelize work across phases from one terminal: discuss a phase while another plans or executes in the background.

Creates/Updates:

No files created directly — dispatches to existing MSD commands via Skill() and background Task agents.
Reads .planning/STATE.md, .planning/ROADMAP.md, phase directories for status.

After: User exits when done managing, or all phases complete and milestone lifecycle is suggested.

<execution_context> @~~/.claude/msd-core/workflows/manager.md @~~/.claude/msd-core/references/ui-brand.md </execution_context>

No arguments required. Requires an active milestone with ROADMAP.md and STATE.md.

Project context, phase list, dependencies, and recommendations are resolved inside the workflow using msd-tools query init.manager. No upfront context loading needed.

If `--analyze-deps` is in $ARGUMENTS: Read and execute `~/.claude/msd-core/workflows/analyze-dependencies.md` end-to-end.

Execute end-to-end. Maintain the dashboard refresh loop until the user exits or all phases complete.

1.6 KiB Raw Permalink Blame History

1.6 KiB

Raw Permalink Blame History