speccrew 0.6.37 → 0.6.39

package/.speccrew/agents/speccrew-team-leader-xml.md

@@ -400,6 +400,13 @@ When user reports problems ("something went wrong", "error occurred", "not worki
 - When dispatching workers: ensure task descriptions explicitly state "use PowerShell/Bash only"
 - For JSON operations: use `node -e` with inline JS, or PowerShell `ConvertFrom-Json` / `ConvertTo-Json`
 
+**CONTINUOUS EXECUTION ENFORCEMENT:**
+- NEVER offer A/B/C choices during pipeline execution
+- NEVER pause to ask "Should I continue?" when workload is large
+- NEVER suggest "partial execution" or "on-demand initialization" as options
+- When context window is running low, complete current stage fully, write checkpoint, then continue in next context — DO NOT ask user
+- The ONLY acceptable reason to stop is: unrecoverable error (file system failure, missing dependencies)
+
 **Must NOT Do:**
 - Do not directly execute specific steps in Skill (must read Skill file first)
 - Do not skip Skill and directly generate deliverables

package/.speccrew/skills/speccrew-knowledge-bizs-dispatch-xml/SKILL.md

@@ -105,6 +105,10 @@ Stage 4: System Summary
     <field name="text">DO NOT ask for confirmation before generating output files</field>
     <field name="text">DO NOT warn about "large number of files" or "this may take a while" — proceed with generation</field>
     <field name="text">ONLY pause at explicit &lt;event action="confirm"&gt; blocks defined in the workflow</field>
+    <field name="text">DO NOT offer "continue/pause/partial" options — EVER</field>
+    <field name="text">DO NOT estimate workload and suggest breaking it into phases — execute ALL phases in sequence</field>
+    <field name="text">When many features need analysis, dispatch ALL of them — do NOT skip or defer any</field>
+    <field name="text">Context window management: if approaching limit, save progress to checkpoint file and resume — do NOT ask user for guidance</field>
   </block>
 
   <!-- ============================================================

package/.speccrew/skills/speccrew-knowledge-system-summarize/SKILL.md

@@ -55,7 +55,7 @@ Before starting, verify:
 - **Empty modules directory**: If no `*-overview.md` files found, generate a skeleton system-overview.md with empty statistics and return `status: "warning"`.
 - **Incomplete module overviews**: If a module-overview.md only has Section 1-2 (initial version), use available data and note gaps with `<!-- DATA INCOMPLETE -->`.
 - **Same module name from different platforms**: Treat as separate modules. Use `{module_name} ({platform_type})` for display and `{module_name}_{platform_type}` as internal ID.
-- **Missing timestamp service**: If `speccrew-get-timestamp` is unavailable, use system current time as fallback.
+- **Timestamp generation**: Run `node scripts/get-timestamp.js` to get current timestamp. If the script is unavailable, use system current time as fallback.
 
 ```mermaid
 flowchart TD
@@ -261,10 +261,10 @@ Fill each `[TO BE FILLED]` placeholder with actual content:
    - Read `speccrew-workspace/docs/configs/tech-stack-mappings.json` → system tech stacks and display names
    - Read `speccrew-workspace/docs/rules/mermaid-rule.md` → Mermaid diagram guidelines
 
-2. **Invoke** `speccrew-get-timestamp` using Skill tool:
-   - Parameters: none (uses default format `YYYY-MM-DD-HHmmss`)
-   - Returns: timestamp string (e.g., `2026-03-17-132645`)
-   - Use the returned timestamp as generation timestamp in document
+2. **Get timestamp** by running the script:
+   - Run: `node scripts/get-timestamp.js`
+   - Default format: `YYYY-MM-DD-HHmmss` (e.g., `2026-03-17-132645`)
+   - Use the output as generation timestamp in document
 
 3. **Determine Technology Stack**:
    - Extract platform types from discovered module paths

package/.speccrew/skills/speccrew-knowledge-system-summarize-xml/SKILL.md

@@ -292,9 +292,9 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
     <output name="mermaid_rules" />
   </task>
 
-  <!-- Invoke speccrew-get-timestamp skill -->
-  <task name="get_timestamp" action="run-skill" skill="speccrew-get-timestamp">
-    <output name="timestamp" />
+  <!-- Get timestamp via script -->
+  <task name="get_timestamp" action="run-script" description="Get current timestamp">
+    <run-script script="scripts/get-timestamp.js" output="timestamp" />
   </task>
 
   <!-- Gateway: Fallback for timestamp -->

package/.speccrew/skills/speccrew-knowledge-techs-dispatch/SKILL.md

@@ -308,7 +308,7 @@ speccrew-workspace/knowledges/techs/{platform_id}/
 2. `speccrew-knowledge-techs-index` must check actual existing documents per platform and dynamically generate links
 
 **Status Tracking**:
-- **Get timestamp** using `speccrew-get-timestamp` skill
+- **Get timestamp**: Run `node scripts/get-timestamp.js` to get current timestamp
 - **Generate `stage2-status.json`** at `speccrew-workspace/knowledges/base/sync-state/knowledge-techs/stage2-status.json`
 
 **Stage 2 status tracks**:
@@ -675,7 +675,7 @@ THRESHOLD: warnings > 5 → flag for manual review
 - `speccrew-workspace/knowledges/techs/INDEX.md` (complete with platform index and Agent mapping, dynamically generated)
 
 **Status Tracking**:
-- **Get timestamp** using `speccrew-get-timestamp` skill
+- **Get timestamp**: Run `node scripts/get-timestamp.js` to get current timestamp
 - **Generate `stage3-status.json`** at `speccrew-workspace/knowledges/base/sync-state/knowledge-techs/stage3-status.json`
 
 **Stage 3 status tracks**:

package/.speccrew/skills/speccrew-knowledge-techs-dispatch-xml/SKILL.md

@@ -118,6 +118,10 @@ Read `speccrew-workspace/docs/configs/platform-mapping.json` for standardized pl
     <field name="text">DO NOT ask for confirmation before generating output files</field>
     <field name="text">DO NOT warn about "large number of files" or "this may take a while" — proceed with generation</field>
     <field name="text">ONLY pause at explicit &lt;event action="confirm"&gt; blocks defined in the workflow</field>
+    <field name="text">DO NOT offer "continue/pause/partial" options — EVER</field>
+    <field name="text">DO NOT estimate workload and suggest breaking it into phases — execute ALL phases in sequence</field>
+    <field name="text">When many platforms need analysis, dispatch ALL of them — do NOT skip or defer any</field>
+    <field name="text">Context window management: if approaching limit, save progress to checkpoint file and resume — do NOT ask user for guidance</field>
   </block>
 
   <!-- ============================================================

package/.speccrew/skills/speccrew-knowledge-techs-index/SKILL.md

@@ -160,8 +160,8 @@ Read each platform's INDEX.md to extract:
    - Preserve all template section headers and structure
 
 3. **Get Timestamp**:
-   - **CRITICAL**: Use the Skill tool to invoke `speccrew-get-timestamp` (no format parameter needed, uses default)
-   - Store the returned timestamp as `{{generated_at}}` template variable
+   - **CRITICAL**: Run `node scripts/get-timestamp.js` to get current timestamp (no format parameter needed, uses default)
+   - Store the output as `{{generated_at}}` template variable
 
 4. **Fill the following sections** in the copied template:
 

package/.speccrew/skills/speccrew-knowledge-techs-index-xml/SKILL.md

@@ -120,8 +120,8 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
   </loop>
 
   <!-- Step 4: Get Timestamp -->
-  <task id="step4-get-timestamp" action="run-skill" description="Get current timestamp for generated_at field">
-    <run-skill skill="speccrew-get-timestamp" />
+  <task id="step4-get-timestamp" action="run-script" description="Get current timestamp for generated_at field">
+    <run-script script="scripts/get-timestamp.js" output="timestamp" />
   </task>
 
   <!-- Step 5: Generate Root INDEX.md -->

package/.speccrew/skills/speccrew-knowledge-techs-init/SKILL.md

@@ -155,8 +155,8 @@ For each detected platform, extract:
 ### Step 3: Generate techs-manifest.json
 
 1. **Get Timestamp**:
-   - **CRITICAL**: Use the Skill tool to invoke `speccrew-get-timestamp` (no format parameter needed, uses default)
-   - Store the returned timestamp as `generated_at` value
+   - **CRITICAL**: Run `node scripts/get-timestamp.js` to get current timestamp (no format parameter needed, uses default)
+   - Store the output as `generated_at` value
 
 2. **Create JSON file** with detected platforms:
 

package/.speccrew/skills/speccrew-knowledge-techs-init-xml/SKILL.md

@@ -132,8 +132,8 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
   </loop>
 
   <!-- Step 3: Get Timestamp -->
-  <task id="step3-get-timestamp" action="run-skill" description="Get current timestamp for generated_at field">
-    <run-skill skill="speccrew-get-timestamp" />
+  <task id="step3-get-timestamp" action="run-script" description="Get current timestamp for generated_at field">
+    <run-script script="scripts/get-timestamp.js" output="timestamp" />
   </task>
 
   <!-- Step 4: Generate techs-manifest.json -->

package/package.json

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

package/workspace-template/scripts/get-timestamp.js

@@ -0,0 +1,35 @@
+#!/usr/bin/env node
+/**
+ * Get current timestamp in specified format
+ * Usage: node get-timestamp.js [format]
+ * Default format: YYYY-MM-DD-HHmmss
+ */
+
+const FORMATS = {
+  'YYYY-MM-DD-HHmmss': () => {
+    const now = new Date();
+    return `${now.getFullYear()}-${String(now.getMonth() + 1).padStart(2, '0')}-${String(now.getDate()).padStart(2, '0')}-${String(now.getHours()).padStart(2, '0')}${String(now.getMinutes()).padStart(2, '0')}${String(now.getSeconds()).padStart(2, '0')}`;
+  },
+  'YYYY-MM-DD': () => {
+    const now = new Date();
+    return `${now.getFullYear()}-${String(now.getMonth() + 1).padStart(2, '0')}-${String(now.getDate()).padStart(2, '0')}`;
+  },
+  'HHmm': () => {
+    const now = new Date();
+    return `${String(now.getHours()).padStart(2, '0')}${String(now.getMinutes()).padStart(2, '0')}`;
+  },
+  'ISO': () => new Date().toISOString()
+};
+
+function getTimestamp(format = 'YYYY-MM-DD-HHmmss') {
+  const formatter = FORMATS[format];
+  if (formatter) {
+    return formatter();
+  }
+  // Default fallback
+  return FORMATS['YYYY-MM-DD-HHmmss']();
+}
+
+// Main execution
+const format = process.argv[2] || 'YYYY-MM-DD-HHmmss';
+console.log(getTimestamp(format));