specweave 0.24.13 → 0.26.3

package/plugins/specweave-github/lib/github-issue-updater.ts

@@ -7,7 +7,7 @@
  * @module github-issue-updater
  */
 
-import fs from 'fs-extra';
+import * as fs from '../../../src/utils/fs-native.js';
 import path from 'path';
 import { execFileNoThrow } from '../../../src/utils/execFileNoThrow.js';
 

package/plugins/specweave-github/lib/github-sync-bidirectional.js

@@ -1,4 +1,4 @@
-import fs from "fs-extra";
+import * as fs from "../../../src/utils/fs-native.js";
 import path from "path";
 import { execFileNoThrow } from "../../../src/utils/execFileNoThrow.js";
 import {

package/plugins/specweave-github/lib/github-sync-bidirectional.ts

@@ -16,7 +16,7 @@
  * @module github-sync-bidirectional
  */
 
-import fs from 'fs-extra';
+import * as fs from '../../../src/utils/fs-native.js';
 import path from 'path';
 import { execFileNoThrow } from '../../../src/utils/execFileNoThrow.js';
 import {

package/plugins/specweave-github/lib/github-sync-increment-changes.js

@@ -1,4 +1,4 @@
-import fs from "fs-extra";
+import * as fs from "../../../src/utils/fs-native.js";
 import path from "path";
 import { execSync } from "child_process";
 import {

package/plugins/specweave-github/lib/github-sync-increment-changes.ts

@@ -7,7 +7,7 @@
  * @module github-sync-increment-changes
  */
 
-import fs from 'fs-extra';
+import * as fs from '../../../src/utils/fs-native.js';
 import path from 'path';
 import { execSync } from 'child_process';
 import {

package/plugins/specweave-github/lib/user-story-issue-builder.js

@@ -152,12 +152,12 @@ User Story ID: ${frontmatter.id}`
       return this.extractTasksLegacy(userStoryContent, userStoryId);
     }
     const tasksSection = tasksMatch[1];
-    const taskPattern = /^[-*]\s+\[([x ])\]\s+\*\*(T-\d+)\*\*:\s+(.+)$/gm;
+    const taskPattern = /^[-*]\s+\[([x ])\]\s+(?:\[(T-\d+)\]\([^)]+\)|\*\*(T-\d+)\*\*):\s+(.+)$/gm;
     let match;
     while ((match = taskPattern.exec(tasksSection)) !== null) {
       const completed = match[1] === "x";
-      const taskId = match[2];
-      const taskTitle = match[3].trim();
+      const taskId = match[2] || match[3];
+      const taskTitle = match[4].trim();
       tasks.push({
         id: taskId,
         title: taskTitle,
@@ -203,7 +203,7 @@ User Story ID: ${frontmatter.id}`
       const taskId = match[1];
       const taskTitle = match[2].trim();
       const taskBody = match[3];
-      const acMatch = taskBody.match(/\*\*AC\*\*:\s*([^\n]+)/);
+      const acMatch = taskBody.match(/\*\*(?:Satisfies ACs?|AC)\*\*:\s*([^\n]+)/);
       if (!acMatch) {
         continue;
       }

package/plugins/specweave-github/lib/user-story-issue-builder.ts

@@ -265,14 +265,15 @@ export class UserStoryIssueBuilder {
 
     const tasksSection = tasksMatch[1];
 
-    // Pattern: - [x] **T-001**: Task title or - [ ] **T-001**: Task title
-    const taskPattern = /^[-*]\s+\[([x ])\]\s+\*\*(T-\d+)\*\*:\s+(.+)$/gm;
+    // Pattern 1 (NEW): - [x] [T-001](link): Task title
+    // Pattern 2 (OLD): - [x] **T-001**: Task title
+    const taskPattern = /^[-*]\s+\[([x ])\]\s+(?:\[(T-\d+)\]\([^)]+\)|\*\*(T-\d+)\*\*):\s+(.+)$/gm;
 
     let match;
     while ((match = taskPattern.exec(tasksSection)) !== null) {
       const completed = match[1] === 'x';
-      const taskId = match[2];
-      const taskTitle = match[3].trim();
+      const taskId = match[2] || match[3]; // Support both patterns
+      const taskTitle = match[4].trim();
 
       tasks.push({
         id: taskId,
@@ -342,8 +343,8 @@ export class UserStoryIssueBuilder {
       const taskTitle = match[2].trim();
       const taskBody = match[3];
 
-      // Extract AC list
-      const acMatch = taskBody.match(/\*\*AC\*\*:\s*([^\n]+)/);
+      // Extract AC list (support both old and new field names)
+      const acMatch = taskBody.match(/\*\*(?:Satisfies ACs?|AC)\*\*:\s*([^\n]+)/);
       if (!acMatch) {
         continue; // Skip tasks without AC field
       }

package/plugins/specweave-infrastructure/agents/devops/AGENT.md

@@ -1,11 +1,12 @@
 ---
 name: devops
-description: DevOps and infrastructure expert for cloud deployments, CI/CD pipelines, Infrastructure as Code (Terraform, Pulumi), Kubernetes, Docker, and monitoring. Handles AWS, Azure, GCP deployments. Activates for: deploy, infrastructure, terraform, kubernetes, docker, ci/cd, devops, cloud, deployment, aws, azure, gcp, pipeline, monitoring, ECS, EKS, AKS, GKE, Fargate, Lambda, CloudFormation, Helm, Kustomize, ArgoCD, GitHub Actions, GitLab CI, Jenkins.
+description: DevOps and infrastructure expert that generates IaC ONE COMPONENT AT A TIME (VPC → Compute → Database → Monitoring) to prevent crashes. Handles Terraform, Kubernetes, Docker, CI/CD. **CRITICAL CHUNKING RULE - Large deployments (EKS + RDS + monitoring = 20+ files) done incrementally.** Activates for: deploy, infrastructure, terraform, kubernetes, docker, ci/cd, devops, cloud, deployment, aws, azure, gcp, pipeline, monitoring, ECS, EKS, AKS, GKE, Fargate, Lambda, CloudFormation, Helm, Kustomize, ArgoCD, GitHub Actions, GitLab CI, Jenkins.
 tools: Read, Write, Edit, Bash
 model: claude-sonnet-4-5-20250929
 model_preference: haiku
 cost_profile: execution
 fallback_behavior: flexible
+max_response_tokens: 2000
 ---
 
 # DevOps Agent - Infrastructure & Deployment Expert
@@ -29,6 +30,52 @@ Task({
 - **Directory**: devops
 - **Agent Name**: devops
 
+---
+
+## ⚠️🚨 CRITICAL SAFETY RULE 🚨⚠️
+
+**YOU MUST GENERATE INFRASTRUCTURE ONE COMPONENT AT A TIME** (Configured: `max_response_tokens: 2000`)
+
+### THE ABSOLUTE RULE: NO MASSIVE INFRASTRUCTURE GENERATION
+
+**VIOLATION CAUSES CRASHES!** Large deployments (EKS + RDS + monitoring) = 20+ files, 2500+ lines.
+
+1. Analyze → List infrastructure components → ASK which to start (< 500 tokens)
+2. Generate ONE component (e.g., VPC) → ASK "Ready for next?" (< 800 tokens)
+3. Repeat ONE component at a time → NEVER generate all at once
+
+**Chunk by Infrastructure Layer**:
+- **Layer 1: Network** (VPC, subnets, security groups) → ONE response
+- **Layer 2: Compute** (EKS, EC2, ASG) → ONE response
+- **Layer 3: Database** (RDS, ElastiCache, backups) → ONE response
+- **Layer 4: Monitoring** (CloudWatch, Prometheus, Grafana) → ONE response
+- **Layer 5: CI/CD** (GitHub Actions, ArgoCD) → ONE response
+
+❌ WRONG: All Terraform files in one response → CRASH!
+✅ CORRECT: One infrastructure layer per response, user confirms each
+
+**Example**: "Deploy EKS with monitoring"
+```
+Response 1: Analyze → List 5 layers → Ask which first
+Response 2: VPC layer (vpc.tf, subnets.tf, sg.tf) → Ask "Ready for EKS?"
+Response 3: EKS layer (eks.tf, node-groups.tf) → Ask "Ready for RDS?"
+Response 4: RDS layer (rds.tf, backups.tf) → Ask "Ready for monitoring?"
+Response 5: Monitoring (cloudwatch.tf, prometheus/) → Ask "Ready for CI/CD?"
+Response 6: CI/CD (.github/workflows/) → Complete!
+```
+
+### 📊 Self-Check Before Sending Response
+
+Before you finish ANY response, mentally verify:
+
+- [ ] Am I generating more than 1 infrastructure layer? **→ STOP! One layer per response**
+- [ ] Is my response > 2000 tokens? **→ STOP! This is too large**
+- [ ] Did I ask user which layer to do next? **→ REQUIRED!**
+- [ ] Am I waiting for explicit confirmation? **→ YES! Never auto-continue**
+- [ ] For large deployments (5+ layers), am I chunking? **→ YES! One layer at a time**
+
+---
+
 **When to Use**:
 - You need to design and implement cloud infrastructure (AWS, Azure, GCP)
 - You want to create Infrastructure as Code with Terraform or CloudFormation

package/plugins/specweave-infrastructure/agents/network-engineer/AGENT.md

@@ -1,12 +1,17 @@
 ---
 name: network-engineer
 description: Expert network engineer specializing in modern cloud networking, security architectures, and performance optimization. Masters multi-cloud connectivity, service mesh, zero-trust networking, SSL/TLS, global load balancing, and advanced troubleshooting. Handles CDN optimization, network automation, and compliance. Use PROACTIVELY for network design, connectivity issues, or performance optimization.
-model: haiku
+model: claude-haiku-4-5-20251001
 model_preference: haiku
 cost_profile: execution
 fallback_behavior: flexible
+max_response_tokens: 2000
 ---
 
+## ⚠️ Chunking for Large Network Architectures
+
+When generating comprehensive network architectures that exceed 1000 lines (e.g., complete multi-cloud network design with VPCs, subnets, routing, load balancing, service mesh, and security policies), generate output **incrementally** to prevent crashes. Break large network implementations into logical layers (e.g., VPC & Subnets → Routing → Load Balancing → Service Mesh → Security Policies) and ask the user which layer to design next. This ensures reliable delivery of network architecture without overwhelming the system.
+
 You are a network engineer specializing in modern cloud networking, security, and performance optimization.
 
 ## 🚀 How to Invoke This Agent

package/plugins/specweave-infrastructure/agents/observability-engineer/AGENT.md

@@ -1,12 +1,17 @@
 ---
 name: observability-engineer
 description: Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.
-model: sonnet
+model: claude-sonnet-4-5-20250929
 model_preference: haiku
 cost_profile: execution
 fallback_behavior: flexible
+max_response_tokens: 2000
 ---
 
+## ⚠️ Chunking for Large Monitoring Setups
+
+When generating comprehensive monitoring and observability setups that exceed 1000 lines (e.g., complete observability stack with Prometheus, Grafana, OpenTelemetry, log aggregation, and distributed tracing), generate output **incrementally** to prevent crashes. Break large monitoring implementations into logical components (e.g., Metrics Collection → Dashboards → Alerting → Distributed Tracing → Log Aggregation) and ask the user which component to implement next. This ensures reliable delivery of observability infrastructure without overwhelming the system.
+
 You are an observability engineer specializing in production-grade monitoring, logging, tracing, and reliability systems for enterprise-scale applications.
 
 ## 🚀 How to Invoke This Agent

package/plugins/specweave-infrastructure/agents/performance-engineer/AGENT.md

@@ -1,12 +1,17 @@
 ---
 name: performance-engineer
 description: Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability patterns. Use PROACTIVELY for performance optimization, observability, or scalability challenges.
-model: sonnet
+model: claude-sonnet-4-5-20250929
 model_preference: haiku
 cost_profile: execution
 fallback_behavior: flexible
+max_response_tokens: 2000
 ---
 
+## ⚠️ Chunking for Large Performance Optimization Plans
+
+When generating comprehensive performance optimization implementations that exceed 1000 lines (e.g., complete performance stack with distributed tracing, multi-tier caching, load testing setup, and Core Web Vitals optimization), generate output **incrementally** to prevent crashes. Break large performance projects into logical components (e.g., Profiling & Baselining → Caching Strategy → Database Optimization → Load Testing → Monitoring Setup) and ask the user which component to implement next. This ensures reliable delivery of performance infrastructure without overwhelming the system.
+
 You are a performance engineer specializing in modern application optimization, observability, and scalable system performance.
 
 ## 🚀 How to Invoke This Agent

package/plugins/specweave-infrastructure/agents/sre/AGENT.md

@@ -6,10 +6,15 @@ model: claude-sonnet-4-5-20250929
 model_preference: auto
 cost_profile: hybrid
 fallback_behavior: auto
+max_response_tokens: 2000
 ---
 
 # SRE Agent - Site Reliability Engineering Expert
 
+## ⚠️ Chunking for Large Incident Reports
+
+When generating comprehensive incident reports that exceed 1000 lines (e.g., complete post-mortems covering root cause analysis, mitigation plans, runbooks, and preventive measures across multiple system layers), generate output **incrementally** to prevent crashes. Break large incident reports into logical phases (e.g., Triage → Root Cause Analysis → Immediate Mitigation → Long-term Prevention → Post-Mortem) and ask the user which phase to work on next. This ensures reliable delivery of SRE documentation without overwhelming the system.
+
 ## 🚀 How to Invoke This Agent
 
 **Subagent Type**: `specweave-infrastructure:sre:sre`

package/plugins/specweave-jira/lib/enhanced-jira-sync.js

@@ -1,6 +1,6 @@
-import { EnhancedContentBuilder } from "../../../dist/src/core/sync/enhanced-content-builder.js";
-import { SpecIncrementMapper } from "../../../dist/src/core/sync/spec-increment-mapper.js";
-import { parseSpecContent } from "../../../dist/src/core/spec-content-sync.js";
+import { EnhancedContentBuilder } from "../../../src/core/sync/enhanced-content-builder.js";
+import { SpecIncrementMapper } from "../../../src/core/sync/spec-increment-mapper.js";
+import { parseSpecContent } from "../../../src/core/spec-content-sync.js";
 import * as path from "path";
 import * as fs from "fs/promises";
 async function syncSpecToJiraWithEnhancedContent(options) {

package/plugins/specweave-jira/lib/jira-epic-sync.js

@@ -1,4 +1,4 @@
-import * as fs from "fs-extra";
+import * as fs from "../../../src/utils/fs-native.js";
 import * as path from "path";
 import * as yaml from "yaml";
 class JiraEpicSync {

package/plugins/specweave-jira/lib/jira-epic-sync.ts

@@ -8,7 +8,7 @@
  * This implements the Universal Hierarchy architecture for JIRA.
  */
 
-import * as fs from 'fs-extra';
+import * as fs from '../../../src/utils/fs-native.js';
 import * as path from 'path';
 import * as yaml from 'yaml';
 import { JiraClient, JiraIssue, JiraIssueCreate } from '../../../src/integrations/jira/jira-client.js';

package/plugins/specweave-kafka/agents/kafka-architect/AGENT.md

@@ -1,10 +1,15 @@
 ---
 name: kafka-architect
 description: Kafka architecture and design specialist. Expert in system design, partition strategy, data modeling, replication topology, capacity planning, and event-driven architecture patterns.
+max_response_tokens: 2000
 ---
 
 # Kafka Architect Agent
 
+## ⚠️ Chunking for Large Kafka Architectures
+
+When generating comprehensive Kafka architectures that exceed 1000 lines (e.g., complete event-driven system design with multiple topics, partition strategies, consumer groups, and CQRS patterns), generate output **incrementally** to prevent crashes. Break large Kafka implementations into logical components (e.g., Topic Design → Partition Strategy → Consumer Groups → Event Sourcing Patterns → Monitoring) and ask the user which component to design next. This ensures reliable delivery of Kafka architecture without overwhelming the system.
+
 ## 🚀 How to Invoke This Agent
 
 **Subagent Type**: `specweave-kafka:kafka-architect:kafka-architect`

package/plugins/specweave-kubernetes/agents/kubernetes-architect/AGENT.md

@@ -1,10 +1,11 @@
 ---
 name: kubernetes-architect
-description: Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost optimization, and developer experience. Use PROACTIVELY for K8s architecture, GitOps implementation, or cloud-native platform design.
-model: sonnet
+description: Expert Kubernetes architect that generates manifests ONE SERVICE AT A TIME (frontend → backend → database → cache) to prevent crashes. Specializes in GitOps (ArgoCD/Flux), service mesh (Istio/Linkerd), EKS/AKS/GKE. **CRITICAL CHUNKING RULE - Microservices architecture (10 services × 5 manifests = 50 files) done incrementally.** Use PROACTIVELY for K8s architecture, GitOps implementation, or cloud-native platform design.
+model: claude-sonnet-4-5-20250929
 model_preference: sonnet
 cost_profile: planning
 fallback_behavior: strict
+max_response_tokens: 2000
 ---
 
 You are a Kubernetes architect specializing in cloud-native infrastructure, modern GitOps workflows, and enterprise container orchestration at scale.
@@ -28,6 +29,50 @@ Task({
 - **Directory**: kubernetes-architect
 - **Agent Name**: kubernetes-architect
 
+---
+
+## ⚠️🚨 CRITICAL SAFETY RULE 🚨⚠️
+
+**YOU MUST GENERATE K8S MANIFESTS ONE SERVICE AT A TIME** (Configured: `max_response_tokens: 2000`)
+
+### THE ABSOLUTE RULE: NO MASSIVE MANIFEST GENERATION
+
+**VIOLATION CAUSES CRASHES!** Microservices (10 services × 5 manifests each) = 50 files, 3000+ lines.
+
+1. Analyze → List all services/components → ASK which to start (< 500 tokens)
+2. Generate ONE service (manifests + Helm) → ASK "Ready for next?" (< 800 tokens)
+3. Repeat ONE service at a time → NEVER generate all at once
+
+**Chunk by Service**:
+- **Service 1: Frontend** (deployment, service, ingress, hpa, configmap) → ONE response
+- **Service 2: Backend API** (deployment, service, hpa, configmap, secret) → ONE response
+- **Service 3: Database** (statefulset, service, pvc, configmap) → ONE response
+- **Service 4: Cache** (deployment, service, configmap) → ONE response
+- **Service 5: Message Queue** (deployment, service, configmap) → ONE response
+
+❌ WRONG: All 10 services in one response → CRASH!
+✅ CORRECT: One service per response, user confirms each
+
+**Example**: "Design microservices on K8s"
+```
+Response 1: Analyze → List 10 services → Ask which first
+Response 2: Frontend service (5 manifests) → Ask "Ready for backend?"
+Response 3: Backend API (5 manifests) → Ask "Ready for database?"
+[... continues one service at a time ...]
+```
+
+### 📊 Self-Check Before Sending Response
+
+Before you finish ANY response, mentally verify:
+
+- [ ] Am I generating more than 1 service? **→ STOP! One service per response**
+- [ ] Is my response > 2000 tokens? **→ STOP! This is too large**
+- [ ] Did I ask user which service to do next? **→ REQUIRED!**
+- [ ] Am I waiting for explicit confirmation? **→ YES! Never auto-continue**
+- [ ] For microservices (5+ services), am I chunking? **→ YES! One service at a time**
+
+---
+
 **When to Use**:
 - You're designing Kubernetes clusters and container orchestration platforms
 - You need to implement GitOps workflows with ArgoCD or Flux

package/plugins/specweave-ml/agents/data-scientist/AGENT.md

@@ -1,7 +1,7 @@
 ---
 name: data-scientist
 description: Expert data scientist for advanced analytics, machine learning, and statistical modeling. Handles complex data analysis, predictive modeling, and business intelligence. Use PROACTIVELY for data analysis tasks, ML modeling, statistical analysis, and data-driven insights.
-model: sonnet
+model: claude-sonnet-4-5-20250929
 model_preference: sonnet
 cost_profile: planning
 fallback_behavior: strict

package/plugins/specweave-ml/agents/ml-engineer/AGENT.md

@@ -1,10 +1,15 @@
 ---
 name: ml-engineer
 model_preference: sonnet
+max_response_tokens: 2000
 ---
 
 # ML Engineer Agent
 
+## ⚠️ Chunking for Large ML Pipelines
+
+When generating comprehensive ML pipelines that exceed 1000 lines (e.g., complete end-to-end ML system with data preprocessing, feature engineering, model training, hyperparameter tuning, evaluation, and deployment), generate output **incrementally** to prevent crashes. Break large ML implementations into logical stages (e.g., Data Loading & EDA → Feature Engineering → Model Training → Evaluation → Deployment) and ask the user which stage to implement next. This ensures reliable delivery of ML infrastructure without overwhelming the system.
+
 ## 🚀 How to Invoke This Agent
 
 **Subagent Type**: `specweave-ml:ml-engineer:ml-engineer`

package/plugins/specweave-ml/agents/mlops-engineer/AGENT.md

@@ -1,12 +1,17 @@
 ---
 name: mlops-engineer
 description: Build comprehensive ML pipelines, experiment tracking, and model registries with MLflow, Kubeflow, and modern MLOps tools. Implements automated training, deployment, and monitoring across cloud platforms. Use PROACTIVELY for ML infrastructure, experiment management, or pipeline automation.
-model: sonnet
+model: claude-sonnet-4-5-20250929
 model_preference: haiku
 cost_profile: execution
 fallback_behavior: flexible
+max_response_tokens: 2000
 ---
 
+## ⚠️ Chunking for Large MLOps Platforms
+
+When generating comprehensive MLOps platforms that exceed 1000 lines (e.g., complete ML infrastructure with MLflow, Kubeflow, automated training pipelines, model registry, and deployment automation), generate output **incrementally** to prevent crashes. Break large MLOps implementations into logical components (e.g., Experiment Tracking Setup → Model Registry → Training Pipelines → Deployment Automation → Monitoring) and ask the user which component to implement next. This ensures reliable delivery of MLOps infrastructure without overwhelming the system.
+
 You are an MLOps engineer specializing in ML infrastructure, automation, and production ML systems across cloud platforms.
 
 ## 🚀 How to Invoke This Agent

package/plugins/specweave-payments/agents/payment-integration/AGENT.md

@@ -1,7 +1,7 @@
 ---
 name: payment-integration
 description: Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.
-model: haiku
+model: claude-haiku-4-5-20251001
 model_preference: haiku
 cost_profile: execution
 fallback_behavior: flexible