msd-core/docs/features/developer-profiling.md at fe3ed0669103d6a8edd1caffaaa47caf6a4b7eba

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.7 KiB

Raw Blame History

id, title, group

id	title	group
38	Developer Profiling	Infrastructure Features

Command: /msd-profile-user [--questionnaire] [--refresh]

Purpose: Analyze Claude Code session history to build behavioral profiles across 8 dimensions, generating artifacts that personalize Claude's responses to the developer's style.

Dimensions:

Communication style (terse vs verbose, formal vs casual)
Decision patterns (rapid vs deliberate, risk tolerance)
Debugging approach (systematic vs intuitive, log preference)
UX preferences (design sensibility, accessibility awareness)
Vendor/technology choices (framework preferences, ecosystem familiarity)
Frustration triggers (what causes friction in workflows)
Learning style (documentation vs examples, depth preference)
Explanation depth (high-level vs implementation detail)

Generated Artifacts:

USER-PROFILE.md — Full behavioral profile with evidence citations
CLAUDE.md profile section — Auto-discovered by Claude Code

Flags:

--questionnaire — Interactive questionnaire fallback when session history is unavailable
--refresh — Re-analyze sessions and regenerate profile

Pipeline Modules:

profile-pipeline.cjs — Session scanning, message extraction, sampling
profile-output.cjs — Profile rendering, questionnaire, artifact generation
msd-user-profiler agent — Behavioral analysis from session data

Requirements:

REQ-PROF-01: Session analysis MUST cover at least 8 behavioral dimensions
REQ-PROF-02: Profile MUST cite evidence from actual session messages
REQ-PROF-03: Questionnaire MUST be available as fallback when no session history exists
REQ-PROF-04: Generated artifacts MUST be discoverable by Claude Code (CLAUDE.md integration)

1.7 KiB Raw Blame History

1.7 KiB

Raw Blame History