@limina-labs/momentum 0.31.0 → 0.31.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +45 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,9 +1,11 @@
|
|
|
1
1
|
<div align="center">
|
|
2
2
|
<img src="site/src/assets/logo/wordmark.svg" width="280" alt="momentum" />
|
|
3
3
|
|
|
4
|
-
###
|
|
4
|
+
### The right context for your coding agent
|
|
5
5
|
|
|
6
|
-
|
|
6
|
+
momentum keeps your project's memory and state as Markdown files in the repo —
|
|
7
|
+
so every session your agent retrieves the right context, hallucinates less,
|
|
8
|
+
and turns a vague request into a well-grounded plan.
|
|
7
9
|
|
|
8
10
|
[](https://www.npmjs.com/package/@limina-labs/momentum)
|
|
9
11
|
[](LICENSE)
|
|
@@ -14,11 +16,24 @@
|
|
|
14
16
|
|
|
15
17
|
---
|
|
16
18
|
|
|
17
|
-
##
|
|
19
|
+
## Your agent doesn't need more context. It needs the right context.
|
|
18
20
|
|
|
19
|
-
**
|
|
21
|
+
**Without it, your agent guesses.** Ask an agent to fix a bug and it greps
|
|
22
|
+
around, fills the gaps with assumptions, and drafts a plan on shaky ground —
|
|
23
|
+
burning tokens rediscovering what your project already knew. And whatever it
|
|
24
|
+
does learn evaporates at the context limit or the next fresh session.
|
|
20
25
|
|
|
21
|
-
momentum
|
|
26
|
+
momentum hands the agent your project's real state up front. Phases, decisions,
|
|
27
|
+
history, and backlog live as plain Markdown files in the repo — read at the
|
|
28
|
+
start of every session, updated as the agent works — so it reasons from
|
|
29
|
+
recorded facts instead of guesses, and the *project* persists, not just
|
|
30
|
+
whatever one session shipped.
|
|
31
|
+
|
|
32
|
+
| Without momentum | With momentum |
|
|
33
|
+
| --- | --- |
|
|
34
|
+
| Greps the codebase, hopes it found the right files | Reads project state first — oriented in seconds |
|
|
35
|
+
| Fills the gaps with assumptions — hallucinates | Reasons from recorded decisions, not guesses |
|
|
36
|
+
| Plans on shaky ground, burns tokens rediscovering | Produces a well-grounded, actionable plan |
|
|
22
37
|
|
|
23
38
|
## Quick install
|
|
24
39
|
|
|
@@ -44,6 +59,31 @@ npx @limina-labs/momentum@latest init --agent antigravity # Antigravity
|
|
|
44
59
|
npx @limina-labs/momentum@latest init --ecosystem my-eco
|
|
45
60
|
```
|
|
46
61
|
|
|
62
|
+
## Better context in. Better work out.
|
|
63
|
+
|
|
64
|
+
- **Less hallucination** — the agent reasons from recorded facts (status,
|
|
65
|
+
decisions, history) instead of confident guesses. Fewer wrong turns, fewer
|
|
66
|
+
retries.
|
|
67
|
+
- **Higher-signal context** — the relevant history and prior decisions surface
|
|
68
|
+
first, not whatever a blind search returned. Less noise in the window, less
|
|
69
|
+
token waste.
|
|
70
|
+
- **Better-grounded plans** — a vague ask becomes a concrete plan: what to
|
|
71
|
+
change, where in the codebase, and how to verify it.
|
|
72
|
+
|
|
73
|
+
Based on hands-on use — momentum reduces guesswork and re-derivation. Your
|
|
74
|
+
mileage will vary by project and agent.
|
|
75
|
+
|
|
76
|
+
## The phase loop
|
|
77
|
+
|
|
78
|
+
Work happens in **phases** — one repeatable unit of work, five stages:
|
|
79
|
+
|
|
80
|
+
**Brainstorm → Plan → Execute → Verify → Release**
|
|
81
|
+
|
|
82
|
+
Your agent drives all of it: scopes through dialogue (disk writes gated until
|
|
83
|
+
you approve), plans groups + tasks + acceptance criteria, commits per group
|
|
84
|
+
with conventional commits, and marks tasks done only with passing evidence.
|
|
85
|
+
It stops at exactly one hard gate — the merge and release are yours to approve.
|
|
86
|
+
|
|
47
87
|
## How it works — no daemon, no lock-in
|
|
48
88
|
|
|
49
89
|
momentum isn't a framework or a background service. It's plain files and conventions your agent already knows how to read:
|
package/package.json
CHANGED