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.
47 lines
1.6 KiB
Markdown
47 lines
1.6 KiB
Markdown
---
|
|
name: msd:profile-user
|
|
description: Generate developer behavioral profile and create Claude-discoverable artifacts
|
|
argument-hint: "[--questionnaire] [--refresh]"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Bash
|
|
- Glob
|
|
- Grep
|
|
- AskUserQuestion
|
|
- Agent
|
|
---
|
|
|
|
<objective>
|
|
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.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/msd-core/workflows/profile-user.md
|
|
@~/.claude/msd-core/references/ui-brand.md
|
|
</execution_context>
|
|
|
|
<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
|
|
</context>
|
|
|
|
<process>
|
|
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)
|
|
</process>
|