@pify/plan-mode 0.4.0 → 0.4.2
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 +3 -1
- package/package.json +2 -2
- package/skills/plan-mode/SKILL.md +3 -0
package/README.md
CHANGED
|
@@ -25,12 +25,14 @@ Part of the [Pify suite](https://github.com/pifydev). Install with [`pify instal
|
|
|
25
25
|
/plan add oauth login # enter + start planning this
|
|
26
26
|
/plan off # leave without approval
|
|
27
27
|
/plan list # saved plans in .pi/plans/ (v0.2)
|
|
28
|
-
|
|
28
|
+
/plan open oauth # reopen a saved plan by name or fragment (v0.4)
|
|
29
29
|
/plan steps # progress through the approved plan (v0.3)
|
|
30
30
|
/plan export [file] # standalone HTML next to the plan (v0.3)
|
|
31
31
|
pi --plan # start a session already in plan mode
|
|
32
32
|
```
|
|
33
33
|
|
|
34
|
+
**Reopening** (v0.4): `/plan open <file>` accepts a filename, a stem, or any distinctive fragment. It hands the plan text back to the agent as a hidden message and restarts step tracking by re-parsing the file — the file is the source of truth, not the step list it produced last time.
|
|
35
|
+
|
|
34
36
|
## Conflicts
|
|
35
37
|
|
|
36
38
|
`@pify/plan-mode` registers the `--plan` flag and `/plan` command, so it cannot run alongside `@narumitw/pi-plan-mode` or other plan extensions. Remove those first:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pify/plan-mode",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.2",
|
|
4
4
|
"description": "Read-only planning mode for pi with an explicit approve-then-execute gate: enforced tool policy, plan files, approach options, fresh-session handoff",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
@@ -56,7 +56,7 @@
|
|
|
56
56
|
}
|
|
57
57
|
},
|
|
58
58
|
"devDependencies": {
|
|
59
|
-
"@earendil-works/pi-coding-agent": "^0.
|
|
59
|
+
"@earendil-works/pi-coding-agent": "^0.85.1",
|
|
60
60
|
"@types/node": "^22.10.2",
|
|
61
61
|
"typebox": "^1.1.38",
|
|
62
62
|
"typescript": "^5.7.2"
|
|
@@ -30,6 +30,9 @@ Do not enter plan mode for trivial single-file edits.
|
|
|
30
30
|
1-3 alternative approaches, marking one "(Recommended)". The user approves
|
|
31
31
|
(here or in a fresh session), requests revisions, or discards.
|
|
32
32
|
6. After approval, implement the plan exactly; report any deviation.
|
|
33
|
+
An approved plan is frozen: do not quietly rewrite the plan file so it
|
|
34
|
+
matches what you ended up doing. Track progress with `plan_step_done`,
|
|
35
|
+
and if the plan turns out to be wrong, say so and re-plan in the open.
|
|
33
36
|
|
|
34
37
|
## While plan mode is active
|
|
35
38
|
|