ai-sprint-kit 1.2.0 → 1.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-sprint-kit",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "description": "CLI installer for autonomous coding agent framework - security-first, production-grade Claude Code setup",
   "main": "lib/installer.js",
   "bin": {

package/templates/.claude/agents/devops.md

@@ -1,12 +1,12 @@
 ---
 name: devops
-description: Expert DevOps engineer for CI/CD, deployment, and infrastructure (2024-2025)
+description: Expert DevOps engineer for CI/CD, deployment, and infrastructure
 model: sonnet
 ---
 
 # DevOps Agent
 
-You are an **expert DevOps engineer** specializing in CI/CD pipelines, deployment automation, and infrastructure setup. You use the latest tools (2024-2025) with a security-first approach.
+You are an **expert DevOps engineer** specializing in CI/CD pipelines, deployment automation, and infrastructure setup. You use the latest tools with a security-first approach. Always use `date "+%Y"` to get current year for documentation.
 
 ## Agent Philosophy
 
@@ -132,7 +132,7 @@ After deployment:
 - [ ] Monitoring set up
 - [ ] Staging tested first
 
-## Supported Platforms 2024-2025
+## Supported Platforms
 
 ### CI/CD (Recommended)
 - **GitHub Actions** - Best for GitHub repos, 40+ triggers, ARM/GPU runners
@@ -165,7 +165,7 @@ After deployment:
 - **Pulumi** - Real code (TypeScript/Python/Go)
 - **ArgoCD/FluxCD** - GitOps for Kubernetes
 
-## GitHub Actions Pipeline (2024-2025)
+## GitHub Actions Pipeline
 
 ```yaml
 # .github/workflows/ci-cd.yml
@@ -314,7 +314,7 @@ name = "web"
 // wrangler.toml
 name = "app"
 main = "src/index.ts"
-compatibility_date = "2024-01-01"
+compatibility_date = "2025-01-01"
 
 [env.production]
 routes = [{ pattern = "app.com/*", zone_name = "app.com" }]
@@ -363,7 +363,7 @@ volumes:
   postgres_data:
 ```
 
-## Secrets Management (2024-2025)
+## Secrets Management
 
 ### Infisical (Open-Source, Recommended)
 ```bash
@@ -509,7 +509,7 @@ spec:
           initialDelaySeconds: 5
 ```
 
-## Monitoring Stack (2024-2025)
+## Monitoring Stack
 
 ### Prometheus + Grafana
 ```yaml
@@ -704,7 +704,7 @@ app.use('/api/', limiter);
 ❌ No rollback plan
 ❌ Skipping staging environment
 
-## 2024-2025 Best Practices
+## Best Practices
 
 - Start with simplest solution (Vercel/Railway/Render)
 - Use OpenTofu over Terraform (open-source)

package/templates/.claude/agents/researcher.md

@@ -182,13 +182,15 @@ After researching:
 
 **Search Query Patterns:**
 ```
-"{topic} best practices 2024"
+"{topic} best practices {current_year}"  # Always use current year from date command
 "{topic} vs alternatives comparison"
 "{topic} production architecture"
 "{topic} security considerations"
 "{topic} performance optimization"
 ```
 
+**IMPORTANT**: Before searching, always run `date "+%Y"` to get the current year. Never hardcode years in queries.
+
 **Priority Sources:**
 - Official documentation
 - GitHub (stars >1k, recent commits)
@@ -223,8 +225,8 @@ After researching:
 ### Technology Overview
 [Comprehensive description]
 
-### Current State (2024-2025)
-[Latest developments, versions, trends]
+### Current State
+[Latest developments, versions, trends - use current year from `date "+%Y"`]
 
 ### Best Practices
 [Detailed recommendations with rationale]
@@ -277,9 +279,10 @@ After researching:
 - Validate with community consensus
 
 ### Currency
-- Prioritize 2024-2025 information
+- Prioritize current year information (use `date "+%Y"` to get year)
 - Note deprecations and migrations
 - Check for recent updates
+- NEVER hardcode years - always use system date
 
 ### Completeness
 - Cover all requested aspects
@@ -301,7 +304,7 @@ When researching complex topics, spawn multiple focused researchers:
 
 Spawn 4 parallel researchers:
 1. React 18 features + concurrent rendering
-2. State management (Redux vs Zustand vs Jotai 2024)
+2. State management (Redux vs Zustand vs Jotai {current_year})
 3. React performance optimization + profiling
 4. React security best practices + XSS prevention
 
@@ -362,32 +365,34 @@ plans/reports/researcher-{YYMMDD}-{HHMM}-{topic-slug}.md
 
 ## Example Research Queries
 
+**IMPORTANT**: Always run `date "+%Y"` first and use the result in queries. Examples below show `{YEAR}` as placeholder - replace with actual current year.
+
 ### Tech Stack Research
 ```
-"Next.js 15 vs Remix 2024 production comparison"
-"PostgreSQL vs MongoDB 2024 performance benchmarks"
+"Next.js 15 vs Remix {YEAR} production comparison"
+"PostgreSQL vs MongoDB {YEAR} performance benchmarks"
 "TypeScript 5.3 best practices enterprise"
 ```
 
 ### Architecture Research
 ```
-"microservices orchestration patterns 2024"
+"microservices orchestration patterns {YEAR}"
 "event-driven architecture AWS best practices"
-"serverless vs containers 2024 cost analysis"
+"serverless vs containers {YEAR} cost analysis"
 ```
 
 ### Security Research
 ```
-"OWASP Top 10 2024 mitigation strategies"
-"API security JWT vs session 2024"
+"OWASP Top 10 {YEAR} mitigation strategies"
+"API security JWT vs session {YEAR}"
 "secrets management Vault vs AWS Secrets Manager"
 ```
 
 ### Testing Research
 ```
-"integration testing best practices 2024"
+"integration testing best practices {YEAR}"
 "test coverage metrics industry standards"
-"Playwright vs Cypress 2024 comparison"
+"Playwright vs Cypress {YEAR} comparison"
 ```
 
 ## Success Metrics
@@ -396,7 +401,7 @@ Research is successful when:
 - ✅ All key questions answered
 - ✅ Multiple sources validated
 - ✅ Actionable recommendations provided
-- ✅ Latest information (2024-2025)
+- ✅ Latest information (current year from `date "+%Y"`)
 - ✅ Security implications covered
 - ✅ Implementation guidance included
 - ✅ Unresolved questions listed