pan-wizard 3.14.0 → 3.15.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.
@@ -1,249 +1,249 @@
1
- # Continuation Format
2
-
3
- Standard format for presenting next steps after completing a command or workflow.
4
-
5
- ## Core Structure
6
-
7
- ```
8
- ---
9
-
10
- ## ▶ Next Up
11
-
12
- **{identifier}: {name}** — {one-line description}
13
-
14
- `{command to copy-paste}`
15
-
16
- <sub>`/clear` first → fresh context window</sub>
17
-
18
- ---
19
-
20
- **Also available:**
21
- - `{alternative option 1}` — description
22
- - `{alternative option 2}` — description
23
-
24
- ---
25
- ```
26
-
27
- ## Format Rules
28
-
29
- 1. **Always show what it is** — name + description, never just a command path
30
- 2. **Pull context from source** — roadmap.md for phases, plan.md `<objective>` for plans
31
- 3. **Command in inline code** — backticks, easy to copy-paste, renders as clickable link
32
- 4. **`/clear` explanation** — always include, keeps it concise but explains why
33
- 5. **"Also available" not "Other options"** — sounds more app-like
34
- 6. **Visual separators** — `---` above and below to make it stand out
35
-
36
- ## Variants
37
-
38
- ### Execute Next Plan
39
-
40
- ```
41
- ---
42
-
43
- ## ▶ Next Up
44
-
45
- **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
46
-
47
- `/pan:exec-phase 2`
48
-
49
- <sub>`/clear` first → fresh context window</sub>
50
-
51
- ---
52
-
53
- **Also available:**
54
- - Review plan before executing
55
- - `/pan:assumptions 2` — check assumptions
56
-
57
- ---
58
- ```
59
-
60
- ### Execute Final Plan in Phase
61
-
62
- Add note that this is the last plan and what comes after:
63
-
64
- ```
65
- ---
66
-
67
- ## ▶ Next Up
68
-
69
- **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
70
- <sub>Final plan in Phase 2</sub>
71
-
72
- `/pan:exec-phase 2`
73
-
74
- <sub>`/clear` first → fresh context window</sub>
75
-
76
- ---
77
-
78
- **After this completes:**
79
- - Phase 2 → Phase 3 transition
80
- - Next: **Phase 3: Core Features** — User dashboard and settings
81
-
82
- ---
83
- ```
84
-
85
- ### Plan a Phase
86
-
87
- ```
88
- ---
89
-
90
- ## ▶ Next Up
91
-
92
- **Phase 2: Authentication** — JWT login flow with refresh tokens
93
-
94
- `/pan:plan-phase 2`
95
-
96
- <sub>`/clear` first → fresh context window</sub>
97
-
98
- ---
99
-
100
- **Also available:**
101
- - `/pan:discuss-phase 2` — gather context first
102
- - `/pan:research-phase 2` — investigate unknowns
103
- - Review roadmap
104
-
105
- ---
106
- ```
107
-
108
- ### Phase Complete, Ready for Next
109
-
110
- Show completion status before next action:
111
-
112
- ```
113
- ---
114
-
115
- ## ✓ Phase 2 Complete
116
-
117
- 3/3 plans executed
118
-
119
- ## ▶ Next Up
120
-
121
- **Phase 3: Core Features** — User dashboard, settings, and data export
122
-
123
- `/pan:plan-phase 3`
124
-
125
- <sub>`/clear` first → fresh context window</sub>
126
-
127
- ---
128
-
129
- **Also available:**
130
- - `/pan:discuss-phase 3` — gather context first
131
- - `/pan:research-phase 3` — investigate unknowns
132
- - Review what Phase 2 built
133
-
134
- ---
135
- ```
136
-
137
- ### Multiple Equal Options
138
-
139
- When there's no clear primary action:
140
-
141
- ```
142
- ---
143
-
144
- ## ▶ Next Up
145
-
146
- **Phase 3: Core Features** — User dashboard, settings, and data export
147
-
148
- **To plan directly:** `/pan:plan-phase 3`
149
-
150
- **To discuss context first:** `/pan:discuss-phase 3`
151
-
152
- **To research unknowns:** `/pan:research-phase 3`
153
-
154
- <sub>`/clear` first → fresh context window</sub>
155
-
156
- ---
157
- ```
158
-
159
- ### Milestone Complete
160
-
161
- ```
162
- ---
163
-
164
- ## 🎉 Milestone v1.0 Complete
165
-
166
- All 4 phases shipped
167
-
168
- ## ▶ Next Up
169
-
170
- **Start v1.1** — questioning → research → requirements → roadmap
171
-
172
- `/pan:milestone-new`
173
-
174
- <sub>`/clear` first → fresh context window</sub>
175
-
176
- ---
177
- ```
178
-
179
- ## Pulling Context
180
-
181
- ### For phases (from roadmap.md):
182
-
183
- ```markdown
184
- ### Phase 2: Authentication
185
- **Goal**: JWT login flow with refresh tokens
186
- ```
187
-
188
- Extract: `**Phase 2: Authentication** — JWT login flow with refresh tokens`
189
-
190
- ### For plans (from roadmap.md):
191
-
192
- ```markdown
193
- Plans:
194
- - [ ] 02-03: Add refresh token rotation
195
- ```
196
-
197
- Or from plan.md `<objective>`:
198
-
199
- ```xml
200
- <objective>
201
- Add refresh token rotation with sliding expiry window.
202
-
203
- Purpose: Extend session lifetime without compromising security.
204
- </objective>
205
- ```
206
-
207
- Extract: `**02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry`
208
-
209
- ## Anti-Patterns
210
-
211
- ### Don't: Command-only (no context)
212
-
213
- ```
214
- ## To Continue
215
-
216
- Run `/clear`, then paste:
217
- /pan:exec-phase 2
218
- ```
219
-
220
- User has no idea what 02-03 is about.
221
-
222
- ### Don't: Missing /clear explanation
223
-
224
- ```
225
- `/pan:plan-phase 3`
226
-
227
- Run /clear first.
228
- ```
229
-
230
- Doesn't explain why. User might skip it.
231
-
232
- ### Don't: "Other options" language
233
-
234
- ```
235
- Other options:
236
- - Review roadmap
237
- ```
238
-
239
- Sounds like an afterthought. Use "Also available:" instead.
240
-
241
- ### Don't: Fenced code blocks for commands
242
-
243
- ```
244
- ```
245
- /pan:plan-phase 3
246
- ```
247
- ```
248
-
249
- Fenced blocks inside templates create nesting ambiguity. Use inline backticks instead.
1
+ # Continuation Format
2
+
3
+ Standard format for presenting next steps after completing a command or workflow.
4
+
5
+ ## Core Structure
6
+
7
+ ```
8
+ ---
9
+
10
+ ## ▶ Next Up
11
+
12
+ **{identifier}: {name}** — {one-line description}
13
+
14
+ `{command to copy-paste}`
15
+
16
+ <sub>`/clear` first → fresh context window</sub>
17
+
18
+ ---
19
+
20
+ **Also available:**
21
+ - `{alternative option 1}` — description
22
+ - `{alternative option 2}` — description
23
+
24
+ ---
25
+ ```
26
+
27
+ ## Format Rules
28
+
29
+ 1. **Always show what it is** — name + description, never just a command path
30
+ 2. **Pull context from source** — roadmap.md for phases, plan.md `<objective>` for plans
31
+ 3. **Command in inline code** — backticks, easy to copy-paste, renders as clickable link
32
+ 4. **`/clear` explanation** — always include, keeps it concise but explains why
33
+ 5. **"Also available" not "Other options"** — sounds more app-like
34
+ 6. **Visual separators** — `---` above and below to make it stand out
35
+
36
+ ## Variants
37
+
38
+ ### Execute Next Plan
39
+
40
+ ```
41
+ ---
42
+
43
+ ## ▶ Next Up
44
+
45
+ **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
46
+
47
+ `/pan:exec-phase 2`
48
+
49
+ <sub>`/clear` first → fresh context window</sub>
50
+
51
+ ---
52
+
53
+ **Also available:**
54
+ - Review plan before executing
55
+ - `/pan:assumptions 2` — check assumptions
56
+
57
+ ---
58
+ ```
59
+
60
+ ### Execute Final Plan in Phase
61
+
62
+ Add note that this is the last plan and what comes after:
63
+
64
+ ```
65
+ ---
66
+
67
+ ## ▶ Next Up
68
+
69
+ **02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry
70
+ <sub>Final plan in Phase 2</sub>
71
+
72
+ `/pan:exec-phase 2`
73
+
74
+ <sub>`/clear` first → fresh context window</sub>
75
+
76
+ ---
77
+
78
+ **After this completes:**
79
+ - Phase 2 → Phase 3 transition
80
+ - Next: **Phase 3: Core Features** — User dashboard and settings
81
+
82
+ ---
83
+ ```
84
+
85
+ ### Plan a Phase
86
+
87
+ ```
88
+ ---
89
+
90
+ ## ▶ Next Up
91
+
92
+ **Phase 2: Authentication** — JWT login flow with refresh tokens
93
+
94
+ `/pan:plan-phase 2`
95
+
96
+ <sub>`/clear` first → fresh context window</sub>
97
+
98
+ ---
99
+
100
+ **Also available:**
101
+ - `/pan:discuss-phase 2` — gather context first
102
+ - `/pan:research-phase 2` — investigate unknowns
103
+ - Review roadmap
104
+
105
+ ---
106
+ ```
107
+
108
+ ### Phase Complete, Ready for Next
109
+
110
+ Show completion status before next action:
111
+
112
+ ```
113
+ ---
114
+
115
+ ## ✓ Phase 2 Complete
116
+
117
+ 3/3 plans executed
118
+
119
+ ## ▶ Next Up
120
+
121
+ **Phase 3: Core Features** — User dashboard, settings, and data export
122
+
123
+ `/pan:plan-phase 3`
124
+
125
+ <sub>`/clear` first → fresh context window</sub>
126
+
127
+ ---
128
+
129
+ **Also available:**
130
+ - `/pan:discuss-phase 3` — gather context first
131
+ - `/pan:research-phase 3` — investigate unknowns
132
+ - Review what Phase 2 built
133
+
134
+ ---
135
+ ```
136
+
137
+ ### Multiple Equal Options
138
+
139
+ When there's no clear primary action:
140
+
141
+ ```
142
+ ---
143
+
144
+ ## ▶ Next Up
145
+
146
+ **Phase 3: Core Features** — User dashboard, settings, and data export
147
+
148
+ **To plan directly:** `/pan:plan-phase 3`
149
+
150
+ **To discuss context first:** `/pan:discuss-phase 3`
151
+
152
+ **To research unknowns:** `/pan:research-phase 3`
153
+
154
+ <sub>`/clear` first → fresh context window</sub>
155
+
156
+ ---
157
+ ```
158
+
159
+ ### Milestone Complete
160
+
161
+ ```
162
+ ---
163
+
164
+ ## 🎉 Milestone v1.0 Complete
165
+
166
+ All 4 phases shipped
167
+
168
+ ## ▶ Next Up
169
+
170
+ **Start v1.1** — questioning → research → requirements → roadmap
171
+
172
+ `/pan:milestone-new`
173
+
174
+ <sub>`/clear` first → fresh context window</sub>
175
+
176
+ ---
177
+ ```
178
+
179
+ ## Pulling Context
180
+
181
+ ### For phases (from roadmap.md):
182
+
183
+ ```markdown
184
+ ### Phase 2: Authentication
185
+ **Goal**: JWT login flow with refresh tokens
186
+ ```
187
+
188
+ Extract: `**Phase 2: Authentication** — JWT login flow with refresh tokens`
189
+
190
+ ### For plans (from roadmap.md):
191
+
192
+ ```markdown
193
+ Plans:
194
+ - [ ] 02-03: Add refresh token rotation
195
+ ```
196
+
197
+ Or from plan.md `<objective>`:
198
+
199
+ ```xml
200
+ <objective>
201
+ Add refresh token rotation with sliding expiry window.
202
+
203
+ Purpose: Extend session lifetime without compromising security.
204
+ </objective>
205
+ ```
206
+
207
+ Extract: `**02-03: Refresh Token Rotation** — Add /api/auth/refresh with sliding expiry`
208
+
209
+ ## Anti-Patterns
210
+
211
+ ### Don't: Command-only (no context)
212
+
213
+ ```
214
+ ## To Continue
215
+
216
+ Run `/clear`, then paste:
217
+ /pan:exec-phase 2
218
+ ```
219
+
220
+ User has no idea what 02-03 is about.
221
+
222
+ ### Don't: Missing /clear explanation
223
+
224
+ ```
225
+ `/pan:plan-phase 3`
226
+
227
+ Run /clear first.
228
+ ```
229
+
230
+ Doesn't explain why. User might skip it.
231
+
232
+ ### Don't: "Other options" language
233
+
234
+ ```
235
+ Other options:
236
+ - Review roadmap
237
+ ```
238
+
239
+ Sounds like an afterthought. Use "Also available:" instead.
240
+
241
+ ### Don't: Fenced code blocks for commands
242
+
243
+ ```
244
+ ```
245
+ /pan:plan-phase 3
246
+ ```
247
+ ```
248
+
249
+ Fenced blocks inside templates create nesting ambiguity. Use inline backticks instead.