speccrew 0.6.1 → 0.6.3

package/.speccrew/agents/speccrew-system-developer.md

@@ -443,6 +443,24 @@ All development outputs MUST go under `iterations/{iter}/04.development/`.
 
 **FORBIDDEN directory names**: `04.dev-report/`, `04.dev-reports/`, `04.implementation/`, or any other variant.
 
+#### Helper Scripts Constraint
+
+All temporary/helper scripts generated during development MUST be placed under:
+```
+04.development/{platform_id}/scripts/
+```
+
+This includes but is not limited to:
+- Data initialization scripts
+- Local validation/verification scripts
+- Environment setup scripts
+- Build helper scripts
+- Test data generation scripts
+
+Scripts that are part of the application source code (e.g., database migrations, seed scripts) should go to the project source directory as specified in conventions-data.md, NOT to this scripts directory.
+
+Each Worker MUST list all generated scripts in their Task Record under a "Generated Scripts" section.
+
 > ⛔ **NO DIRECT CODING**: System Developer MUST NOT use file creation/editing tools to write application code. Every module implementation MUST be dispatched to a `speccrew-task-worker` agent running a dev skill (speccrew-dev-backend/frontend/mobile/desktop). System Developer's role in this phase is EXCLUSIVELY: task list creation, worker dispatch, progress tracking, and review coordination.
 
 > **IMPORTANT**: Dispatch `speccrew-task-worker` agents (via Agent tool) for parallel module development. Do NOT call dev skills directly — each module MUST run in an independent Worker Agent for progress visibility and error isolation.

package/.speccrew/skills/speccrew-dev-backend/SKILL.md

@@ -201,6 +201,17 @@ If accepting suboptimal solutions, write to tech-debt directory:
 
 Use the unified tech_debt document template defined in the workspace document templates configuration.
 
+#### Helper Scripts Output
+
+All temporary/helper scripts (validation, data init, environment setup, etc.) MUST be saved to:
+```
+iterations/{iter}/04.development/{platform_id}/scripts/
+```
+
+**Exception**: Application source scripts (migrations, seeds) go to the project source directory per conventions-data.md.
+
+Include all generated scripts in the Task Record "Generated Scripts" section with path and purpose.
+
 ## Step 9: Completion Notification
 
 When all tasks complete, update task record and notify user:

package/.speccrew/skills/speccrew-dev-frontend/SKILL.md

@@ -206,6 +206,17 @@ Tech Debt: {count}
 Task Record: speccrew-workspace/iterations/{number}-{type}-{name}/04.development/{platform_id}/{feature-name}-tasks.md
 ```
 
+#### Helper Scripts Output
+
+All temporary/helper scripts (validation, data init, environment setup, mock data, etc.) MUST be saved to:
+```
+iterations/{iter}/04.development/{platform_id}/scripts/
+```
+
+**Exception**: Application source scripts (build configs, etc.) go to the project source directory per conventions-dev.md.
+
+Include all generated scripts in the Task Record "Generated Scripts" section with path and purpose.
+
 ## Task Completion Report
 
 At the end of Step 6 (or if the skill fails at any point), output a structured Task Completion Report:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "speccrew",
-  "version": "0.6.1",
+  "version": "0.6.3",
   "description": "Spec-Driven Development toolkit for AI-powered IDEs",
   "author": "charlesmu99",
   "repository": {

package/workspace-template/docs/solutions/workspace-structure.md

@@ -113,6 +113,7 @@ iterations/
 ├── .checkpoints.json                  # Stage progress checkpoints
 ├── DISPATCH-PROGRESS.json             # Task dispatch and execution tracking
 ├── {platform_id}/                     # Grouped by platform (e.g., backend-spring, web-vue)
+│   ├── scripts/                       # Helper scripts generated during development
 │   ├── {module}-task.md               # Development task record (created by Dev Skill)
 │   └── {module}-review-report.md      # Code review report (created by Review Skill)
 └── delivery-report.md                 # Final delivery summary

package/workspace-template/scripts/update-progress.js

@@ -129,6 +129,21 @@ function acquireLock(filePath) {
             fs.closeSync(fd);
             return lockPath;
         } catch (error) {
+            // 检查是否为锁文件已存在的错误
+            if (error.code === 'EEXIST') {
+                try {
+                    const lockStat = fs.statSync(lockPath);
+                    const ageSeconds = (Date.now() - lockStat.mtimeMs) / 1000;
+                    if (ageSeconds > 60) {
+                        console.error(`Warning: Stale lock file detected (age: ${Math.round(ageSeconds)}s), removing: ${lockPath}`);
+                        fs.unlinkSync(lockPath);
+                        // 不消耗重试次数，继续下一次循环尝试获取锁
+                        continue;
+                    }
+                } catch (statErr) {
+                    // 锁文件在 stat 时已被删除，继续重试即可
+                }
+            }
             retryCount++;
             if (retryCount >= maxRetries) {
                 throw new Error(`Failed to acquire file lock for '${filePath}' after ${maxRetries} attempts`);