@leeovery/claude-technical-workflows 2.1.7 → 2.1.8
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
|
@@ -19,7 +19,7 @@ This is **Phase 1** of the six-phase workflow:
|
|
|
19
19
|
| 5. Implementation | DOING - tests first, then code | |
|
|
20
20
|
| 6. Review | VALIDATING - check work against artifacts | |
|
|
21
21
|
|
|
22
|
-
**Stay in your lane**: Explore freely. This is the time for broad thinking, feasibility checks, and learning.
|
|
22
|
+
**Stay in your lane**: Explore freely. This is the time for broad thinking, feasibility checks, and learning. Surface options and tradeoffs — don't make decisions. When a topic converges toward a conclusion, that's a signal it's ready for discussion phase, not a cue to start deciding. Park it and move on.
|
|
23
23
|
|
|
24
24
|
---
|
|
25
25
|
|
|
@@ -65,6 +65,57 @@ Don't constrain yourself. Research goes wherever it needs to go.
|
|
|
65
65
|
|
|
66
66
|
**Be honest**: If something seems flawed or risky, say so. Challenge assumptions.
|
|
67
67
|
|
|
68
|
+
**Explore, don't decide**: Your job is to surface options, tradeoffs, and understanding — not to pick winners. Synthesis is welcome ("the tradeoffs are X, Y, Z"), conclusions are not ("therefore we should do Y"). Decisions belong in the discussion phase.
|
|
69
|
+
|
|
70
|
+
## Convergence Awareness
|
|
71
|
+
|
|
72
|
+
Research threads naturally converge. As you explore a topic, options narrow, tradeoffs clarify, and opinions start forming. This is healthy — but it's also a signal.
|
|
73
|
+
|
|
74
|
+
### Recognizing convergence
|
|
75
|
+
|
|
76
|
+
Watch for these signs that a thread is moving from exploration toward decision-making:
|
|
77
|
+
|
|
78
|
+
- "We should..." or "The best approach is..." language (from you or the user)
|
|
79
|
+
- Options narrowing to a clear frontrunner with well-understood tradeoffs
|
|
80
|
+
- The same conclusion being reached from multiple angles
|
|
81
|
+
- Discussion shifting from "what are the options?" to "which option?"
|
|
82
|
+
- You or the user starting to advocate for a particular approach
|
|
83
|
+
|
|
84
|
+
### What to do
|
|
85
|
+
|
|
86
|
+
When you notice convergence, **flag it and give the user options**:
|
|
87
|
+
|
|
88
|
+
> "This thread seems to be converging — we've explored {topic} enough that the tradeoffs are clear and it's approaching decision territory.
|
|
89
|
+
>
|
|
90
|
+
> - **`p`/`park`** — Mark as discussion-ready and move to another topic
|
|
91
|
+
> - **`k`/`keep`** — Keep digging, there's more to understand
|
|
92
|
+
> - **`s`/`something else`** — Your call"
|
|
93
|
+
|
|
94
|
+
**Never decide for the user.** Even if the answer seems obvious, flag it and ask.
|
|
95
|
+
|
|
96
|
+
### If the user parks it
|
|
97
|
+
|
|
98
|
+
Document the convergence point in the research file using this marker:
|
|
99
|
+
|
|
100
|
+
```markdown
|
|
101
|
+
> **Discussion-ready**: {Brief summary of what was explored and why it's ready for decision-making. Key tradeoffs or options identified.}
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
Then continue with whatever's next — another topic, a different angle, or wrapping up the session.
|
|
105
|
+
|
|
106
|
+
### If the user keeps digging
|
|
107
|
+
|
|
108
|
+
Continue exploring. The convergence signal isn't a stop sign — it's an awareness check. The user might want to stress-test the emerging conclusion, explore edge cases, or understand the problem more deeply before moving on. That's valid research work.
|
|
109
|
+
|
|
110
|
+
### Synthesis vs decision
|
|
111
|
+
|
|
112
|
+
This distinction matters:
|
|
113
|
+
|
|
114
|
+
- **Synthesis** (research): "There are three viable approaches. A is simplest but limited. B scales better but costs more. C is future-proof but complex."
|
|
115
|
+
- **Decision** (discussion): "We should go with B because scaling matters more than simplicity for this project."
|
|
116
|
+
|
|
117
|
+
Synthesis is your job. Decisions are not. Present the landscape, don't pick the destination.
|
|
118
|
+
|
|
68
119
|
## Questioning
|
|
69
120
|
|
|
70
121
|
For structured questioning, use the interview reference (`references/interview.md`). Good research questions:
|