gsd:reference:checkpoints

Organize GSD checkpoint documentation across waves, phases, milestones, and projects.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/cshyang/nochore --skill gsd-reference-checkpoints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd:reference:checkpoints
Source: https://github.com/cshyang/nochore/tree/main/capabilities/incubator/skills/gsd/references/checkpoints
Command: npx skills add https://github.com/cshyang/nochore --skill gsd-reference-checkpoints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organize and standardize GSD checkpoint documentation across waves, phases, milestones, and projects.

Core Features & Use Cases

  • Checkpoint types: wave, phase, milestone, project.
  • Contents guidance: completed work, pending work, blockers and risks, user decisions.
  • Best practices and usage scenarios for governance, reporting, and decision-making.

Quick Start

Plan your next checkpoint by selecting the appropriate checkpoint type and populating the recommended content.

Frequently Asked Questions about gsd:reference:checkpoints

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

FAQPage Schema
How do I standardize checkpoint documentation across project milestones?

Standardize checkpoint documentation by organizing progress, decisions, and risks into structured Markdown with frontmatter metadata. Use defined checkpoint types like wave, phase, milestone, and project to track governance and reporting consistently.

What should be included in project management checkpoint reports?

Checkpoint reports should include completed work, pending work, blockers and risks, and user decisions. Structuring these contents ensures project governance teams can effectively track progress and make informed decisions at each milestone.

When do I need to use different checkpoint types for project tracking?

Use different checkpoint types when tracking progress across varying scopes. Apply wave, phase, milestone, and project checkpoints to organize governance documentation, ensuring each level captures relevant decisions, risks, and completed work.

How do I write best practices for milestone documentation in GSD workflows?

Write best practices for milestone documentation by defining clear success criteria and standardizing frontmatter metadata. Apply these practices to governance, reporting, and decision-making scenarios to maintain consistent progress tracking.

Can I use structured Markdown for project governance decision tracking?

Yes, structured Markdown supports project governance decision tracking by combining frontmatter metadata with a readable body. This format standardizes checkpoint contents, enabling teams to review decisions, blockers, and risks effectively.