msd-core/commands/gsd/profile-user.md at 8bc255c266954f653d1b6230d3d4aa7df875f4ee

Files

Tom Boucher 1452b1275b fix(dispatcher): rename Task→Agent in allowed-tools, workflow prose, and agent tools frontmatter

Fixes #3168

The Claude Code subagent dispatcher tool is named `Agent` (with `subagent_type`
parameter). The `Task*` namespace (TaskCreate, TaskList, TaskGet, TaskUpdate,
TaskOutput, TaskStop) is the separate task-tracker. GSD's commands, workflows,
and agents were partially migrated and still referenced `- Task` / `Task(` in
55 files, causing orchestrators to silently fall back to inline execution when
no `Task` tool appeared on their tool surface.

Changes:
- `commands/gsd/*.md` allowed-tools: replaced `- Task` with `- Agent` in 24
  files; removed duplicate `- Task` from autonomous.md (already had `- Agent`)
- `get-shit-done/workflows/*.md`: replaced dispatcher `Task(` → `Agent(` in
  29 workflow files (~133 call sites); TaskCreate/List/Get/Update/Output/Stop
  left untouched
- `agents/gsd-debug-session-manager.md`: replaced `Task` → `Agent` in tools
  frontmatter (the only remaining agent with the wrong name)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-06 15:00:08 -04:00

1.6 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd: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, /gsd-dev-preferences, 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/get-shit-done/workflows/profile-user.md @~~/.claude/get-shit-done/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:

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

1.6 KiB Raw Blame History

1.6 KiB

Raw Blame History