@leeovery/claude-technical-workflows 2.0.28 → 2.0.30

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
@@ -183,7 +183,7 @@ When using the full workflow, it progresses through six distinct phases:
183
183
 
184
184
  **Phase 2 - Discussion:** Captures the back-and-forth exploration of a problem. Documents competing solutions, why certain approaches won or lost, edge cases discovered, and the journey to decisions, not just the decisions themselves.
185
185
 
186
- **Phase 3 - Specification:** Transforms discussion documentation into a validated, standalone specification. Filters hallucinations and inaccuracies, enriches gaps through discussion, and builds a document that planning can execute against without referencing other sources.
186
+ **Phase 3 - Specification:** Transforms discussion(s) into validated, standalone specifications. Automatically analyses multiple discussions for natural groupings, filters hallucinations and inaccuracies, enriches gaps, and builds documents that planning can execute against without referencing other sources.
187
187
 
188
188
  **Phase 4 - Planning:** Converts specifications into actionable implementation plans with phases, tasks, and acceptance criteria. Supports multiple output formats (local markdown, Linear, Backlog.md).
189
189
 
@@ -225,19 +225,23 @@ skills/ # Input-agnostic processors
225
225
  └── technical-review/ # Validate against artefacts
226
226
 
227
227
  commands/ # Input layer (gather context → invoke skills)
228
- ├── workflow:start-research.md # Sequential: begin research
229
- ├── workflow:start-discussion.md # Sequential: begin discussions
230
- ├── workflow:start-specification.md # Sequential: begin specification
231
- ├── workflow:start-planning.md # Sequential: begin planning
232
- ├── workflow:start-implementation.md # Sequential: begin implementation
233
- ├── workflow:start-review.md # Sequential: begin review
234
- ├── workflow:status.md # Utility: show workflow status and next steps
235
- ├── workflow:view-plan.md # Utility: view plan tasks and progress
236
228
  ├── start-feature.md # Standalone: spec from inline context
237
- └── link-dependencies.md # Standalone: wire cross-topic deps
229
+ ├── link-dependencies.md # Standalone: wire cross-topic deps
230
+ └── workflow/ # Sequential workflow commands
231
+ ├── start-research.md # Begin research
232
+ ├── start-discussion.md # Begin discussions
233
+ ├── start-specification.md # Begin specification
234
+ ├── start-planning.md # Begin planning
235
+ ├── start-implementation.md # Begin implementation
236
+ ├── start-review.md # Begin review
237
+ ├── status.md # Show workflow status
238
+ └── view-plan.md # View plan tasks
238
239
 
239
240
  agents/
240
241
  └── chain-verifier.md # Parallel task verification for review
242
+
243
+ scripts/ # Helper scripts for commands
244
+ └── specification-discovery.sh # Discovery for specification command
241
245
  ```
242
246
 
243
247
  ## Skills
@@ -263,12 +267,12 @@ Sequential commands prefixed with `workflow:`. They expect files from previous p
263
267
 
264
268
  | Command | Description |
265
269
  |--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
266
- | [**/workflow:start-research**](commands/workflow:start-research.md) | Begin research exploration. For early-stage ideas, feasibility checks, and broad exploration before formal discussion. |
267
- | [**/workflow:start-discussion**](commands/workflow:start-discussion.md) | Begin a new technical discussion. Gathers topic, context, background information, and relevant codebase areas before starting documentation. |
268
- | [**/workflow:start-specification**](commands/workflow:start-specification.md) | Start a specification session from an existing discussion. Validates and refines discussion content into a standalone specification. |
269
- | [**/workflow:start-planning**](commands/workflow:start-planning.md) | Start a planning session from an existing specification. Creates implementation plans with phases, tasks, and acceptance criteria. Supports multiple output formats (markdown, Linear, Backlog.md, Beads). |
270
- | [**/workflow:start-implementation**](commands/workflow:start-implementation.md) | Start implementing a plan. Executes tasks via strict TDD, committing after each passing test. |
271
- | [**/workflow:start-review**](commands/workflow:start-review.md) | Start reviewing completed work. Validates implementation against plan tasks and acceptance criteria. |
270
+ | [**/workflow:start-research**](commands/workflow/start-research.md) | Begin research exploration. For early-stage ideas, feasibility checks, and broad exploration before formal discussion. |
271
+ | [**/workflow:start-discussion**](commands/workflow/start-discussion.md) | Begin a new technical discussion. Gathers topic, context, background information, and relevant codebase areas before starting documentation. |
272
+ | [**/workflow:start-specification**](commands/workflow/start-specification.md) | Start a specification session from existing discussion(s). Automatically analyses multiple discussions for natural groupings and consolidates them into unified specifications. |
273
+ | [**/workflow:start-planning**](commands/workflow/start-planning.md) | Start a planning session from an existing specification. Creates implementation plans with phases, tasks, and acceptance criteria. Supports multiple output formats (markdown, Linear, Backlog.md, Beads). |
274
+ | [**/workflow:start-implementation**](commands/workflow/start-implementation.md) | Start implementing a plan. Executes tasks via strict TDD, committing after each passing test. |
275
+ | [**/workflow:start-review**](commands/workflow/start-review.md) | Start reviewing completed work. Validates implementation against plan tasks and acceptance criteria. |
272
276
 
273
277
  ### Utility Commands
274
278
 
@@ -276,8 +280,8 @@ Helpers for navigating and understanding the workflow.
276
280
 
277
281
  | Command | Description |
278
282
  |--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
279
- | [**/workflow:status**](commands/workflow:status.md) | Show workflow status - what topics exist at each phase, and suggested next steps. |
280
- | [**/workflow:view-plan**](commands/workflow:view-plan.md) | View a plan's tasks and progress, regardless of output format. |
283
+ | [**/workflow:status**](commands/workflow/status.md) | Show workflow status - what topics exist at each phase, and suggested next steps. |
284
+ | [**/workflow:view-plan**](commands/workflow/view-plan.md) | View a plan's tasks and progress, regardless of output format. |
281
285
 
282
286
  ### Standalone Commands
283
287
 
@@ -296,7 +296,7 @@ Wait for response before proceeding.
296
296
 
297
297
  After completing the steps above, this command's purpose is fulfilled.
298
298
 
299
- Invoke the [technical-discussion](../skills/technical-discussion/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
299
+ Invoke the [technical-discussion](../../skills/technical-discussion/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
300
300
 
301
301
  **Example handoff (from research):**
302
302
  ```
@@ -70,7 +70,7 @@ Which plan would you like to implement?
70
70
 
71
71
  **This step is a gate.** Implementation cannot proceed if dependencies are not satisfied.
72
72
 
73
- See **[dependencies.md](../skills/technical-planning/references/dependencies.md)** for dependency format and states.
73
+ See **[dependencies.md](../../skills/technical-planning/references/dependencies.md)** for dependency format and states.
74
74
 
75
75
  After the user selects a plan:
76
76
 
@@ -161,7 +161,7 @@ If they choose a specific phase or task, ask them to specify which one.
161
161
 
162
162
  After completing the steps above, this command's purpose is fulfilled.
163
163
 
164
- Invoke the [technical-implementation](../skills/technical-implementation/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
164
+ Invoke the [technical-implementation](../../skills/technical-implementation/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
165
165
 
166
166
  **Example handoff:**
167
167
  ```
@@ -94,7 +94,7 @@ Ask: **Which feature specification would you like to plan?**
94
94
 
95
95
  Ask: **Where should this plan live?**
96
96
 
97
- 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.
97
+ 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.
98
98
 
99
99
  ## Step 5: Gather Additional Context
100
100
 
@@ -125,7 +125,7 @@ These specifications contain validated architectural decisions that should infor
125
125
 
126
126
  After completing the steps above, this command's purpose is fulfilled.
127
127
 
128
- Invoke the [technical-planning](../skills/technical-planning/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
128
+ Invoke the [technical-planning](../../skills/technical-planning/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
129
129
 
130
130
  **Example handoff:**
131
131
  ```
@@ -43,4 +43,4 @@ Ask these questions clearly and wait for responses before proceeding.
43
43
 
44
44
  After completing the steps above, this command's purpose is fulfilled.
45
45
 
46
- Invoke the [technical-research](../skills/technical-research/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
46
+ Invoke the [technical-research](../../skills/technical-research/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
@@ -90,7 +90,7 @@ Check if a specification exists:
90
90
 
91
91
  After completing the steps above, this command's purpose is fulfilled.
92
92
 
93
- Invoke the [technical-review](../skills/technical-review/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
93
+ Invoke the [technical-review](../../skills/technical-review/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
94
94
 
95
95
  **Example handoff:**
96
96
  ```