gsd:complete-milestone

Verify milestone completion, archive documents, and update project status records.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tDalile/dotfiles --skill gsd-complete-milestone-tdalile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd:complete-milestone
Source: https://github.com/tDalile/dotfiles/tree/main/agents/skills/gsd/commands/complete-milestone
Command: npx skills add https://github.com/tDalile/dotfiles --skill gsd-complete-milestone-tdalile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages the finalization of project milestones by verifying completion, archiving relevant documents, and updating project status to reflect progress and closure.

Core Features & Use Cases

  • Verification: Check deliverables and acceptance criteria to confirm milestone completion.
  • Archiving: Collect and archive milestone documents and artifacts to the project repository or archive storage.
  • Status Updates: Update project trackers and status fields to notify stakeholders and reflect closure.
  • Use Case: Close a release milestone after all tasks are done, archive release notes and artifacts, and mark the milestone as complete in the project board.

Quick Start

Complete the 'Q2 Launch' milestone by verifying all deliverables, archiving its documents, and updating the project status to completed.

Frequently Asked Questions about gsd:complete-milestone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify deliverables and archive documents when completing a project milestone?▼

To complete a project milestone, verify deliverables against acceptance criteria, archive associated documents to the project repository, and update project trackers to reflect closure. This ensures all milestone artifacts are stored and status records are current for stakeholders.

What is the best way to finalize an engineering sprint milestone and update project status?▼

Finalizing an engineering sprint milestone requires checking completion criteria, archiving release notes and artifacts, and updating the project board status. This workflow closes the sprint, archives essential documents, and notifies stakeholders of the milestone completion.

Can I use a milestone completion workflow for cross-team initiatives and product launches?▼

Yes, milestone completion workflows apply to cross-team initiatives and product launches. The process verifies readiness by checking deliverables, archives project documentation to a central repository, and updates status trackers to reflect overall project progress and closure.

Does archiving milestone documents update the project trackers automatically?▼

Archiving milestone documents involves collecting artifacts for the project repository, while status updates modify project trackers. Both actions are part of the milestone completion workflow, ensuring that archiving and status reflection are executed to notify stakeholders of closure.

What steps are needed to close a release milestone after all tasks are done?▼

Closing a release milestone requires verifying all task deliverables meet acceptance criteria, archiving release notes and artifacts to project storage, and marking the milestone as complete. This process updates project status records to reflect final closure.