@linimin/pi-letscook 0.1.49 → 0.1.50
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 +6 -0
- package/README.md +18 -7
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,12 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
+
## 0.1.50
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
|
|
9
|
+
- simplified the README opening so people can tell at a glance whether this extension helps with their workflow, while preserving the existing `/cook` behavior and release-parity guidance
|
|
10
|
+
|
|
5
11
|
## 0.1.49
|
|
6
12
|
|
|
7
13
|
### Changed
|
package/README.md
CHANGED
|
@@ -1,17 +1,21 @@
|
|
|
1
1
|
# @linimin/pi-letscook
|
|
2
2
|
|
|
3
|
-
A Pi extension
|
|
3
|
+
A Pi extension for long-running repo work.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
It gives you `/cook`: a discussion-driven workflow command that keeps mission, progress, and verification in repo-local `.agent/**` state instead of chat memory.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
## Is this for you?
|
|
8
8
|
|
|
9
|
+
**Useful if your work needs to:**
|
|
9
10
|
- continue across sessions
|
|
10
11
|
- stay anchored to one mission
|
|
11
12
|
- resume from repo state instead of chat memory
|
|
12
13
|
- keep review, audit, and verification tied to the repo
|
|
13
14
|
|
|
14
|
-
|
|
15
|
+
**Probably overkill if you mostly do:**
|
|
16
|
+
- one-off chat tasks
|
|
17
|
+
- brainstorming
|
|
18
|
+
- planning docs without immediate implementation
|
|
15
19
|
|
|
16
20
|
## What you get
|
|
17
21
|
|
|
@@ -32,20 +36,27 @@ Then run `/reload` in Pi.
|
|
|
32
36
|
|
|
33
37
|
## Quick start
|
|
34
38
|
|
|
35
|
-
|
|
39
|
+
`/cook` supports both bare discussion-driven startup and optional inline intent hints.
|
|
36
40
|
|
|
37
41
|
```text
|
|
38
42
|
/cook
|
|
43
|
+
/cook login redirect
|
|
39
44
|
```
|
|
40
45
|
|
|
41
|
-
Use `/cook` after you discuss the mission in the main chat.
|
|
46
|
+
Use `/cook` after you discuss the mission in the main chat.
|
|
42
47
|
|
|
48
|
+
What it can do:
|
|
43
49
|
- start a brand-new workflow from recent discussion
|
|
44
50
|
- continue the current workflow when recent discussion still matches it, or when discussion is too weak or ambiguous to justify a refocus
|
|
45
51
|
- surface a conservative refocus chooser when recent discussion clearly points to a different workflow
|
|
46
52
|
- start the next workflow round after the previous one is `done`
|
|
47
53
|
|
|
48
|
-
|
|
54
|
+
What it expects:
|
|
55
|
+
- recent main-chat discussion about concrete repo changes
|
|
56
|
+
- README/CHANGELOG updates still count as concrete repo changes
|
|
57
|
+
- assistant-produced summaries and plan/spec/design-doc/proposal-only artifacts do not
|
|
58
|
+
|
|
59
|
+
`/cook <hint>` acts as a high-priority intent hint that helps proposal derivation interpret the recent discussion, but it still goes through the same fail-closed routing and approval-only Start/Cancel confirmation flow.
|
|
49
60
|
|
|
50
61
|
On startup and next-round flows, if recent discussion is missing, weak, ambiguous, assistant-produced, or only describes planning artifacts instead of concrete repo changes, `/cook` fails closed, leaves canonical `.agent/**` state unchanged, and tells you to clarify the mission in the main chat before rerunning `/cook`.
|
|
51
62
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@linimin/pi-letscook",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.50",
|
|
4
4
|
"description": "Pi package for long-running completion workflows with canonical .agent state, role-based subagents, continuity, and verification helpers.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"private": false,
|