@leeovery/claude-technical-workflows 2.0.13 → 2.0.15
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.
|
@@ -36,8 +36,9 @@ Scan the codebase for research and discussions:
|
|
|
36
36
|
- If it exists, read it to get the stored checksum from the frontmatter
|
|
37
37
|
|
|
38
38
|
5. **Compute current research checksum** (if research files exist):
|
|
39
|
-
- Run: `cat
|
|
40
|
-
-
|
|
39
|
+
- Run exactly: `cat docs/workflow/research/*.md 2>/dev/null | md5sum | cut -d' ' -f1`
|
|
40
|
+
- IMPORTANT: Use this exact command - glob expansion is alphabetically sorted by default
|
|
41
|
+
- Do NOT modify or "simplify" this command - checksum must be deterministic
|
|
41
42
|
- Store this value to compare with the cached checksum
|
|
42
43
|
|
|
43
44
|
## Step 2: Present Workflow State and Options
|
|
@@ -72,6 +72,7 @@ How would you like to proceed?
|
|
|
72
72
|
1. **Implement all phases** - Work through the entire plan sequentially
|
|
73
73
|
2. **Implement specific phase** - Focus on one phase (e.g., "Phase 1")
|
|
74
74
|
3. **Implement specific task** - Focus on a single task
|
|
75
|
+
4. **Next available task** - Auto-discover the next unblocked task
|
|
75
76
|
|
|
76
77
|
Which approach?
|
|
77
78
|
```
|
|
@@ -87,7 +88,7 @@ Invoke the **technical-implementation** skill for this conversation.
|
|
|
87
88
|
Pass to the technical-implementation skill:
|
|
88
89
|
- Plan: `docs/workflow/planning/{topic}.md`
|
|
89
90
|
- Format: (from frontmatter)
|
|
90
|
-
- Scope: (all phases | specific phase | specific task)
|
|
91
|
+
- Scope: (all phases | specific phase | specific task | next-available)
|
|
91
92
|
- Environment setup: (completed | not needed)
|
|
92
93
|
|
|
93
94
|
**Example handoff:**
|