skill-yesterday-ai-skills-forward-momentum · by Install
$ agentstack add skill-yesterday-ai-skills-forward-momentum ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-yesterday-ai-skills-forward-momentum) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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." 🦝
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Yesterday-AI
- Source: Yesterday-AI/skills
- License: MIT
- Homepage: https://github.com/Yesterday-AI/skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.