Can this skill help prevent developer burnout?

Yes, by enforcing strict WIP limits (1-2 active tasks per person) and calculating realistic capacity based on historical data rather than wishful thinking.

What is the 4-Hour Rule included in this skill?

It is a best practice that mandates breaking any task larger than 4 hours into smaller sub-tasks, ensuring progress is visible daily and blockers are identified early.

How are project health indicators tracked?

The skill monitors 'zombie tasks' stuck in progress, velocity trends, and completion rates to provide early warnings before a project's health declines.

How does this skill help with project slowdowns?

It uses a tiered Velocity Assessment System to identify the severity of a stall and provides a step-by-step recovery workflow to simplify tasks and restore momentum.

Does this work for remote or asynchronous teams?

Absolutely. It includes structured communication patterns for async updates, daily standups, and accountability messages that keep distributed teams aligned.

Team Productivity & Velocity

Name: Team Productivity & Velocity
Author: LayerDynamics

byLayerDynamics

0•

Herramientas de Colaboración

Optimizes team performance through structured velocity tracking, sprint capacity planning, and sustainable workload management.

This skill transforms Claude into a project management coach, helping teams implement high-performance workflows via the Lore plugin framework. It provides a deterministic system for tracking project velocity, managing Work-in-Progress (WIP) limits, and identifying 'crash states' to prevent project stagnation. By automating capacity calculations and establishing consistent cadences for daily standups and sprint planning, it ensures sustainable developer productivity and transparent project health monitoring across the entire development lifecycle.

Características Principales

010 GitHub stars

02Automated reporting for daily standups, weekly retrospectives, and sprint reviews

03Structured task breakdown guidance using the 4-Hour Rule for better visibility

04Work-in-Progress (WIP) limit enforcement to minimize context switching costs

05Automated sprint capacity planning based on team size and meeting loads

06Velocity Assessment System to identify and recover from project momentum loss

Casos de Uso

01Planning realistic sprint workloads for engineering teams to prevent overcommitment

02Recovering a stalled development project using the tiered Velocity Recovery Workflow

03Balancing individual developer capacity and redistributing tasks to avoid bottlenecks

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add layerdynamics/lore team-productivity

For use in Claude.ai and ChatGPT

Características Principales

010 GitHub stars

02Automated reporting for daily standups, weekly retrospectives, and sprint reviews

03Structured task breakdown guidance using the 4-Hour Rule for better visibility

04Work-in-Progress (WIP) limit enforcement to minimize context switching costs

05Automated sprint capacity planning based on team size and meeting loads

06Velocity Assessment System to identify and recover from project momentum loss

Casos de Uso

01Planning realistic sprint workloads for engineering teams to prevent overcommitment

02Recovering a stalled development project using the tiered Velocity Recovery Workflow

03Balancing individual developer capacity and redistributing tasks to avoid bottlenecks