@leeovery/claude-technical-workflows 2.0.18 → 2.0.19
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/package.json
CHANGED
|
@@ -37,15 +37,17 @@ Either way: Transform unvalidated reference material into a specification that's
|
|
|
37
37
|
|
|
38
38
|
## What You Do
|
|
39
39
|
|
|
40
|
-
1. **
|
|
40
|
+
1. **Extract exhaustively**: For each topic, re-scan ALL source material. Search for keywords and related terms. Information is often scattered - collect it all before synthesizing. Include only what we're building (not discarded alternatives).
|
|
41
41
|
|
|
42
|
-
2. **
|
|
42
|
+
2. **Filter**: Reference material may contain hallucinations, inaccuracies, or outdated concepts. Validate before including.
|
|
43
43
|
|
|
44
|
-
3. **
|
|
44
|
+
3. **Enrich**: Reference material may have gaps. Fill them through discussion.
|
|
45
45
|
|
|
46
|
-
4. **
|
|
46
|
+
4. **Present**: Synthesize and present content to the user in the format it would appear in the specification.
|
|
47
47
|
|
|
48
|
-
|
|
48
|
+
5. **Log**: Only when approved, write content verbatim to the specification.
|
|
49
|
+
|
|
50
|
+
The specification is the **golden document** - planning uses only this. If information doesn't make it into the specification, it won't be built. No references back to discussions or other source material.
|
|
49
51
|
|
|
50
52
|
## Critical Rules
|
|
51
53
|
|
|
@@ -33,8 +33,31 @@ Before starting any topic, identify ALL available reference material:
|
|
|
33
33
|
|
|
34
34
|
Work through the specification **topic by topic**:
|
|
35
35
|
|
|
36
|
-
### 1. Review
|
|
37
|
-
|
|
36
|
+
### 1. Review (Exhaustive Extraction)
|
|
37
|
+
|
|
38
|
+
**This step is critical. The specification is the golden document - if information doesn't make it here, it won't be built.**
|
|
39
|
+
|
|
40
|
+
For each topic or subtopic, perform exhaustive extraction:
|
|
41
|
+
|
|
42
|
+
1. **Re-scan ALL source material** - Don't rely on memory. Go back to the source material and systematically review it for the current topic.
|
|
43
|
+
|
|
44
|
+
2. **Search for keywords** - Topics are rarely contained in one section. Search for:
|
|
45
|
+
- The topic name and synonyms
|
|
46
|
+
- Related concepts and terms
|
|
47
|
+
- Names of systems, fields, or behaviors mentioned in context
|
|
48
|
+
|
|
49
|
+
3. **Collect scattered information** - Source material (research, discussions, requirements) is often non-linear. Information about a single topic may be scattered across:
|
|
50
|
+
- Multiple sections of the same document
|
|
51
|
+
- Different documents entirely
|
|
52
|
+
- Tangential discussions that revealed important details
|
|
53
|
+
|
|
54
|
+
4. **Filter for what we're building** - Include only validated decisions:
|
|
55
|
+
- Exclude discarded alternatives
|
|
56
|
+
- Exclude ideas that were explored but rejected
|
|
57
|
+
- Exclude "maybes" that weren't confirmed
|
|
58
|
+
- Include only what the user has decided to build
|
|
59
|
+
|
|
60
|
+
**Why this matters:** The specification is the single source of truth for planning. Planning will not reference discussions or research - only this document. Missing a detail here means that detail doesn't get implemented.
|
|
38
61
|
|
|
39
62
|
### 2. Synthesize and Present
|
|
40
63
|
Present your understanding to the user **in the format it would appear in the specification**:
|
|
@@ -98,6 +121,8 @@ Suggested skeleton:
|
|
|
98
121
|
|
|
99
122
|
## Critical Rules
|
|
100
123
|
|
|
124
|
+
**Exhaustive extraction is non-negotiable**: Before presenting any topic, re-scan source material. Search for keywords. Collect scattered information. The specification is the golden document - planning uses only this. If you miss something, it doesn't get built.
|
|
125
|
+
|
|
101
126
|
**Present before logging**: Never write content to the specification until the user has seen and approved it.
|
|
102
127
|
|
|
103
128
|
**Log verbatim**: When approved, write exactly what was presented - no silent modifications.
|