speccrew 0.6.32 → 0.6.33
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.
|
@@ -164,6 +164,14 @@ When the task fails or is blocked, output:
|
|
|
164
164
|
|
|
165
165
|
## Constraints
|
|
166
166
|
|
|
167
|
+
**TECHNOLOGY STACK CONSTRAINTS:**
|
|
168
|
+
- Scripting languages ONLY: PowerShell (Windows) and Bash (Linux/Mac)
|
|
169
|
+
- Node.js permitted ONLY for existing project scripts (e.g., `node scripts/xxx.js`)
|
|
170
|
+
- FORBIDDEN: Python, Ruby, Perl, compiled languages, or any runtime requiring separate installation
|
|
171
|
+
- DO NOT create temporary .py, .rb, .pl files under any circumstances
|
|
172
|
+
- For JSON validation, use `node -e "JSON.parse(require('fs').readFileSync('file.json','utf8'))"` instead of Python
|
|
173
|
+
- For file processing, use PowerShell cmdlets (Get-Content, ConvertFrom-Json, Set-Content) or Bash built-ins
|
|
174
|
+
|
|
167
175
|
**MUST DO:**
|
|
168
176
|
- If `skill_name` is provided, MUST use Skill Discovery to resolve the full path and strictly follow the Skill definition
|
|
169
177
|
- If `skill_name` is provided but Skill file does not exist, immediately report error
|
|
@@ -379,6 +379,13 @@ When user reports problems ("something went wrong", "error occurred", "not worki
|
|
|
379
379
|
- Display pipeline status visually when WORKFLOW-PROGRESS.json exists
|
|
380
380
|
- Support both auto-orchestration mode (when user requests "auto") and manual mode
|
|
381
381
|
|
|
382
|
+
**Technology Stack Constraints:**
|
|
383
|
+
- Scripting: PowerShell and Bash only (zero Python dependency, zero external tools)
|
|
384
|
+
- Node.js: Permitted ONLY for existing project scripts (e.g., speccrew CLI, update-progress.js)
|
|
385
|
+
- FORBIDDEN: Python, Ruby, Perl, compiled languages, or any runtime not pre-installed
|
|
386
|
+
- When dispatching workers: ensure task descriptions explicitly state "use PowerShell/Bash only"
|
|
387
|
+
- For JSON operations: use `node -e` with inline JS, or PowerShell `ConvertFrom-Json` / `ConvertTo-Json`
|
|
388
|
+
|
|
382
389
|
**Must NOT Do:**
|
|
383
390
|
- Do not directly execute specific steps in Skill (must read Skill file first)
|
|
384
391
|
- Do not skip Skill and directly generate deliverables
|
|
@@ -107,6 +107,18 @@ Stage 4: System Summary
|
|
|
107
107
|
<field name="text">ONLY pause at explicit <event action="confirm"> blocks defined in the workflow</field>
|
|
108
108
|
</block>
|
|
109
109
|
|
|
110
|
+
<!-- ============================================================
|
|
111
|
+
Global Technology Stack Constraints
|
|
112
|
+
============================================================ -->
|
|
113
|
+
<block type="rule" id="GLOBAL-R-TECHSTACK" level="forbidden" desc="Technology stack constraints — NEVER violate">
|
|
114
|
+
<field name="text">FORBIDDEN: Python, Ruby, Perl, compiled binaries, or any runtime requiring separate installation</field>
|
|
115
|
+
<field name="text">PERMITTED scripting: PowerShell (Windows) and Bash (Linux/Mac) ONLY</field>
|
|
116
|
+
<field name="text">PERMITTED Node.js: ONLY for existing project scripts (e.g., node scripts/update-progress.js)</field>
|
|
117
|
+
<field name="text">For JSON validation use: node -e "JSON.parse(require('fs').readFileSync('file.json','utf8'))"</field>
|
|
118
|
+
<field name="text">For JSON creation use: node -e with inline script, or PowerShell ConvertTo-Json</field>
|
|
119
|
+
<field name="text">DO NOT create temporary .py, .rb, .pl, .bat files — use inline commands via run_in_terminal</field>
|
|
120
|
+
</block>
|
|
121
|
+
|
|
110
122
|
<!-- ============================================================
|
|
111
123
|
Stage 0: Platform Detection
|
|
112
124
|
============================================================ -->
|