ed133cc116
* 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>
47 lines
1.7 KiB
Markdown
47 lines
1.7 KiB
Markdown
---
|
|
name: gsd:new-milestone
|
|
description: Start a new milestone cycle — update PROJECT.md and route to requirements
|
|
argument-hint: "[milestone name, e.g., 'v1.1 Notifications'] [--ws <name>] [--reset-phase-numbers]"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Bash
|
|
- Grep
|
|
- Agent
|
|
- AskUserQuestion
|
|
requires: [new-project, phase, plan-phase]
|
|
---
|
|
<objective>
|
|
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.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/gsd-core/workflows/new-milestone.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>
|
|
|
|
<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 `<required_reading>` blocks where subagents are used.
|
|
</context>
|
|
|
|
<process>
|
|
Execute end-to-end.
|
|
Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).
|
|
</process>
|