msd-core/commands/gsd/new-project.md at 55fba5f7ce8a7d06ac8a3f0a5f5f326310a82c62

Files

Tom Boucher ed133cc116 enhance(#3085 ): add Grep to allowed-tools for 21 skills (#4397 )

* enhance(#3085): add Grep to allowed-tools for 21 skills

29 of 71 skills omit Grep from allowed-tools, forcing Bash grep for
structured search instead of the dedicated tool. Adds Grep to the
21-skill subset confirmed safe in prior review (excludes the 6
gsd-ns-* dispatchers, gsd-help, and gsd-surface, which have no
plausible structured-search need).

Hand-edits commands/gsd/*.md only; skills/*/SKILL.md is regenerated
via `npm run gen:plugin-skills` from that source. Updates the one
hardcoded copilot-install test assertion affected by gsd-health's
new tool order.

* chore(#3085): backfill changeset PR number

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

* test(#2618): assert the Needs clause on the structured field, not the path-length-dependent bullet

The bullet embeds the todo file's ABSOLUTE path, so its total length
varies by runner tmpdir: on macOS CI, /private/var/folders/… plus the
test harness's gsd-test-run-* wrapper pushed the full bullet to 244
chars — past renderPendingTodoBullet's intended 240-char cap, whose
documented first degradation step drops the Needs clause. The product
behavior is correct (#2618 design); the assertion was runner-dependent.
The extraction is now pinned on json.todos[0].needs; the rendered-bullet
shape stays covered by the path-independent title assertion and the
renderer's own unit rows.

Found blocking #4186's CI on the macOS shard (test landed 30 minutes
earlier in b7406b293f / PR #4384).

---------

Co-authored-by: sim <sim@local>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-06 13:37:47 -04:00

1.6 KiB

Raw Blame History

name, description, argument-hint, allowed-tools, requires

name

description

argument-hint

allowed-tools

requires

gsd:new-project

Initialize a new project with deep context gathering and PROJECT.md

[--auto]

Read

Bash

Grep

Write

Agent

AskUserQuestion

config

phase

plan-phase

<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API. </runtime_note>

**Flags:** - `--auto` — Automatic mode. After config questions, runs research → requirements → roadmap without further interaction. Expects idea document via @ reference. Initialize a new project through unified flow: questioning → research (optional) → requirements → roadmap.

Creates:

.planning/PROJECT.md — project context
.planning/config.json — workflow preferences
.planning/research/ — domain research (optional)
.planning/REQUIREMENTS.md — scoped requirements
.planning/ROADMAP.md — phase structure
.planning/STATE.md — project memory

After this command: Run /gsd:plan-phase 1 to start execution.

<execution_context> @~~/.claude/gsd-core/workflows/new-project.md @~~/.claude/gsd-core/references/questioning.md @~~/.claude/gsd-core/references/ui-brand.md @~~/.claude/gsd-core/templates/project.md @~/.claude/gsd-core/templates/requirements.md </execution_context>

Execute end-to-end. Preserve all workflow gates (validation, approvals, commits, routing).

1.6 KiB Raw Blame History

1.6 KiB

Raw Blame History