sprint-deliverable-update

Draft and post per-deliverable sprint updates to deliverable issues.

Updated Oct 28, 2025
One-click install
npx skills add https://github.com/SnowboardTechie/dotfiles --skill sprint-deliverable-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-deliverable-update
Source: https://github.com/SnowboardTechie/dotfiles/tree/main/dot-config/opencode/skills/sprint-deliverable-update
Command: npx skills add https://github.com/SnowboardTechie/dotfiles --skill sprint-deliverable-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft or post a sprint update comment on a deliverable issue. Use when asked to "write the sprint update for [deliverable]", "post the update on #7309", or "draft the deliverable comment for this sprint."

Core Features & Use Cases

  • Per-deliverable update posts at the end of each sprint, enabling consistent status communication.
  • Reference to a separate project-level rollup that aggregates all per-deliverable updates into a board status update (sprint-status-update).

Quick Start

Draft or post a per-deliverable sprint update using the designated template for the current sprint.

Frequently Asked Questions about sprint-deliverable-update

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

FAQPage Schema
How do I draft a sprint update comment for a specific deliverable issue on GitHub?

To draft a sprint update comment for a deliverable issue, the Skill generates a standardized status update, including rollovers and risk notes, directly onto the GitHub issue.

What is the best way to post per-deliverable sprint status updates consistently?

Per-deliverable sprint status updates are drafted using a designated template to ensure consistent communication of progress, rollovers, and risk notes on individual issues.

Can I use this to write sprint updates for individual GitHub issues rather than the whole project?

Yes, this Skill is specifically designed to draft and post updates for individual deliverable issues across sprints, rather than generating a full project-level board status rollup.

Do I need a specific project structure to generate deliverable comments for sprints?

Yes, you need a SKILL.md file at the root directory with YAML frontmatter containing the name and description, while optional scripts, references, and assets directories can be loaded as needed.

How do rollups work with per-deliverable sprint updates?

Per-deliverable sprint updates are designed to be aggregated by a separate project-level rollup, which compiles all individual issue comments into a comprehensive board status update.

What should I include in a sprint deliverable update comment?

A sprint deliverable update comment should include the current status, notes on any rollovers, and identified risks, drafted from the designated template for the current sprint.