mindforge-profile-user
This Claude Code skill generates a developer behavioral profile by analyzing session history or using a questionnaire fallback, then creates discoverable artifacts including USER-PROFILE.md and preference configurations that personalize agent responses. Use it to establish baseline developer behavior patterns, refresh existing profiles with the --refresh flag to track behavioral changes, or bypass session analysis entirely with --questionnaire when historical data is unavailable.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge-profile-user && cp -r /tmp/mindforge-profile-user/.agent/skills/mindforge-profile-user ~/.claude/skills/mindforge-profile-userSKILL.md
<objective> Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, /mindforge-dev-preferences, GEMINI.md section) that personalize the agent'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> @.agent/workflows/mindforge-profile-user.md @.agent/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, GEMINI.md sections) 9. Sequential artifact generation 10. Summary with refresh diff (if applicable) </process>
Publish a skill to the npm registry (or private registry).
Add an idea to the backlog parking lot (999.x numbering)
Add phase to end of current milestone in roadmap
Generate tests for a completed phase based on UAT criteria and implementation
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Cross-phase audit of all outstanding UAT and verification items
Run all remaining phases autonomously — discuss→plan→execute per phase