msd-core/commands/gsd/complete-milestone.md at 4d92b3cddaf83fd7ac43b9d2b034de02d0661743

Files

Tim Willis 4d92b3cdda feat: add Claude Code marketplace plugin support

Add complete marketplace plugin configuration and documentation for GSD,
enabling installation via Claude Code's plugin marketplace.

Changes:
- Add .claude-plugin/marketplace.json and plugin.json manifests
- Add marketplace installation instructions to README.md
- Update all command files with marketplace tool permissions
- Add plugin conversion design and implementation documentation
- Update .gitignore for Claude Code plugin artifacts

Users can now install via:
  /plugin marketplace add glittercowboy/get-shit-done
  /plugin install get-shit-done@get-shit-done

2026-01-06 18:11:30 -06:00

2.9 KiB

Raw Blame History

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

type

name

description

argument-hint

allowed-tools

prompt

gsd:complete-milestone

Archive completed milestone and prepare for next version

Read

Write

Bash

Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md.

Purpose: Create historical record of shipped version, collapse completed work in roadmap, and prepare for next milestone. Output: Milestone archived, roadmap reorganized, git tagged.

<execution_context> Load these files NOW (before proceeding):

@~/.claude/get-shit-done/workflows/complete-milestone.md (main workflow)
@~/.claude/get-shit-done/templates/milestone-archive.md (archive template) </execution_context>

**Project files:** - `.planning/ROADMAP.md` - `.planning/STATE.md` - `.planning/PROJECT.md`

User input:

Version: {{version}} (e.g., "1.0", "1.1", "2.0")

Follow complete-milestone.md workflow:

Verify readiness:
- Check all phases in milestone have completed plans (SUMMARY.md exists)
- Present milestone scope and stats
- Wait for confirmation
Gather stats:
- Count phases, plans, tasks
- Calculate git range, file changes, LOC
- Extract timeline from git log
- Present summary, confirm
Extract accomplishments:
- Read all phase SUMMARY.md files in milestone range
- Extract 4-6 key accomplishments
- Present for approval
Archive milestone:
- Create .planning/milestones/v{{version}}-ROADMAP.md
- Extract full phase details from ROADMAP.md
- Fill milestone-archive.md template
- Update ROADMAP.md to one-line summary with link
- Offer to create next milestone
Update PROJECT.md:
- Add "Current State" section with shipped version
- Add "Next Milestone Goals" section
- Archive previous content in <details> (if v1.1+)
Commit and tag:
- Stage: MILESTONES.md, PROJECT.md, ROADMAP.md, STATE.md, archive file
- Commit: chore: archive v{{version}} milestone
- Tag: git tag -a v{{version}} -m "[milestone summary]"
- Ask about pushing tag
Offer next steps:
- Plan next milestone
- Archive planning
- Done for now

<success_criteria>

Milestone archived to .planning/milestones/v{{version}}-ROADMAP.md
ROADMAP.md collapsed to one-line entry
PROJECT.md updated with current state
Git tag v{{version}} created
Commit successful
User knows next steps </success_criteria>

<critical_rules>

Load workflow first: Read complete-milestone.md before executing
Verify completion: All phases must have SUMMARY.md files
User confirmation: Wait for approval at verification gates
Archive before collapsing: Always create archive file before updating ROADMAP.md
One-line summary: Collapsed milestone in ROADMAP.md should be single line with link
Context efficiency: Archive keeps ROADMAP.md constant size </critical_rules>

2.9 KiB Raw Blame History

2.9 KiB

Raw Blame History