Files
msd-core/commands/msd/profile-user.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

1.6 KiB

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
msd:profile-user Generate developer behavioral profile and create Claude-discoverable artifacts [--questionnaire] [--refresh]
Read
Write
Bash
Glob
Grep
AskUserQuestion
Agent
Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, `msd-dev-preferences` skill config, CLAUDE.md section) that personalize Claude's responses.

Routes to the profile-user workflow which orchestrates the full flow: consent gate, session analysis or questionnaire fallback, profile generation, result display, and artifact selection.

<execution_context> @/.claude/msd-core/workflows/profile-user.md @/.claude/msd-core/references/ui-brand.md </execution_context>

Flags from $ARGUMENTS: - `--questionnaire` -- Skip session analysis entirely, use questionnaire-only path - `--refresh` -- Rebuild profile even when one exists, backup old profile, show dimension diff Execute the profile-user workflow end-to-end.

The workflow handles all logic including:

  1. Initialization and existing profile detection
  2. Consent gate before session analysis
  3. Session scanning and data sufficiency checks
  4. Session analysis (profiler agent) or questionnaire fallback
  5. Cross-project split resolution
  6. Profile writing to USER-PROFILE.md
  7. Result display with report card and highlights
  8. Artifact selection (dev-preferences, CLAUDE.md sections)
  9. Sequential artifact generation
  10. Summary with refresh diff (if applicable)