@groeponline/pi-missions 0.3.14 → 0.3.15
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/CHANGELOG.md +4 -0
- package/README.md +29 -28
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -2,53 +2,36 @@
|
|
|
2
2
|
|
|
3
3
|
<img src="https://raw.githubusercontent.com/GroepOnline/pi-missions/main/docs/images/missions_banner.png" alt="Pi Missions" width="100%">
|
|
4
4
|
|
|
5
|
-
#
|
|
5
|
+
# Pi Missions
|
|
6
6
|
|
|
7
|
-
**
|
|
7
|
+
**Keep long-running coding work alive after the chat is gone.**
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
Turn a big implementation into a durable mission with ordered features, acceptance criteria, evidence and resumable state across Pi sessions.
|
|
10
10
|
|
|
11
11
|
[](https://www.npmjs.com/package/@groeponline/pi-missions) [](https://www.npmjs.com/package/@groeponline/pi-missions) [](https://github.com/GroepOnline/pi-missions/actions/workflows/ci.yml) [](https://pi.dev/packages/@groeponline/pi-missions) 
|
|
12
12
|
|
|
13
13
|
</div>
|
|
14
14
|
|
|
15
|
-
##
|
|
16
|
-
|
|
17
|
-
Agent sessions are temporary. Real implementation work is not.
|
|
18
|
-
|
|
19
|
-
Pi Missions gives a job a durable identity with a plan, ordered features, acceptance criteria, evidence, history and handoff state. The active session can end; the mission remains on disk and can be loaded again by Pi or another compatible worker.
|
|
20
|
-
|
|
21
|
-
Use it when a task is too large for one prompt, one context window or one uninterrupted coding session.
|
|
22
|
-
|
|
23
|
-
## Where it fits
|
|
24
|
-
|
|
25
|
-
Pi Missions owns **durable work state**: plans, features, evidence, history, recovery, and handoff context that must survive session boundaries. It does not replace Wishcraft's lightweight idea inbox and it does not execute multi-agent swarms itself.
|
|
26
|
-
|
|
27
|
-
`pi-wishcraft idea -> pi-missions mission -> pi-agent-orchestrator run` is the intended promotion path when a thought becomes durable work and then needs parallel or isolated execution.
|
|
28
|
-
|
|
29
|
-
- [`pi-wishcraft`](https://github.com/GroepOnline/pi-wishcraft): operator cockpit and fast idea capture.
|
|
30
|
-
- **pi-missions**: durable plan/task/evidence state.
|
|
31
|
-
- [`pi-agent-orchestrator`](https://github.com/GroepOnline/pi-agent-orchestrator): execution fabric for agents, worktrees, swarms, schedules, and handoffs.
|
|
32
|
-
|
|
33
|
-
GitHub, Slack and webhook integration classes remain lightweight scaffolding; production-readiness is tracked in [#13](https://github.com/GroepOnline/pi-missions/issues/13).
|
|
34
|
-
|
|
35
|
-
## 30-second start
|
|
15
|
+
## Start in 10 seconds
|
|
36
16
|
|
|
37
17
|
```bash
|
|
38
18
|
pi install npm:@groeponline/pi-missions
|
|
39
19
|
```
|
|
40
20
|
|
|
41
|
-
|
|
21
|
+
Then inside Pi:
|
|
42
22
|
|
|
43
23
|
```text
|
|
44
24
|
/mission start "Implement user auth"
|
|
45
|
-
/mission status
|
|
46
25
|
/mission next
|
|
47
|
-
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
When the feature is actually done:
|
|
29
|
+
|
|
30
|
+
```text
|
|
48
31
|
/mission done "Tests pass and login flow verified"
|
|
49
32
|
```
|
|
50
33
|
|
|
51
|
-
Resume
|
|
34
|
+
Close Pi. Come back later. Resume the same mission:
|
|
52
35
|
|
|
53
36
|
```text
|
|
54
37
|
/mission list
|
|
@@ -56,6 +39,24 @@ Resume later:
|
|
|
56
39
|
/mission status
|
|
57
40
|
```
|
|
58
41
|
|
|
42
|
+
## Why Pi Missions
|
|
43
|
+
|
|
44
|
+
Agent sessions are temporary. Real implementation work is not. Pi Missions stores the plan, current feature, acceptance criteria, evidence, history and handoff state on disk so progress survives restarts, compaction, forks and context loss.
|
|
45
|
+
|
|
46
|
+
Use it when a job is too large for one prompt, one context window or one uninterrupted coding session.
|
|
47
|
+
|
|
48
|
+
## Where it fits
|
|
49
|
+
|
|
50
|
+
Pi Missions owns **durable work state**. Wishcraft captures lightweight ideas; Missions turns serious work into a resumable track; Agent Orchestrator executes parallel or isolated work when that becomes useful.
|
|
51
|
+
|
|
52
|
+
`pi-wishcraft idea → pi-missions mission → pi-agent-orchestrator run`
|
|
53
|
+
|
|
54
|
+
- [`pi-wishcraft`](https://github.com/GroepOnline/pi-wishcraft): operator cockpit and fast idea capture.
|
|
55
|
+
- **pi-missions**: durable plan, queue, evidence and recovery state.
|
|
56
|
+
- [`pi-agent-orchestrator`](https://github.com/GroepOnline/pi-agent-orchestrator): agents, worktrees, swarms, schedules and execution handoffs.
|
|
57
|
+
|
|
58
|
+
GitHub, Slack and webhook integration classes remain lightweight scaffolding; production-readiness is tracked in [#13](https://github.com/GroepOnline/pi-missions/issues/13).
|
|
59
|
+
|
|
59
60
|
## Execution loop
|
|
60
61
|
|
|
61
62
|
```mermaid
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@groeponline/pi-missions",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.15",
|
|
4
4
|
"description": "Persistent mission orchestration for Pi: durable plans, task queues, evidence trails, SQLite state, resumable execution, and handoffs across agent sessions.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"private": false,
|