msd-core/skills/gsd-milestone-summary/SKILL.md at 697cbb1f05b47a3ea2461ba1d98f0fecf7d1045e

Files

Tom Boucher da4a86d8c1 feat(#1596 ): ship GSD skills via .claude-plugin/plugin.json

Phase B-provide of epic #1258. Adds a build-generated skills/ dir +
a skills manifest field so plugin-installed GSD exposes gsd-core:<skill>
the native Claude Code way. Closes the gap where plugin-only installs
lacked the skill surface because bin/install.js never ran.

- scripts/gen-plugin-skills.cjs: build step converting commands/gsd/*.md
  to skills/gsd-<stem>/SKILL.md via convertClaudeCommandToClaudeSkill
- .claude-plugin/plugin.json: add "skills": "./skills/"
- package.json: add skills to files, gen:plugin-skills to build chain
- tests/issue-766-plugin-manifest.test.cjs: Section H conformance
  (manifest field + dir + frontmatter + count parity) + C2 skills symlink
- docs/adr/766-*.md: dated amendment adding skills surface row
- .changeset/rapid-bears-hum.md: type Added
- skills/: 69 generated gsd-<stem>/SKILL.md files (build-committed)

Closes #1596

2026-06-22 18:07:35 -04:00

1.8 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd-milestone-summary

Generate a comprehensive project summary from milestone artifacts for team onboarding and review

[version]

Read

Write

Bash

Grep

Glob

Generate a structured milestone summary for team onboarding and project review. Reads completed milestone artifacts (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION files) and produces a human-friendly overview of what was built, how, and why.

Purpose: Enable new team members to understand a completed project by reading one document and asking follow-up questions. Output: MILESTONE_SUMMARY written to .planning/reports/, presented inline, optional interactive Q&A.

<execution_context> @~/.claude/gsd-core/workflows/milestone-summary.md </execution_context>

**Project files:** - `.planning/ROADMAP.md` - `.planning/PROJECT.md` - `.planning/STATE.md` - `.planning/RETROSPECTIVE.md` - `.planning/milestones/v{version}-ROADMAP.md` (if archived) - `.planning/milestones/v{version}-REQUIREMENTS.md` (if archived) - `.planning/phases/*-*/` (SUMMARY.md, VERIFICATION.md, CONTEXT.md, RESEARCH.md)

User input:

Version: $ARGUMENTS (optional — defaults to current/latest milestone)

Execute end-to-end.

<success_criteria>

Milestone version resolved (from args, STATE.md, or archive scan)
All available artifacts read (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, RETROSPECTIVE)
Summary document written to .planning/reports/MILESTONE_SUMMARY-v{version}.md
All 7 sections generated (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started)
Summary presented inline to user
Interactive Q&A offered
STATE.md updated </success_criteria>

1.8 KiB Raw Blame History

1.8 KiB

Raw Blame History