ai-sprint-kit 1.1.9 → 1.2.1

package/README.md

@@ -37,7 +37,7 @@ npx ai-sprint-kit init
 claude
 
 # Run your first autonomous cycle
-/auto "build a REST API for user management"
+/ai-sprint-auto "build a REST API for user management"
 ```
 
 **That's it.** The framework handles planning, coding, testing, security scanning, and documentation.
@@ -63,17 +63,17 @@ claude
 ### 11 Slash Commands
 
 ```bash
-/plan     # Create implementation plans
-/code     # Generate or refactor code
-/test     # Generate and run tests
-/review   # Code quality review
-/secure   # Security scanning
-/deploy   # CI/CD setup
-/docs     # Generate documentation
-/debug    # Investigate issues
-/scan     # Index codebase for AI context
-/validate # Pre-commit checks
-/auto     # Full autonomous cycle
+/ai-sprint-plan     # Create implementation plans
+/ai-sprint-code     # Generate or refactor code
+/ai-sprint-test     # Generate and run tests
+/ai-sprint-review   # Code quality review
+/ai-sprint-secure   # Security scanning
+/ai-sprint-deploy   # CI/CD setup
+/ai-sprint-docs     # Generate documentation
+/ai-sprint-debug    # Investigate issues
+/ai-sprint-scan     # Index codebase for AI context
+/ai-sprint-validate # Pre-commit checks
+/ai-sprint-auto     # Full autonomous cycle
 ```
 
 ### Built-in Security
@@ -164,7 +164,7 @@ your-project/
 mkdir my-app && cd my-app
 npx ai-sprint-kit init
 claude
-/auto "build e-commerce API with Stripe integration"
+/ai-sprint-auto "build e-commerce API with Stripe integration"
 ```
 
 ### Existing Project
@@ -173,17 +173,17 @@ claude
 cd my-existing-project
 npx ai-sprint-kit init --scan
 claude
-/review   # Analyze code quality
-/secure   # Find vulnerabilities
+/ai-sprint-review   # Analyze code quality
+/ai-sprint-secure   # Find vulnerabilities
 ```
 
 ### Security-First Development
 
 ```bash
-/plan "implement payment processing"
-/code "build with PCI DSS compliance"
-/secure   # Comprehensive scan
-/validate # Pre-commit checks
+/ai-sprint-plan "implement payment processing"
+/ai-sprint-code "build with PCI DSS compliance"
+/ai-sprint-secure   # Comprehensive scan
+/ai-sprint-validate # Pre-commit checks
 ```
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-sprint-kit",
-  "version": "1.1.9",
+  "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/debugger.md

@@ -111,7 +111,7 @@ ai_context/
 
 ### Phase 4: Document
 ```
-1. Call Write: ai_context/reports/debug-{timestamp}-{slug}.md
+1. Call Write: ai_context/reports/ai-sprint-debug-{timestamp}-{slug}.md
 2. Update ai_context/memory/learning.md with new pattern
 ```
 

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
 
@@ -108,7 +108,7 @@ ai_context/
 
 ### Phase 4: Documentation
 ```
-1. Call Write: ai_context/reports/deploy-{timestamp}.md
+1. Call Write: ai_context/reports/ai-sprint-deploy-{timestamp}.md
 2. Document rollback procedures
 3. Update ai_context/memory/decisions.md
 ```
@@ -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/docs.md

@@ -107,7 +107,7 @@ ai_context/
 
 ### Phase 4: Report
 ```
-1. Call Write: ai_context/reports/docs-audit-{timestamp}.md
+1. Call Write: ai_context/reports/ai-sprint-docs-audit-{timestamp}.md
 2. Document what was updated
 ```
 

package/templates/.claude/agents/implementer.md

@@ -76,7 +76,7 @@ date "+%y%m%d"      # For file naming: 251224
 
 ### Phase 1: Context & Planning
 ```
-1. Call Read tool for ai_context/plans/*/plan.md (current plan)
+1. Call Read tool for ai_context/ai-sprint-plans/*/ai-sprint-plan.md (current plan)
 2. Call Read tool for ai_context/memory/learning.md (avoid mistakes)
 3. Call Read tool for existing code in scope
 4. Call Glob to understand project structure
@@ -208,7 +208,7 @@ Activate these skills for enhanced capabilities:
 
 Before implementing:
 1. Check `ai_context/memory/learning.md` - Avoid past mistakes
-2. Check `ai_context/plans/` - Follow the plan
+2. Check `ai_context/ai-sprint-plans/` - Follow the plan
 
 After implementing:
 1. Update `ai_context/memory/learning.md` if you learned something

package/templates/.claude/agents/planner.md

@@ -101,7 +101,7 @@ DO NOT use model knowledge for dates. Always call Bash with date command.
 
 ### Phase 3: Plan Creation
 ```
-1. Call Write tool to create ai_context/plans/{timestamp}-feature-name/plan.md
+1. Call Write tool to create ai_context/ai-sprint-plans/{timestamp}-feature-name/ai-sprint-plan.md
 2. Call Write tool for each phase-*.md breakdown
 3. Include security considerations in every phase
 4. Define measurable success criteria

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

package/templates/.claude/agents/reviewer.md

@@ -98,7 +98,7 @@ ai_context/
 
 ### Phase 3: Reporting
 ```
-1. Call Write: ai_context/reports/review-{timestamp}.md
+1. Call Write: ai_context/reports/ai-sprint-review-{timestamp}.md
 2. Categorize by severity (Critical/High/Medium/Low)
 3. Provide before/after code examples
 4. Include rationale for each suggestion

package/templates/.claude/agents/tester.md

@@ -108,7 +108,7 @@ ai_context/
 
 ### Phase 4: Reporting
 ```
-1. Call Write: ai_context/reports/test-coverage-{timestamp}.md
+1. Call Write: ai_context/reports/ai-sprint-test-coverage-{timestamp}.md
 2. Document coverage metrics
 3. Note gaps and recommendations
 ```
@@ -491,7 +491,7 @@ test('no memory leaks in worker', async () => {
 
 ### CI Configuration
 ```yaml
-# .github/workflows/test.yml
+# .github/workflows/ai-sprint-test.yml
 name: Tests
 
 on: [push, pull_request]
@@ -507,7 +507,7 @@ jobs:
       - run: npm run test:e2e
 
       # Upload coverage
-      - uses: codecov/codecov-action@v3
+      - uses: codecov/ai-sprint-codecov-action@v3
         with:
           files: ./coverage/lcov.info
 

package/templates/.claude/commands/{auto.md → ai-sprint-auto.md}

@@ -15,21 +15,21 @@ argument-hint: [feature description]
 
 ### Phase 1: Planning (MANDATORY - Execute First)
 
-**⚠️ STOP! Before ANY code, execute `/plan` command:**
+**⚠️ STOP! Before ANY code, execute `/ai-sprint-plan` command:**
 
 ```
-/plan "$ARGUMENTS"
+/ai-sprint-plan "$ARGUMENTS"
 ```
 
-The `/plan` command will:
+The `/ai-sprint-plan` command will:
 1. Research best practices and approaches
 2. Ask clarifying questions if needed
 3. Create implementation plan with architecture
-4. Save plan to `ai_context/plans/`
+4. Save plan to `ai_context/ai-sprint-plans/`
 
 **Validation Gate:** Plan MUST exist before proceeding.
-- Check: `ai_context/plans/` has new plan directory
-- If NO plan exists → STOP and run `/plan` first
+- Check: `ai_context/ai-sprint-plans/` has new plan directory
+- If NO plan exists → STOP and run `/ai-sprint-plan` first
 
 ---
 
@@ -37,7 +37,7 @@ The `/plan` command will:
 
 Only after plan exists, execute:
 ```
-/code "implement the plan at ai_context/plans/{plan-path}"
+/ai-sprint-code "implement the plan at ai_context/ai-sprint-plans/{plan-path}"
 ```
 
 **Requirements:**
@@ -52,7 +52,7 @@ Only after plan exists, execute:
 
 After implementation, execute:
 ```
-/test
+/ai-sprint-test
 ```
 
 **Requirements:**
@@ -62,7 +62,7 @@ After implementation, execute:
 - All tests must pass
 
 **Validation Gate:** Tests must pass before proceeding.
-- If tests fail → Fix issues → Rerun `/test`
+- If tests fail → Fix issues → Rerun `/ai-sprint-test`
 - Do NOT proceed with failing tests
 
 ---
@@ -71,7 +71,7 @@ After implementation, execute:
 
 After tests pass, execute:
 ```
-/review
+/ai-sprint-review
 ```
 
 **Requirements:**
@@ -80,7 +80,7 @@ After tests pass, execute:
 - No critical issues allowed
 
 **Validation Gate:** Review must pass.
-- If critical issues → Fix → Rerun `/review`
+- If critical issues → Fix → Rerun `/ai-sprint-review`
 
 ---
 
@@ -88,7 +88,7 @@ After tests pass, execute:
 
 After review passes, execute:
 ```
-/secure
+/ai-sprint-secure
 ```
 
 **Requirements:**
@@ -97,7 +97,7 @@ After review passes, execute:
 - Dependency vulnerability check
 
 **Validation Gate:** No high/critical security issues.
-- If issues found → Fix → Rerun `/secure`
+- If issues found → Fix → Rerun `/ai-sprint-secure`
 
 ---
 
@@ -105,7 +105,7 @@ After review passes, execute:
 
 After security passes, execute:
 ```
-/docs
+/ai-sprint-docs
 ```
 
 **Requirements:**
@@ -144,7 +144,7 @@ After all phases complete, provide summary:
 
 ## REMEMBER
 
-- **Phase 1 is MANDATORY** - Always run `/plan` first
+- **Phase 1 is MANDATORY** - Always run `/ai-sprint-plan` first
 - **No skipping** - Execute each phase in order
 - **Validation gates** - Do not proceed if a gate fails
 - **Fix and retry** - If any phase fails, fix issues and rerun

package/templates/.claude/commands/{code.md → ai-sprint-code.md}

@@ -11,13 +11,13 @@ argument-hint: [plan-path or task description]
 
 ### Step 0: Check for Plan (IMPORTANT)
 
-**If argument contains a plan path (e.g., `ai_context/plans/...`):**
+**If argument contains a plan path (e.g., `ai_context/ai-sprint-plans/...`):**
 1. Read the plan: `plan.md` and `phase-*.md` files
 2. Follow implementation phases in order
 3. Mark phases complete as you progress
 
 **If no plan exists:**
-- Ask: "No plan found. Run `/plan` first or proceed with direct implementation?"
+- Ask: "No plan found. Run `/ai-sprint-plan` first or proceed with direct implementation?"
 - If direct implementation requested, continue to Step 1
 
 ---
@@ -143,7 +143,7 @@ export async function createUser(data) {
 
 ### Example 1: API Endpoint
 ```
-/code "create REST API endpoint for user registration with email verification"
+/ai-sprint-code "create REST API endpoint for user registration with email verification"
 ```
 
 **Generated:**
@@ -213,7 +213,7 @@ export async function POST(request: Request) {
 
 ### Example 2: Refactoring
 ```
-/code "refactor this callback-based code to use async/await"
+/ai-sprint-code "refactor this callback-based code to use async/await"
 ```
 
 **Before:**
@@ -261,40 +261,40 @@ async function getUser(id: string): Promise<User> {
 
 ## Next Steps
 
-After `/code` completion:
+After `/ai-sprint-code` completion:
 1. Review generated code
-2. Run `/test` to generate tests
-3. Run `/review` for quality check
-4. Run `/secure` for security scan
+2. Run `/ai-sprint-test` to generate tests
+3. Run `/ai-sprint-review` for quality check
+4. Run `/ai-sprint-secure` for security scan
 5. Commit changes
 
 ## Common Use Cases
 
 ### New Features
 ```
-/code "add pagination to the products API"
-/code "implement password reset functionality"
-/code "create admin dashboard with user management"
+/ai-sprint-code "add pagination to the products API"
+/ai-sprint-code "implement password reset functionality"
+/ai-sprint-code "create admin dashboard with user management"
 ```
 
 ### Refactoring
 ```
-/code "convert class components to functional components"
-/code "split this 500-line file into smaller modules"
-/code "replace REST with GraphQL for user API"
+/ai-sprint-code "convert class components to functional components"
+/ai-sprint-code "split this 500-line file into smaller modules"
+/ai-sprint-code "replace REST with GraphQL for user API"
 ```
 
 ### Bug Fixes
 ```
-/code "fix the race condition in payment processing"
-/code "resolve memory leak in WebSocket handler"
+/ai-sprint-code "fix the race condition in payment processing"
+/ai-sprint-code "resolve memory leak in WebSocket handler"
 ```
 
 ### Performance
 ```
-/code "optimize this N+1 query problem"
-/code "add caching to frequently accessed data"
-/code "implement lazy loading for images"
+/ai-sprint-code "optimize this N+1 query problem"
+/ai-sprint-code "add caching to frequently accessed data"
+/ai-sprint-code "implement lazy loading for images"
 ```
 
 ## Remember

package/templates/.claude/commands/{debug.md → ai-sprint-debug.md}

@@ -7,17 +7,17 @@ argument-hint: [bug description or error message]
 
 **Objective:** $ARGUMENTS
 
-## Command: /debug
+## Command: /ai-sprint-debug
 
 Systematically investigate bugs, perform root cause analysis, and provide fixes with regression tests.
 
 ## Usage
 
 ```
-/debug "users can't login"
-/debug "500 error on checkout"
-/debug "memory leak in WebSocket handler"
-/debug "database query is slow"
+/ai-sprint-debug "users can't login"
+/ai-sprint-debug "500 error on checkout"
+/ai-sprint-debug "memory leak in WebSocket handler"
+/ai-sprint-debug "database query is slow"
 ```
 
 ## Workflow
@@ -252,11 +252,11 @@ Before debugging:
 
 After debugging:
 - Update `ai_context/memory/learning.md` with new bug pattern
-- Save report to `ai_context/reports/debug-{timestamp}-{slug}.md`
+- Save report to `ai_context/reports/ai-sprint-debug-{timestamp}-{slug}.md`
 
 ## Debug Report
 
-Save to: `ai_context/reports/debug-YYMMDD-slug.md`
+Save to: `ai_context/reports/ai-sprint-debug-YYMMDD-slug.md`
 
 ```markdown
 # Bug Fix Report
@@ -376,13 +376,13 @@ git bisect reset
 
 ## Integration with Other Commands
 
-**/debug** → **/test**
+**/ai-sprint-debug** → **/ai-sprint-test**
 - After fixing bug, add regression test
 
-**/debug** → **/review**
+**/ai-sprint-debug** → **/ai-sprint-review**
 - Review fix for quality and security
 
-**/debug** → **/secure**
+**/ai-sprint-debug** → **/ai-sprint-secure**
 - If security bug, run security scan
 
 ## Debug Checklist

package/templates/.claude/commands/{deploy.md → ai-sprint-deploy.md}

@@ -3,17 +3,17 @@ description: Set up CI/CD pipeline and deployment automation
 argument-hint: [optional: platform (github|gitlab|vercel|railway)]
 ---
 
-## Command: /deploy
+## Command: /ai-sprint-deploy
 
 Set up automated CI/CD pipeline and configure deployment to your chosen platform.
 
 ## Usage
 
 ```
-/deploy
-/deploy --platform github
-/deploy --platform vercel
-/deploy --platform railway
+/ai-sprint-deploy
+/ai-sprint-deploy --platform github
+/ai-sprint-deploy --platform vercel
+/ai-sprint-deploy --platform railway
 ```
 
 ## Workflow
@@ -53,7 +53,7 @@ If not specified, suggest based on project:
 
 ### GitHub Actions (CI/CD)
 ```yaml
-# .github/workflows/deploy.yml
+# .github/workflows/ai-sprint-deploy.yml
 name: Deploy
 
 on:
@@ -418,7 +418,7 @@ app.use('/api/', limiter);
 
 ## Output
 
-After `/deploy` completion:
+After `/ai-sprint-deploy` completion:
 
 ✅ **CI/CD Pipeline Configured**
 - Automated testing

package/templates/.claude/commands/{docs.md → ai-sprint-docs.md}

@@ -3,17 +3,17 @@ description: Generate and update project documentation
 argument-hint: [optional: specific doc type (readme|api|architecture)]
 ---
 
-## Command: /docs
+## Command: /ai-sprint-docs
 
 Generate comprehensive, up-to-date documentation including README, API docs, architecture diagrams, and inline code comments.
 
 ## Usage
 
 ```
-/docs
-/docs readme
-/docs api
-/docs architecture
+/ai-sprint-docs
+/ai-sprint-docs readme
+/ai-sprint-docs api
+/ai-sprint-docs architecture
 ```
 
 ## Workflow
@@ -489,13 +489,13 @@ graph TD
 
 ## Integration with Other Commands
 
-**/code** → **/docs**
+**/ai-sprint-code** → **/ai-sprint-docs**
 - After generating code, document it
 
-**/review** → **/docs**
+**/ai-sprint-review** → **/ai-sprint-docs**
 - Review identifies missing docs
 
-**/test** → **/docs**
+**/ai-sprint-test** → **/ai-sprint-docs**
 - Tests validate doc examples work
 
 ## Success Criteria