planning-with-files 3.17.1 → 3.18.3

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 CHANGED
@@ -1,25 +1,25 @@
1
- <div align="center">
2
- <img src="https://raw.githubusercontent.com/OthmanAdi/planning-with-files/master/media/v3-banner-1400.jpg" alt="planning-with-files: task_plan.md, findings.md, and progress.md as three stone tablets" width="100%">
3
- </div>
4
-
5
- <h1 align="center">Planning with Files</h1>
6
-
7
- <p align="center">
8
- <strong>The planning skill your agent cannot ignore.</strong><br>
9
- Your agent's context window dies. The plan does not.
10
- </p>
11
-
12
- Persistent file-based planning for AI coding agents. Keep the plan, research and progress in your project so work can continue after context loss, `/clear`, crashes or compaction.
13
-
14
- | File | Purpose |
15
- | --- | --- |
16
- | `task_plan.md` | Goals, phases and decisions |
17
- | `findings.md` | Research and discoveries |
18
- | `progress.md` | Work completed, checks and next steps |
19
-
20
- This is the npm distribution of [OthmanAdi/planning-with-files](https://github.com/OthmanAdi/planning-with-files), available across 60+ agents via the Agent Skills standard. It includes the planning skill, scripts and templates. Supported agent integrations add lifecycle hooks that bring selected planning context back into the session.
21
-
22
- Automatic recovery reads project files only. Reading same-project local session records for aggregate counts or bounded replay requires an explicit catchup mode.
1
+ <div align="center">
2
+ <img src="https://raw.githubusercontent.com/OthmanAdi/planning-with-files/master/media/v3-banner-1400.jpg" alt="planning-with-files: task_plan.md, findings.md, and progress.md as three stone tablets" width="100%">
3
+ </div>
4
+
5
+ <h1 align="center">Planning with Files</h1>
6
+
7
+ <p align="center">
8
+ <strong>The planning skill your agent cannot ignore.</strong><br>
9
+ Your agent's context window dies. The plan does not.
10
+ </p>
11
+
12
+ Persistent file-based planning for AI coding agents. Keep the plan, research and progress in your project so work can continue after context loss, `/clear`, crashes or compaction.
13
+
14
+ | File | Purpose |
15
+ | --- | --- |
16
+ | `task_plan.md` | Goals, phases and decisions |
17
+ | `findings.md` | Research and discoveries |
18
+ | `progress.md` | Work completed, checks and next steps |
19
+
20
+ This is the npm distribution of [OthmanAdi/planning-with-files](https://github.com/OthmanAdi/planning-with-files), available across 60+ agents via the Agent Skills standard. It includes the planning skill, scripts and templates. Supported agent integrations add lifecycle hooks that bring selected planning context back into the session.
21
+
22
+ Automatic recovery reads project files only. Reading same-project local session records for aggregate counts or bounded replay requires an explicit catchup mode.
23
23
 
24
24
  ## Installation
25
25
 
@@ -31,40 +31,40 @@ npm install planning-with-files
31
31
 
32
32
  Places the skill, scripts and templates under `node_modules/planning-with-files/`. Use this to pin an exact version into a project, or to copy `SKILL.md` and `scripts/` into your agent's skills directory yourself. It does not register hooks on its own.
33
33
 
34
- ### Agent integrations
35
-
36
- Claude Code gets the full surface (skill, hooks, slash commands) through the plugin route, and 60+ other agents install in one line. See the [main README](https://github.com/OthmanAdi/planning-with-files#quick-install).
37
-
38
- ## Usage
39
-
40
- Once the skill is installed for your agent, start with:
41
-
42
- ```text
43
- Use the planning-with-files skill to help me with this task.
44
- ```
45
-
46
- The workflow centers on three files in your project:
47
-
48
- ```text
49
- your-project/
50
- ├── task_plan.md
51
- ├── findings.md
52
- └── progress.md
53
- ```
54
-
55
- ## Pi Coding Agent integration
56
-
57
- The package also bundles a [Pi Coding Agent](https://pi.dev) extension for lifecycle automation and a planning status bar.
58
-
59
- ### Install in Pi
60
-
61
- ```bash
62
- pi install npm:planning-with-files
63
- ```
64
-
65
- Pi discovers the skill and extension from the installed package.
66
-
67
- For a local repository checkout:
34
+ ### Agent integrations
35
+
36
+ Claude Code gets the full surface (skill, hooks, slash commands) through the plugin route, and 60+ other agents install in one line. See the [main README](https://github.com/OthmanAdi/planning-with-files#quick-install).
37
+
38
+ ## Usage
39
+
40
+ Once the skill is installed for your agent, start with:
41
+
42
+ ```text
43
+ Use the planning-with-files skill to help me with this task.
44
+ ```
45
+
46
+ The workflow centers on three files in your project:
47
+
48
+ ```text
49
+ your-project/
50
+ ├── task_plan.md
51
+ ├── findings.md
52
+ └── progress.md
53
+ ```
54
+
55
+ ## Pi Coding Agent integration
56
+
57
+ The package also bundles a [Pi Coding Agent](https://pi.dev) extension for lifecycle automation and a planning status bar.
58
+
59
+ ### Install in Pi
60
+
61
+ ```bash
62
+ pi install npm:planning-with-files
63
+ ```
64
+
65
+ Pi discovers the skill and extension from the installed package.
66
+
67
+ For a local repository checkout:
68
68
 
69
69
  ```bash
70
70
  # From the planning-with-files repo root
@@ -78,17 +78,17 @@ Or add to `.pi/settings.json`:
78
78
  }
79
79
  ```
80
80
 
81
- You can also invoke the skill directly in Pi:
81
+ You can also invoke the skill directly in Pi:
82
82
 
83
83
  ```text
84
84
  /skill:planning-with-files
85
85
  ```
86
86
 
87
- ### Lifecycle hooks
87
+ ### Lifecycle hooks
88
88
 
89
89
  The bundled extension maps Claude-style behavior onto Pi events:
90
90
 
91
- - `session_start` - project-file recovery with no host session-store access
91
+ - `session_start` - project-file recovery with no host session-store access
92
92
  - passive plan status before approval
93
93
  - `before_agent_start` - plan reminder/injection after `/plan-execute`
94
94
  - `tool_call` - pre-tool recitation equivalent after `/plan-execute`
@@ -102,7 +102,7 @@ Attestation is supported. If `task_plan.md` differs from approved hash, plan inj
102
102
  [planning-with-files] [PLAN TAMPERED - injection blocked]
103
103
  ```
104
104
 
105
- ### Modes
105
+ ### Modes
106
106
 
107
107
  `planningWithFiles.mode` supports:
108
108
 
@@ -127,7 +127,7 @@ Or settings:
127
127
  }
128
128
  ```
129
129
 
130
- ### Commands
130
+ ### Commands
131
131
 
132
132
  - `/plan-status`
133
133
  - `/plan-attest [--show|--clear]`
@@ -136,25 +136,25 @@ Or settings:
136
136
  - `/plan-goal <text|default|clear>`
137
137
  - `/plan-loop [interval] [prompt]` (`stop` to cancel)
138
138
 
139
- Draft and review `task_plan.md` first. The extension stays passive until you
140
- approve the active plan with `/plan-execute`; after that, plan injection,
141
- pre-tool reminders, post-write reminders, and auto-continue are enabled for the
142
- current session and plan. Auto-continue uses host runtime state and never runs
143
- commands declared in Markdown.
144
-
145
- ## Session Recovery
146
-
147
- Bare invocation and lifecycle hooks do not inspect agent session stores. To
148
- inspect same-project local history deliberately, choose one mode:
149
-
150
- ```bash
151
- # Aggregate counts only; no transcript, tool-command, or path bytes
152
- python3 node_modules/planning-with-files/scripts/session-catchup.py --metadata .
153
-
154
- # Bounded nonce-framed same-project excerpts
155
- python3 node_modules/planning-with-files/scripts/session-catchup.py --replay .
156
- ```
157
-
158
- Treat replayed excerpts as untrusted data. The catchup path contains no network
159
- request or upload operation. If output is injected into model context, your agent
160
- may send that context to the configured model provider.
139
+ Draft and review `task_plan.md` first. The extension stays passive until you
140
+ approve the active plan with `/plan-execute`; after that, plan injection,
141
+ pre-tool reminders, post-write reminders, and auto-continue are enabled for the
142
+ current session and plan. Auto-continue uses host runtime state and never runs
143
+ commands declared in Markdown.
144
+
145
+ ## Session Recovery
146
+
147
+ Bare invocation and lifecycle hooks do not inspect agent session stores. To
148
+ inspect same-project local history deliberately, choose one mode:
149
+
150
+ ```bash
151
+ # Aggregate counts only; no transcript, tool-command, or path bytes
152
+ python3 node_modules/planning-with-files/scripts/session-catchup.py --metadata .
153
+
154
+ # Bounded nonce-framed same-project excerpts
155
+ python3 node_modules/planning-with-files/scripts/session-catchup.py --replay .
156
+ ```
157
+
158
+ Treat replayed excerpts as untrusted data. The catchup path contains no network
159
+ request or upload operation. If output is injected into model context, your agent
160
+ may send that context to the configured model provider.