How does Momentum Keeper detect a project stall?

It monitors objective metrics like time since last task completion and subjective factors like developer energy levels to identify momentum loss early, typically within a 24-48 hour window.

What constitutes a 'quick win' in this framework?

A quick win is a clear, well-defined task that can be completed in 15-60 minutes, providing a tangible output and a psychological boost to tackle more complex work.

Is this skill useful for managing long-term projects?

Absolutely. It is specifically designed for complex, multi-week efforts where maintaining a sustainable pace and avoiding the 'final mile' stall is critical for completion.

Can it help when I'm stuck on a complex technical problem?

Yes, it uses the Resolve Blockers operation to categorize the issue and apply specific resolution patterns such as research-driven experimentation or architectural simplification.

Momentum Keeper

Name: Momentum Keeper
Author: adaptationio

byadaptationio

Productivity & Workflow

Sustains development progress and prevents project stagnation through systematic blocker resolution and energy management strategies.

About

Momentum Keeper is a specialized Claude Code skill designed to keep software projects moving forward by identifying and neutralizing factors that lead to development stalls. It provides a structured framework for early stall detection, systematic blocker resolution, and psychological momentum boosts via 'quick wins.' Whether you are facing complex technical obstacles, losing motivation on long-running tasks, or trying to resume work after a major interruption, this skill ensures continuous progress toward project completion by managing both technical output and developer energy.

Key Features

Early stall detection through objective progress metrics and subjective state assessment
Systematic resolution strategies for technical, decision, complexity, and dependency blockers
Context-resumption strategies to minimize friction when returning to a project after breaks
0 GitHub stars
Energy management techniques to maintain a sustainable development pace and prevent burnout
Identification of achievable 'quick wins' to provide psychological momentum and confidence

Use Cases

Breaking down an overwhelming, complex feature into small, achievable tasks to rebuild confidence
Recovering from a multi-day development stall where no meaningful code progress has been recorded
Regaining project context and focus efficiently after a long interruption or weekend break

About

Key Features

Early stall detection through objective progress metrics and subjective state assessment
Systematic resolution strategies for technical, decision, complexity, and dependency blockers
Context-resumption strategies to minimize friction when returning to a project after breaks
0 GitHub stars
Energy management techniques to maintain a sustainable development pace and prevent burnout
Identification of achievable 'quick wins' to provide psychological momentum and confidence

Use Cases

Breaking down an overwhelming, complex feature into small, achievable tasks to rebuild confidence
Recovering from a multi-day development stall where no meaningful code progress has been recorded
Regaining project context and focus efficiently after a long interruption or weekend break