speccrew 0.5.4 → 0.5.6

package/.speccrew/agents/speccrew-feature-designer.md

@@ -71,6 +71,14 @@ Phase 4: API Contract Generation
 4. **User Rejection**: User rejects Feature Registry, batch design summary, or Joint Confirmation → STOP, ask for specific revision requirements.
 5. **Worker Batch Failure**: If >50% workers in a batch fail → STOP entire batch, report to user.
 
+## TIMESTAMP INTEGRITY
+
+> **All timestamps in progress files (.checkpoints.json, DISPATCH-PROGRESS.json, WORKFLOW-PROGRESS.json) are generated exclusively by `update-progress.js` script.**
+
+1. **FORBIDDEN: Timestamp fabrication** — DO NOT generate, construct, or pass any timestamp string. The script's `getTimestamp()` function auto-generates accurate timestamps.
+2. **FORBIDDEN: Manual JSON creation** — DO NOT use `create_file` or `write` to create progress/checkpoint JSON files. ALWAYS use the appropriate `update-progress.js` command.
+3. **FORBIDDEN: Timestamp parameters** — DO NOT pass `--started-at`, `--completed-at`, or `--confirmed-at` parameters to `update-progress.js` commands. These parameters are deprecated.
+
 # Workflow
 
 ## Phase 0: Workflow Progress Management
@@ -314,8 +322,7 @@ Before presenting the Feature Registry to user:
    - Any features to add, remove, or merge?
 
    IF user requests changes → update .checkpoints.json, then re-present.
-   ONLY after user confirms → update function_decomposition.passed = true,
-   set confirmed_at via: node -e "console.log(new Date().toISOString())"
+   ONLY after user confirms → update function_decomposition.passed = true.
    Then proceed to Phase 3.
    ```
 

package/.speccrew/agents/speccrew-product-manager.md

@@ -859,8 +859,7 @@ node speccrew-workspace/scripts/update-progress.js write-checkpoint \
 ```bash
 node speccrew-workspace/scripts/update-progress.js update-workflow \
   --file speccrew-workspace/iterations/{iteration}/WORKFLOW-PROGRESS.json \
-  --stage 01_prd --status completed \
-  --completed-at $(node -e "console.log(new Date().toISOString())")
+  --stage 01_prd --status completed
 ```
 
 **5.3.3 Update PRD Status**
@@ -944,6 +943,7 @@ Phase 0 → Phase 1 → Phase 2 → Phase 3 → Phase 4 (if complex) → Phase 5
 - For complex requirements (3+ modules), dispatch Sub-PRD generation to parallel workers using `speccrew-pm-sub-prd-generate/SKILL.md`
 
 ### Must not do
+- **FORBIDDEN: Timestamp fabrication** — DO NOT generate or pass timestamp strings. All timestamps are auto-generated by `update-progress.js` script.
 - Do not make technical solution decisions (that's speccrew-planner's responsibility)
 - Do not skip manual confirmation to directly start the next stage
 - Do not assume business rules on your own; clarify unclear requirements with the user

package/.speccrew/skills/speccrew-fd-feature-design/SKILL.md

@@ -36,6 +36,7 @@ ISA-95 Stages 4-6 as internal thinking framework:
 
 **MANDATORY:**
 - Template-first workflow — Step 5 (copy template) MUST precede Step 6 (fill content)
+- **Mermaid for all diagrams** — ALL interaction flows, processing logic flows, and cross-function sequences MUST use Mermaid syntax (`sequenceDiagram`, `flowchart TD`). Plain text ASCII flowcharts are FORBIDDEN for these sections. Reference: `speccrew-workspace/docs/rules/mermaid-rule.md`.
 
 **NOTE:** Design process is internal — no intermediate design-data files are produced.
 
@@ -170,6 +171,8 @@ Create ASCII wireframes showing layout, UI elements, navigation.
 
 Document: `User Action → Frontend Response → Backend API Call`
 
+**Output format: Mermaid `sequenceDiagram`** — Generate interaction flows as Mermaid sequence diagrams showing: User → Frontend → Backend API → Data Store. DO NOT use ASCII text charts.
+
 > **ISA-95 Stage 4 Thinking — Information Flows**
 > - Cross-module flows: Map data flows between feature and other modules
 > - Sequence coverage: Complete chain user→frontend→backend→database→external
@@ -199,6 +202,8 @@ Document: `User Action → Frontend Response → Backend API Call`
 | Data Operations | What data to read/write |
 | Response | What data to return |
 
+**Output format: Mermaid `flowchart TD`** — Generate processing logic as Mermaid flowcharts showing: business validation → data operation → response. DO NOT use ASCII text charts.
+
 ### 2.3 Data Access Scheme
 
 | Operation | Data Target | Type |
@@ -396,6 +401,13 @@ Log: "✅ Checkpoint B (feature_design_review) passed and recorded"
 | 5. API Contract Summary | Aggregated from Step 2.1 API List |
 | 6. Notes | Contextual notes from analysis |
 
+**CRITICAL — Diagram Format Rule:**
+- "交互流程" / "Interaction Flow" sections → MUST use Mermaid `sequenceDiagram`
+- "核心业务逻辑" / "Processing Logic" sections → MUST use Mermaid `flowchart TD`
+- "跨函数流程" / "Cross-Function Flow" sections → MUST use Mermaid `sequenceDiagram`
+- Plain text / ASCII flowcharts are FORBIDDEN in these sections
+- Reference: `speccrew-workspace/docs/rules/mermaid-rule.md` for syntax compliance
+
 ### Filling Rules
 
 - Use `search_replace` for each section individually
@@ -471,7 +483,9 @@ Log: "✅ Feature Spec generation completed. Checkpoint feature_spec_review pass
 - [ ] Output path determined
 - [ ] Template copied using `create_file`
 - [ ] All sections filled using `search_replace`
-- [ ] Mermaid diagrams verified for compliance
+- [ ] **[CRITICAL]** Interaction Flow uses Mermaid sequenceDiagram (NOT ASCII)
+- [ ] **[CRITICAL]** Processing Logic uses Mermaid flowchart TD (NOT ASCII)
+- [ ] All Mermaid diagrams follow mermaid-rule.md compliance rules
 - [ ] `.checkpoints.json` updated via script
 - [ ] No technology decisions included
 - [ ] No intermediate design-data artifact created

package/.speccrew/skills/speccrew-fd-feature-design/templates/FEATURE-SPEC-TEMPLATE.md

@@ -195,7 +195,7 @@
 
 #### 2.1.2 Interaction Flow
 
-<!-- AI-NOTE: Use Mermaid sequenceDiagram to show the flow: User → Frontend → Backend API → Data Store. NO style definitions allowed. NO HTML tags. -->
+<!-- AI-NOTE: Use Mermaid sequenceDiagram to show the flow: User → Frontend → Backend API → Data Store. NO style definitions allowed. NO HTML tags. CRITICAL: This section MUST contain mermaid syntax. Plain text or ASCII flowcharts are FORBIDDEN. -->
 
 ```mermaid
 sequenceDiagram
@@ -250,7 +250,7 @@ sequenceDiagram
 
 **Processing Logic:**
 
-<!-- AI-NOTE: Use Mermaid flowchart TD to show the processing logic for each core interface. Show: business validation → data operation → response. NO style definitions allowed. -->
+<!-- AI-NOTE: Use Mermaid flowchart TD to show the processing logic for each core interface. Show: business validation → data operation → response. NO style definitions allowed. CRITICAL: This section MUST contain mermaid syntax. Plain text or ASCII flowcharts are FORBIDDEN. -->
 
 ```mermaid
 flowchart TD

package/package.json

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

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

@@ -34,8 +34,6 @@
  *      --output <text>         任务输出（completed 时使用）
  *      --error <text>          错误信息（failed 时使用）
  *      --error-category <cat>  错误类别（failed 时使用）
- *      --started-at <iso>      覆盖 started_at 时间戳
- *      --completed-at <iso>    覆盖 completed_at 时间戳
  *
  * 4. update-counts - 强制重算计数
  *    node update-progress.js update-counts --file <path>
@@ -56,9 +54,6 @@
  *      --stage <name>          阶段名称（必需）
  *      --status <status>       状态：pending/in_progress/completed/confirmed（必需）
  *      --output <text>         输出信息（可选）
- *      --started-at <iso>      覆盖 started_at 时间戳
- *      --completed-at <iso>    覆盖 completed_at 时间戳
- *      --confirmed-at <iso>    覆盖 confirmed_at 时间戳
  *
  * 输出格式：
  *   成功：{"success": true, "message": "...", "data": {...}}
@@ -555,24 +550,24 @@ function cmdUpdateTask(args) {
         task.status = args.status;
         task.updated_at = now;
 
-        // 根据状态自动设置时间戳
+        // 根据状态自动设置时间戳（始终使用脚本生成的真实时间，不接受外部参数）
         if (args.status === 'in_progress') {
-            task.started_at = args.startedAt || now;
+            task.started_at = now;
         } else if (args.status === 'partial') {
             // partial 状态：部分完成，可能已有 started_at，可选设置 completed_at
             if (!task.started_at) {
-                task.started_at = args.startedAt || now;
+                task.started_at = now;
             }
             if (args.output) {
                 task.output = args.output;
             }
         } else if (args.status === 'completed') {
-            task.completed_at = args.completedAt || now;
+            task.completed_at = now;
             if (args.output) {
                 task.output = args.output;
             }
         } else if (args.status === 'failed') {
-            task.completed_at = args.completedAt || now;
+            task.completed_at = now;
             if (args.error) {
                 task.error = args.error;
             }
@@ -750,16 +745,16 @@ function cmdUpdateWorkflow(args) {
         // 更新状态
         stage.status = args.status;
 
-        // 根据状态自动设置时间戳
+        // 根据状态自动设置时间戳（始终使用脚本生成的真实时间，不接受外部参数）
         if (args.status === 'in_progress') {
             // 如 started_at 已有值则不覆盖
             if (!stage.started_at) {
-                stage.started_at = args.startedAt || now;
+                stage.started_at = now;
             }
         } else if (args.status === 'completed') {
-            stage.completed_at = args.completedAt || now;
+            stage.completed_at = now;
         } else if (args.status === 'confirmed') {
-            stage.confirmed_at = args.confirmedAt || now;
+            stage.confirmed_at = now;
         }
 
         // 更新输出