scrum-team-developer

Enforce TDD red/green/refactor cycles and update subtask status in scrum.ts.

3|1|Updated Feb 3, 2012
One-click install
npx skills add https://github.com/shishi/dotfiles --skill scrum-team-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scrum-team-developer
Source: https://github.com/shishi/dotfiles/tree/main/claude/skills/scrum-team-developer
Command: npx skills add https://github.com/shishi/dotfiles --skill scrum-team-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps AI developers adhere to TDD within Scrum, enabling reliable PBI execution, structured subtasks, and a clear Definition of Done.

Core Features & Use Cases

  • Execute a single PBI per Sprint using disciplined TDD practices.
  • Break PBIs into subtasks at sprint start and track progress via TDD phases.
  • Update subtask status immediately as tests pass to reflect real progress.
  • Align work with the project dashboard's sprint definitions of done.

Quick Start

Find the next pending subtask in the dashboard, update its status to red to start the TDD cycle, then proceed with /tdd:red, /tdd:green, and /tdd:refactor steps until completion. Update sprint status when all subtasks are completed.

Frequently Asked Questions about scrum-team-developer

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

FAQPage Schema
How do I enforce TDD within a Scrum sprint for AI development?

To enforce TDD within Scrum, execute a single PBI per sprint by breaking it into subtasks and tracking each through the red, green, and refactor cycle. Update subtask status immediately in scrum.ts as tests pass to reflect real progress.

What is the Definition of Done for a Scrum PBI using TDD?

The Definition of Done for a PBI requires all subtasks to complete the TDD red, green, and refactor cycle. Sprint status is updated only when all subtasks pass their tests and align with the project dashboard's sprint definitions.

How do I start the TDD cycle for a pending subtask in Scrum?

To start the TDD cycle, find the next pending subtask in the dashboard and update its status to red. Proceed with the /tdd:red, /tdd:green, and /tdd:refactor steps until the subtask is complete and its status is updated.

Can I manage multiple PBIs in a single sprint using this TDD workflow?

No, this workflow executes a single PBI per sprint to maintain disciplined TDD practices. You break the PBI into subtasks at sprint start and track progress strictly through TDD phases to satisfy the Definition of Done.

Why should I update subtask status immediately during TDD?

Updating subtask status immediately as tests pass reflects real progress within the sprint. It ensures the scrum.ts file accurately tracks the TDD red, green, and refactor phases and aligns with the dashboard's Definition of Done.

Does this Scrum workflow require a project dashboard?

Yes, a project dashboard is required to find pending subtasks, update their TDD status, and align work with the sprint Definition of Done. The dashboard drives the PBI workflow and tracks sprint completion.