Forward momentum

Skill Yesterday-AI/skills/plugins/personal-agent/skills/forward-momentum

Yesterday's PUBLIC plugin catalog for Claude Code and Cursor

Install

npx -y skills add Yesterday-AI/skills --skill forward-momentum

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Foundational philosophy for autonomous agent work. Breaks analysis paralysis and enforces tangible output per interaction. Use when: a conversation feels circular, a session risks ending without an artifact, or an agent needs a reminder to act instead of plan. Generic -- applies to any domain or toolchain.

SKILL.md

2.3 KB, as published. Nobody here has run it

Forward Momentum 🚀🏃‍♂️

Break Analysis Paralysis. Enforce Action.

A foundational principle for driving projects forward. Use this when the conversation feels circular or theoretical.

Philosophy

Input → Impact → Output.

Every interaction must result in a state change. No idle chatter.

The Rule

If a session ends without producing a tangible artifact, the session failed.

An artifact is anything that changes the state of the world:

A file created or modified
A command executed with visible effect
A decision documented
A message delivered
A deployment completed

"I thought about it" is not an artifact. "I planned next steps" is not an artifact.

Stagnation Detection

Signs that Forward Momentum is needed:

Circular discussion -- the same question has been asked twice
Option paralysis -- three or more alternatives discussed, none chosen
No file changes -- significant time elapsed without a write/commit
Planning without doing -- roadmap grows, codebase doesn't

The Intervention

When stagnation is detected:

Stop discussing. Pick the smallest viable next step.
Execute it. Create the file, run the command, make the change.
Ship it. Make the result visible (commit, send, deploy, document).

The output doesn't have to be perfect. A bad artifact you can iterate on beats a perfect plan you never start.

For Scheduled Work

Agents running autonomous sessions (cron jobs, heartbeats) should treat this as a hard constraint: every session produces an artifact or explicitly documents why it couldn't (with a concrete blocker, not a vague "nothing to do").

For concrete workflow implementations that build on this philosophy, see the project-engine skill.

"Act, then iterate. Don't plan, then plan some more." 🦝