team-sm

Track sprint progress and blockers across OpenSpec changes and GitHub issues.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/ConductionNL/decidesk --skill team-sm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-sm
Source: https://github.com/ConductionNL/decidesk/tree/main/.claude/skills/team-sm
Command: npx skills add https://github.com/ConductionNL/decidesk --skill team-sm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scrum teams often struggle with tracking sprint progress, surfacing blockers, and ensuring workflow compliance across multiple active changes. This Skill provides a structured way to monitor state, surface bottlenecks, and generate concise status updates.

Core Features & Use Cases

  • Progress tracking: monitor task status from plan.json and per-task checklists from tasks.md.
  • Blocker identification: detect blockers across OpenSpec changes and associated GitHub issues.
  • Workflow compliance: validate alignment between plan.json, tasks.md, and GitHub issue states, and flag inconsistencies.
  • Use Case: a Scrum Master reviewing a sprint can quickly surface overdue tasks, blocked work, and actions to unblock the team.

Quick Start

Provide a status snapshot for the current active change and point out top blockers with suggested actions.

Frequently Asked Questions about team-sm

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

FAQPage Schema
How do I track sprint progress and identify blockers across active changes?

Track sprint progress by reading plan.json and tasks.md to monitor task status, while validating state consistency with GitHub issues to automatically detect and flag blockers across active changes.

How does workflow compliance validation work for GitHub-backed Scrum projects?

Workflow compliance validation checks alignment between plan.json, tasks.md, and GitHub issue states, flagging inconsistencies to ensure your OpenSpec changes follow the intended Scrum workflow.

Can I use this to monitor OpenSpec changes and GitHub issues together?

Yes, you can monitor OpenSpec changes and GitHub issues together by validating state consistency across both platforms, reading plan data, and surfacing blocked work in a unified status snapshot.

What is the best way to surface overdue tasks and blocked work for a Scrum team?

The best way to surface overdue tasks is to generate a status snapshot that reads plan.json, assesses task checklists, and validates GitHub issue states to pinpoint bottlenecks with suggested unblocking actions.

Do I need plan.json and tasks.md files to track Scrum velocity and task status?

Yes, you need plan.json and tasks.md files because the Skill reads these formats to monitor task status, validate workflow compliance, and assess sprint progress alongside GitHub issue data.