momentum

Explain momentum as accumulated effort carrying current action.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/wojons/je-ne-sais-quoi --skill momentum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: momentum
Source: https://github.com/wojons/je-ne-sais-quoi/tree/main/skills/momentum
Command: npx skills add https://github.com/wojons/je-ne-sais-quoi --skill momentum

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires je-ne-sais-quoi, and includes references (resource) and assets (resource) components.

What problem does it solve?

Momentum helps you respond to situations where progress feels heavier, breaks feel disproportionately costly, or continued effort suddenly stops carrying—so the AI can explain the lived experience, not just the mechanics.

Core Features & Use Cases

  • Felt vs. hollow explanations: contrasts mechanical, metrics-based reasoning with the visceral experience of being carried by accumulated effort.
  • Situation-based tests: uses real-world scenarios (streaks, paused teams, resumed practice, cold starts) to verify whether an answer understands momentum as weight and pull.
  • Failure mode patterning: identifies when explanations become correct-but-empty (e.g., procedural-memory talk) and redirects toward living, embodied framing.

Quick Start

Use the momentum skill to help the AI explain what changes when momentum breaks and restarting becomes harder, using lived-feeling language rather than process jargon.

Frequently Asked Questions about momentum

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

FAQPage Schema
What is the difference between a flow state and a cold start in habit practice?

This skill contrasts mechanical, metrics-based reasoning with the visceral experience of being carried by accumulated effort, helping the AI articulate why restarting feels heavier than starting fresh.

Why does restarting a paused team feel disproportionately harder than maintaining continuous progress?

You run scenario-driven tests using real-world situations like paused teams or resumed practice to verify the AI frames momentum as weight and pull, avoiding correct-but-empty procedural-memory explanations.

Can I use scenario-driven tests to evaluate cold starts and flow state entry?

Resuming a paused team feels disproportionately costly because momentum is a carried weight of accumulated effort; when it breaks, the visceral experience of that loss makes restarting feel heavier despite similar mechanical effort.

What is the restart cost when breaking a habit streak?

You should avoid process jargon when explanations become correct-but-empty, as procedural-memory talk fails to capture the living, embodied framing needed to explain the felt experience of momentum breaks and cold starts.