@leeovery/claude-technical-workflows 2.0.46 → 2.0.47

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,5 +1,5 @@
1
1
  ---
2
- description: Start a planning session from an existing specification. Discovers available specifications, asks where to store the plan, and invokes the technical-planning skill.
2
+ description: Start a planning session from an existing specification. Discovers available specifications, gathers context, and invokes the technical-planning skill.
3
3
  allowed-tools: Bash(.claude/scripts/discovery-for-planning.sh)
4
4
  ---
5
5
 
@@ -164,19 +164,7 @@ To proceed:
164
164
 
165
165
  ---
166
166
 
167
- ## Step 4: Choose Output Destination
168
-
169
- Ask: **Where should this plan live?**
170
-
171
- Load **[output-formats.md](../../skills/technical-planning/references/output-formats.md)** and present the available formats to help the user choose. Then load the corresponding output adapter for that format's setup requirements.
172
-
173
- **STOP.** Wait for user response.
174
-
175
- → Proceed to **Step 5**.
176
-
177
- ---
178
-
179
- ## Step 5: Gather Additional Context
167
+ ## Step 4: Gather Additional Context
180
168
 
181
169
  Ask:
182
170
  - Any additional context or priorities to consider?
@@ -184,11 +172,11 @@ Ask:
184
172
 
185
173
  **STOP.** Wait for user response.
186
174
 
187
- → Proceed to **Step 6**.
175
+ → Proceed to **Step 5**.
188
176
 
189
177
  ---
190
178
 
191
- ## Step 6: Surface Cross-Cutting Context
179
+ ## Step 5: Surface Cross-Cutting Context
192
180
 
193
181
  If any **concluded cross-cutting specifications** exist (from `specifications.crosscutting` in discovery), surface them as reference context for planning:
194
182
 
@@ -208,11 +196,11 @@ These specifications contain validated architectural decisions that should infor
208
196
 
209
197
  **If no cross-cutting specifications exist**: Skip this step.
210
198
 
211
- → Proceed to **Step 7**.
199
+ → Proceed to **Step 6**.
212
200
 
213
201
  ---
214
202
 
215
- ## Step 7: Invoke the Skill
203
+ ## Step 6: Invoke the Skill
216
204
 
217
205
  After completing the steps above, this command's purpose is fulfilled.
218
206
 
@@ -222,8 +210,7 @@ Invoke the [technical-planning](../../skills/technical-planning/SKILL.md) skill
222
210
  ```
223
211
  Planning session for: {topic}
224
212
  Specification: docs/workflow/specification/{topic}.md
225
- Output format: {format}
226
- Additional context: {summary of user's answers from Step 5}
213
+ Additional context: {summary of user's answers from Step 4}
227
214
  Cross-cutting references: {list of applicable cross-cutting specs with brief summaries, or "none"}
228
215
 
229
216
  Invoke the technical-planning skill.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@leeovery/claude-technical-workflows",
3
- "version": "2.0.46",
3
+ "version": "2.0.47",
4
4
  "description": "Technical workflow skills & commands for Claude Code",
5
5
  "license": "MIT",
6
6
  "author": "Lee Overy <me@leeovery.com>",