Files
msd-core/commands/gsd/new-milestone.md
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

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
gsd:new-milestone Start a new milestone cycle — update PROJECT.md and route to requirements [milestone name, e.g., 'v1.1 Notifications']
Read
Write
Bash
Agent
AskUserQuestion
Start a new milestone: questioning → research (optional) → requirements → roadmap.

Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Gathers "what's next", updates PROJECT.md, then runs requirements → roadmap cycle.

Creates/Updates:

  • .planning/PROJECT.md — updated with new milestone goals
  • .planning/research/ — domain research (optional, NEW features only)
  • .planning/REQUIREMENTS.md — scoped requirements for this milestone
  • .planning/ROADMAP.md — phase structure (continues numbering)
  • .planning/STATE.md — reset for new milestone

After: /gsd-plan-phase [N] to start execution.

<execution_context> @/.claude/get-shit-done/workflows/new-milestone.md @/.claude/get-shit-done/references/questioning.md @/.claude/get-shit-done/references/ui-brand.md @/.claude/get-shit-done/templates/project.md @~/.claude/get-shit-done/templates/requirements.md </execution_context>

Milestone name: $ARGUMENTS (optional - will prompt if not provided)

Project and milestone context files are resolved inside the workflow (init new-milestone) and delegated via <files_to_read> blocks where subagents are used.

Execute end-to-end. Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).