specweave 0.28.0 → 0.28.3

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

@@ -2,8 +2,8 @@
 name: devops
 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
+model: claude-opus-4-5-20251101
+model_preference: opus
 cost_profile: execution
 fallback_behavior: flexible
 max_response_tokens: 2000

package/src/templates/.env.example

@@ -53,35 +53,18 @@ VERCEL_TOKEN=your-vercel-token-here
 # ============================================================================
 
 # ----------------------------------------------------------------------------
-# GitHub - 3 Strategies for Team Organization
+# GitHub
 # ----------------------------------------------------------------------------
+# RECOMMENDED: Use gh CLI instead of tokens
+#   gh auth login
+#
+# Only use GITHUB_TOKEN if gh CLI is not available (e.g., CI/CD)
 # Guide: https://github.com/settings/tokens
-# Scopes: repo, read:org, workflow
+# Scopes: repo, read:org
 
-# Required for all strategies:
-GH_TOKEN=ghp_your-github-token-40-chars
-
-# Strategy 1: Repository-per-team (MOST COMMON)
-# Use when: Each team has separate repositories (microservices, multi-repo)
-# Example: Frontend team → frontend-app, Backend team → backend-api
-GITHUB_STRATEGY=repository-per-team
-GITHUB_OWNER=myorg
-GITHUB_REPOS=frontend-app,backend-api,mobile-app,qa-tools
-
-# Strategy 2: Team-based (MONOREPO)
-# Use when: Single repository with team-based filtering
-# Example: Monorepo with teams working on different parts
-# GITHUB_STRATEGY=team-based
-# GITHUB_OWNER=myorg
-# GITHUB_REPO=main-product
-# GITHUB_TEAMS=frontend-team,backend-team,mobile-team,qa-team
-
-# Strategy 3: Team-multi-repo (COMPLEX)
-# Use when: Teams own multiple repositories (platform teams)
-# Example: Platform team owns api-gateway + auth-service
-# GITHUB_STRATEGY=team-multi-repo
-# GITHUB_OWNER=myorg
-# GITHUB_TEAM_REPO_MAPPING='{"platform-team":["api-gateway","auth-service"],"frontend-team":["web-app","mobile-app"]}'
+GITHUB_TOKEN=ghp_your-github-token-40-chars
+
+# All other GitHub configuration is in .specweave/config.json
 
 # ----------------------------------------------------------------------------
 # Jira - 3 Strategies for Team Organization