crewkit 1.1.0 → 1.1.2
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
|
@@ -52,16 +52,29 @@ Use **architect** with explorer findings. Must return:
|
|
|
52
52
|
|
|
53
53
|
**The architect must NOT produce the plan.** Only analysis and decisions.
|
|
54
54
|
|
|
55
|
-
### 3. Present decisions — MANDATORY PAUSE
|
|
55
|
+
### 3. Present decisions — MANDATORY PAUSE (one-by-one)
|
|
56
56
|
|
|
57
|
-
**DO NOT create the plan yet.**
|
|
58
|
-
- Each decision with options, pros/cons, recommendation
|
|
59
|
-
- Required vs compromise vs debt
|
|
60
|
-
- Task size and key risks
|
|
61
|
-
- Technical verdict
|
|
62
|
-
- Ask user to confirm or override each decision
|
|
57
|
+
**DO NOT create the plan yet.**
|
|
63
58
|
|
|
64
|
-
**
|
|
59
|
+
First, present a brief summary: task size, technical verdict, total number of decisions, and key risks. Then present decisions **one at a time**, waiting for user response before showing the next.
|
|
60
|
+
|
|
61
|
+
**For each decision:**
|
|
62
|
+
1. **Name the decision** clearly (e.g., "D1: How to store the onboarding flag")
|
|
63
|
+
2. **Explain what it solves** — 1-2 sentences so the user understands WHY this decision matters
|
|
64
|
+
3. **Present options as a table** with Pros and Cons columns
|
|
65
|
+
4. **Explain the practical difference** — not abstract architecture, but what concretely changes for the user/system with each option
|
|
66
|
+
5. **State your recommendation** with a clear prompt (e.g., "Go with A?")
|
|
67
|
+
6. **Wait for the user to respond** before presenting the next decision
|
|
68
|
+
|
|
69
|
+
**Rules:**
|
|
70
|
+
- ONE decision per message. Never batch multiple decisions.
|
|
71
|
+
- If the user agrees, confirm and move to the next immediately.
|
|
72
|
+
- If the user disagrees, acknowledge the override and record it. Then move to the next.
|
|
73
|
+
- If the user asks for more detail, explain further before asking again.
|
|
74
|
+
- After ALL decisions are confirmed, show a complete summary table.
|
|
75
|
+
- If scope is large, ask about scope reduction early (D1 or D2) since it affects all subsequent decisions.
|
|
76
|
+
|
|
77
|
+
**Wait for ALL decisions to be resolved before proceeding to step 4.**
|
|
65
78
|
|
|
66
79
|
### 4. Create plan file (after confirmation)
|
|
67
80
|
|