aigent-team 0.2.0 → 0.4.0

package/dist/index.d.ts

@@ -10,6 +10,15 @@ interface ReferenceFile {
     description: string;
     whenToRead: string;
     content: string;
+    tags?: string[];
+}
+type GovernanceStatus = 'draft' | 'active' | 'review-needed' | 'deprecated';
+interface GovernanceMetadata {
+    version?: string;
+    owner?: string;
+    status?: GovernanceStatus;
+    lastReviewedAt?: string;
+    deprecatedReason?: string;
 }
 interface SkillFile {
     id: string;
@@ -17,6 +26,42 @@ interface SkillFile {
     description: string;
     trigger: string;
     content: string;
+    useCases?: string[];
+    tags?: string[];
+    governance?: GovernanceMetadata;
+}
+interface ExampleFile {
+    id: string;
+    name: string;
+    description: string;
+    skillRef?: string;
+    content: string;
+    tags?: string[];
+}
+interface OutputContract {
+    id: string;
+    name: string;
+    description: string;
+    skillRef?: string;
+    format?: string;
+    content: string;
+    tags?: string[];
+}
+interface ScriptFile {
+    id: string;
+    name: string;
+    description: string;
+    language: string;
+    content: string;
+    tags?: string[];
+}
+interface AssetFile {
+    id: string;
+    name: string;
+    description: string;
+    format: string;
+    content: string;
+    tags?: string[];
 }
 interface TechStackConfig {
     languages: string[];
@@ -49,6 +94,10 @@ interface AgentDefinition {
     references: ReferenceFile[];
     rulesContent: string;
     skills: SkillFile[];
+    examples: ExampleFile[];
+    outputContracts: OutputContract[];
+    scripts: ScriptFile[];
+    assets: AssetFile[];
     globs?: string[];
 }
 declare const ConfigSchema: z.ZodObject<{
@@ -141,10 +190,13 @@ declare const ConfigSchema: z.ZodObject<{
     }>>;
     output: z.ZodOptional<z.ZodObject<{
         directory: z.ZodOptional<z.ZodString>;
+        pluginDir: z.ZodOptional<z.ZodString>;
     }, "strip", z.ZodTypeAny, {
         directory?: string | undefined;
+        pluginDir?: string | undefined;
     }, {
         directory?: string | undefined;
+        pluginDir?: string | undefined;
     }>>;
 }, "strip", z.ZodTypeAny, {
     projectName: string;
@@ -176,6 +228,7 @@ declare const ConfigSchema: z.ZodObject<{
     } | undefined;
     output?: {
         directory?: string | undefined;
+        pluginDir?: string | undefined;
     } | undefined;
 }, {
     projectName: string;
@@ -207,6 +260,7 @@ declare const ConfigSchema: z.ZodObject<{
     } | undefined;
     output?: {
         directory?: string | undefined;
+        pluginDir?: string | undefined;
     } | undefined;
 }>;
 type AigentTeamConfig = z.infer<typeof ConfigSchema>;

package/dist/index.js

@@ -8,7 +8,7 @@ import {
   configExists,
   loadAgents,
   loadConfig
-} from "./chunk-U3NGK2UZ.js";
+} from "./chunk-OMO7OMKB.js";
 
 // src/index.ts
 function defineConfig(config) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aigent-team",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "description": "Cross-platform AI agent team plugin for Claude Code, Cursor, Codex, and Antigravity",
   "type": "module",
   "main": "./dist/index.js",

package/templates/teams/ba/assets/story-template.md

@@ -0,0 +1,49 @@
+---
+name: User Story Template
+description: Standard template for writing user stories with acceptance criteria
+format: markdown
+tags: [ba, requirements, template]
+---
+
+# User Story Template
+
+## Story: [STORY-ID] [Title]
+
+**Priority:** P0 / P1 / P2 / P3
+**Complexity:** S / M / L / XL
+**Epic:** [Epic name or link]
+
+### Description
+
+**As a** [user role]
+**I want to** [goal or action]
+**So that** [business value or benefit]
+
+### Context
+[Background information, business motivation, or technical context]
+
+### Acceptance Criteria
+
+#### AC-1: [Short description]
+- **Given** [precondition]
+- **When** [action]
+- **Then** [expected result]
+
+#### AC-2: [Short description]
+- **Given** [precondition]
+- **When** [action]
+- **Then** [expected result]
+
+### Out of Scope
+- [Explicitly excluded items]
+
+### Dependencies
+- [Related stories, APIs, or external systems]
+
+### Non-Functional Requirements
+- **Performance:** [if applicable]
+- **Security:** [if applicable]
+- **Accessibility:** [if applicable]
+
+### Notes
+[Additional context, design links, or discussion points]

package/templates/teams/ba/examples/acceptance-criteria.md

@@ -0,0 +1,39 @@
+---
+name: Acceptance Criteria Example
+description: Example of well-structured acceptance criteria for a user story
+skillRef: story-decomposition
+tags: [ba, requirements]
+---
+
+# Example: Acceptance Criteria
+
+## User Story
+
+**As a** logged-in user
+**I want to** filter search results by date range
+**So that** I can find relevant content from a specific time period
+
+## Acceptance Criteria
+
+### AC-1: Date range picker is displayed
+- **Given** the user is on the search results page
+- **When** they click the "Filter" button
+- **Then** a date range picker appears with "Start Date" and "End Date" fields
+
+### AC-2: Valid date range filters results
+- **Given** the date range picker is visible
+- **When** the user selects a start date of "2025-01-01" and end date of "2025-06-30"
+- **And** clicks "Apply"
+- **Then** only results within that date range are displayed
+- **And** the active filter is shown as a chip/tag
+
+### AC-3: Invalid date range shows error
+- **Given** the date range picker is visible
+- **When** the user selects a start date after the end date
+- **Then** an inline error message reads "Start date must be before end date"
+- **And** the "Apply" button is disabled
+
+### AC-4: Clear filter restores all results
+- **Given** a date range filter is active
+- **When** the user clicks the "×" on the filter chip
+- **Then** the filter is removed and all results are displayed again

package/templates/teams/ba/output-contracts/user-story-rubric.md

@@ -0,0 +1,33 @@
+---
+name: User Story Quality Rubric
+description: Self-validation checklist for BA agent user story output
+format: checklist
+tags: [ba, quality]
+---
+
+# Output Contract: User Story
+
+Before delivering a user story, validate against this rubric:
+
+## Structure (all required)
+- [ ] Follows "As a [role], I want [goal], so that [benefit]" format
+- [ ] Has a unique story ID
+- [ ] Includes priority (P0/P1/P2/P3)
+- [ ] Includes estimated complexity (S/M/L/XL)
+
+## Acceptance Criteria (all required)
+- [ ] At least 2 acceptance criteria per story
+- [ ] Each AC uses Given/When/Then format
+- [ ] Covers the happy path
+- [ ] Covers at least one error/edge case
+- [ ] No implementation details in AC (behavior only)
+
+## Completeness
+- [ ] Dependencies on other stories are listed
+- [ ] Out-of-scope items are explicitly noted
+- [ ] Non-functional requirements are included if applicable (performance, security)
+
+## Quality Signals
+- [ ] Story is independently testable
+- [ ] Story delivers user-visible value
+- [ ] AC are specific enough that two developers would implement the same behavior

package/templates/teams/ba/references/acceptance-criteria.md

@@ -1,3 +1,10 @@
+---
+title: Writing Acceptance Criteria
+description: Patterns and frameworks for writing testable, unambiguous acceptance criteria in Given/When/Then format.
+whenToRead: When writing or reviewing acceptance criteria for user stories
+tags: [ba, acceptance-criteria, given-when-then, testing]
+---
+
 # Writing Acceptance Criteria
 
 ## Format: Given / When / Then

package/templates/teams/ba/references/api-contract-design.md

@@ -1,3 +1,10 @@
+---
+title: API Contract Design
+description: Guidelines for defining API contracts between frontend and backend before implementation begins.
+whenToRead: When designing or reviewing API contracts for FE/BE alignment
+tags: [ba, api-contract, integration, specification]
+---
+
 # API Contract Design
 
 ## Purpose

package/templates/teams/ba/references/requirements-analysis.md

@@ -1,3 +1,10 @@
+---
+title: Requirements Analysis
+description: Structured framework for breaking down business requirements into scope, assumptions, and dependencies.
+whenToRead: When analyzing a new feature request or breaking down business requirements
+tags: [ba, requirements, analysis, scoping]
+---
+
 # Requirements Analysis
 
 ## Analysis Framework

package/templates/teams/ba/references/user-story-mapping.md

@@ -1,3 +1,10 @@
+---
+title: User Story Mapping
+description: Techniques for organizing user stories into activity hierarchies and prioritizing MVP scope.
+whenToRead: When mapping user journeys, decomposing epics, or prioritizing stories for MVP
+tags: [ba, user-stories, story-mapping, prioritization]
+---
+
 # User Story Mapping
 
 ## Story Map Structure

package/templates/teams/ba/skills/requirement-validation.md

@@ -1,3 +1,14 @@
+---
+name: Requirement Validation
+description: Validate that requirements are complete, consistent, feasible, and testable before development begins
+trigger: When validating that requirements are complete, consistent, and implementable before development starts.
+useCases:
+  - BA Agent reviewing a new feature spec before handing off to engineering
+  - Lead Agent gating a sprint to ensure all stories meet quality criteria
+  - QA Agent verifying that acceptance criteria are testable and unambiguous
+tags: [ba, requirements, validation, quality]
+---
+
 # Skill: Requirement Validation
 
 **Trigger**: When validating that requirements are complete, consistent, and implementable before development starts.

package/templates/teams/ba/skills/story-decomposition.md

@@ -1,3 +1,19 @@
+---
+name: Story Decomposition
+description: Break epics into implementable user stories using vertical slicing and INVEST criteria
+trigger: When breaking an epic or large feature into implementable user stories.
+useCases:
+  - BA Agent decomposing epics for sprint planning
+  - Lead Agent requesting story breakdown for a feature
+  - BA Agent preparing a backlog refinement session with the team
+tags: [ba, planning, user-stories, decomposition]
+governance:
+  version: "1.1.0"
+  owner: ba-team
+  status: review-needed
+  lastReviewedAt: "2025-01-10"
+---
+
 # Skill: Story Decomposition
 
 **Trigger**: When breaking an epic or large feature into implementable user stories.

package/templates/teams/be/references/api-design.md

@@ -1,3 +1,10 @@
+---
+title: API Design
+description: Standards for RESTful URL structure, HTTP status codes, and API endpoint conventions.
+whenToRead: When designing or implementing REST API endpoints
+tags: [be, api, rest, http]
+---
+
 # API Design
 
 ## RESTful URL Structure

package/templates/teams/be/references/async-processing.md

@@ -1,3 +1,10 @@
+---
+title: Async Processing
+description: Guidelines for queue-based job design, idempotency, and handling long-running background tasks.
+whenToRead: When implementing background jobs, message queues, or asynchronous workflows
+tags: [be, async, queues, jobs]
+---
+
 # Async Processing
 
 ## When to Use Queues

package/templates/teams/be/references/auth-security.md

@@ -1,3 +1,10 @@
+---
+title: Authentication & Security
+description: Standards for JWT authentication, authorization, password storage, and common security hardening practices.
+whenToRead: When implementing authentication, authorization, or reviewing security concerns
+tags: [be, security, authentication, authorization]
+---
+
 # Authentication & Security
 
 ## Authentication

package/templates/teams/be/references/caching.md

@@ -1,3 +1,10 @@
+---
+title: Caching
+description: Cache strategy selection, key design patterns, and invalidation approaches for backend services.
+whenToRead: When adding or reviewing caching layers for performance optimization
+tags: [be, caching, performance, redis]
+---
+
 # Caching
 
 ## Strategy Selection

package/templates/teams/be/references/database.md

@@ -1,3 +1,10 @@
+---
+title: Database
+description: Schema standards, indexing rules, query optimization, and migration best practices for relational databases.
+whenToRead: When designing schemas, writing migrations, or optimizing database queries
+tags: [be, database, schema, indexing]
+---
+
 # Database
 
 ## Schema Standards

package/templates/teams/be/references/error-handling.md

@@ -1,3 +1,10 @@
+---
+title: Error Handling & Resilience
+description: Patterns for domain error hierarchies, HTTP status mapping, and building resilient backend services.
+whenToRead: When implementing error handling, retry logic, or resilience patterns
+tags: [be, error-handling, resilience, reliability]
+---
+
 # Error Handling & Resilience
 
 ## Domain Error Hierarchy

package/templates/teams/be/references/observability.md

@@ -1,3 +1,10 @@
+---
+title: Observability
+description: Standards for structured logging, distributed tracing, and metrics collection across backend services.
+whenToRead: When adding logging, tracing, metrics, or setting up monitoring for a service
+tags: [be, observability, logging, monitoring]
+---
+
 # Observability
 
 ## Three Pillars

package/templates/teams/be/references/review-checklist.md

@@ -1,3 +1,10 @@
+---
+title: Backend Review Checklist
+description: Comprehensive checklist covering API contracts, data layer, security, and performance for backend code reviews.
+whenToRead: When reviewing backend pull requests or performing pre-merge quality checks
+tags: [be, code-review, checklist, quality]
+---
+
 # Backend Review Checklist
 
 ### API Contract

package/templates/teams/be/references/testing.md

@@ -1,3 +1,10 @@
+---
+title: Backend Testing
+description: Test level guidelines covering unit, integration, and end-to-end testing strategies for backend services.
+whenToRead: When writing or reviewing backend tests at any level of the test pyramid
+tags: [be, testing, unit-tests, integration-tests]
+---
+
 # Backend Testing
 
 ## Test Levels

package/templates/teams/be/skills/api-load-test.md

@@ -1,3 +1,14 @@
+---
+name: API Load Test
+description: Validate endpoint performance under load using k6, autocannon, or hey and analyze bottlenecks
+trigger: When validating endpoint performance under load, before a release with traffic expectations, or investigating latency issues.
+useCases:
+  - BE Agent benchmarking a new endpoint before production release
+  - QA Agent running performance regression tests in CI
+  - DevOps Agent investigating latency spikes in a production service
+tags: [be, performance, load-testing, benchmarking]
+---
+
 # Skill: API Load Test
 
 **Trigger**: When validating endpoint performance under load, before a release with traffic expectations, or investigating latency issues.

package/templates/teams/be/skills/database-migration.md

@@ -1,3 +1,14 @@
+---
+name: Database Migration
+description: Safely execute schema changes including new tables, column modifications, index additions, and data migrations
+trigger: When schema changes are needed — new tables, column changes, index additions, or data migrations.
+useCases:
+  - BE Agent adding a new table or column for a feature
+  - Lead Agent reviewing a migration plan for a large-table schema change
+  - DevOps Agent coordinating a zero-downtime migration in production
+tags: [be, database, migration, schema]
+---
+
 # Skill: Database Migration
 
 **Trigger**: When schema changes are needed — new tables, column changes, index additions, or data migrations.

package/templates/teams/devops/references/ci-cd.md

@@ -1,3 +1,10 @@
+---
+title: CI/CD Pipeline Design
+description: Pipeline architecture patterns, stage ordering, caching strategies, and deployment automation.
+whenToRead: When designing, reviewing, or troubleshooting CI/CD pipelines
+tags: [devops, ci-cd, automation, deployment]
+---
+
 # CI/CD Reference
 
 ## Pipeline Stages

package/templates/teams/devops/references/cost-optimization.md

@@ -1,3 +1,10 @@
+---
+title: Cost Optimization
+description: Right-sizing strategies, reserved capacity planning, storage lifecycle policies, and budget alerting.
+whenToRead: When reviewing cloud spend, right-sizing resources, or setting up cost controls
+tags: [devops, cost, cloud, optimization]
+---
+
 # Cost Optimization Reference
 
 ## Right-Sizing

package/templates/teams/devops/references/disaster-recovery.md

@@ -1,3 +1,10 @@
+---
+title: Disaster Recovery
+description: RPO/RTO tier definitions, backup strategies, failover procedures, and chaos engineering practices.
+whenToRead: When planning DR strategy, configuring backups, or running failover tests
+tags: [devops, disaster-recovery, backups, failover]
+---
+
 # Disaster Recovery Reference
 
 ## RPO / RTO Tiers

package/templates/teams/devops/references/docker.md

@@ -1,3 +1,10 @@
+---
+title: Docker Best Practices
+description: Base image selection, multi-stage builds, layer optimization, and container security hardening.
+whenToRead: When writing or reviewing Dockerfiles and container configurations
+tags: [devops, docker, containers, images]
+---
+
 # Docker Reference
 
 ## Base Image Selection

package/templates/teams/devops/references/infrastructure-as-code.md

@@ -1,3 +1,10 @@
+---
+title: Infrastructure as Code
+description: Terraform directory structure, state management, module design, and resource tagging standards.
+whenToRead: When writing or reviewing Terraform/IaC configurations and modules
+tags: [devops, terraform, iac, modules]
+---
+
 # Infrastructure as Code Reference
 
 ## Terraform Directory Structure

package/templates/teams/devops/references/kubernetes.md

@@ -1,3 +1,10 @@
+---
+title: Kubernetes Operations
+description: Namespace strategy, resource management, probes, PodDisruptionBudgets, network policies, and secrets handling.
+whenToRead: When creating or reviewing Kubernetes manifests and cluster configurations
+tags: [devops, kubernetes, orchestration, manifests]
+---
+
 # Kubernetes Reference
 
 ## Namespace Strategy

package/templates/teams/devops/references/monitoring.md

@@ -1,3 +1,10 @@
+---
+title: Monitoring and Observability
+description: Metrics, logs, and traces instrumentation with golden signal alerting and runbook standards.
+whenToRead: When setting up monitoring, defining alerts, or instrumenting services
+tags: [devops, monitoring, observability, alerting]
+---
+
 # Monitoring and Observability Reference
 
 ## Three Pillars

package/templates/teams/devops/references/review-checklist.md

@@ -1,3 +1,10 @@
+---
+title: DevOps Review Checklist
+description: Comprehensive PR review checklist covering IaC, Docker, Kubernetes, CI/CD, security, and monitoring changes.
+whenToRead: When reviewing pull requests that include infrastructure or deployment changes
+tags: [devops, review, checklist, quality]
+---
+
 # DevOps Review Checklist
 
 Use this checklist when reviewing infrastructure, deployment, and platform

package/templates/teams/devops/references/security.md

@@ -1,3 +1,10 @@
+---
+title: Infrastructure Security
+description: Least-privilege IAM patterns, network segmentation, secrets rotation, image scanning, and audit logging.
+whenToRead: When configuring IAM policies, network rules, secrets management, or security scanning
+tags: [devops, security, iam, secrets]
+---
+
 # Security Reference
 
 ## Least Privilege IAM

package/templates/teams/devops/scripts/health-check.sh

@@ -0,0 +1,35 @@
+---
+name: Service Health Check
+description: Script to verify service health endpoints after deployment
+language: bash
+tags: [devops, deployment, monitoring]
+---
+
+#!/usr/bin/env bash
+# Service Health Check Script
+# Usage: ./health-check.sh <base-url> [timeout-seconds]
+
+set -euo pipefail
+
+BASE_URL="${1:?Usage: $0 <base-url> [timeout-seconds]}"
+TIMEOUT="${2:-30}"
+INTERVAL=2
+ELAPSED=0
+
+echo "Checking health at: ${BASE_URL}/health"
+
+while [ "$ELAPSED" -lt "$TIMEOUT" ]; do
+  STATUS=$(curl -s -o /dev/null -w "%{http_code}" "${BASE_URL}/health" 2>/dev/null || echo "000")
+
+  if [ "$STATUS" = "200" ]; then
+    echo "Service is healthy (HTTP 200) after ${ELAPSED}s"
+    exit 0
+  fi
+
+  echo "Status: ${STATUS} — retrying in ${INTERVAL}s (${ELAPSED}/${TIMEOUT}s)"
+  sleep "$INTERVAL"
+  ELAPSED=$((ELAPSED + INTERVAL))
+done
+
+echo "ERROR: Service did not become healthy within ${TIMEOUT}s"
+exit 1

package/templates/teams/devops/skills/health-check.md

@@ -1,3 +1,14 @@
+---
+name: Health Check Verification
+description: Verify service health after deployment by checking endpoints, dependencies, resources, and critical paths
+trigger: When verifying service health after deployment, setting up monitoring, or debugging availability issues.
+useCases:
+  - DevOps Agent running post-deployment verification checks
+  - QA Agent confirming service readiness before running E2E tests
+  - DevOps Agent triaging an availability alert in production
+tags: [devops, monitoring, health-check, deployment]
+---
+
 # Skill: Health Check Verification
 
 **Trigger**: When verifying service health after deployment, setting up monitoring, or debugging availability issues.

package/templates/teams/devops/skills/rollback-procedure.md

@@ -1,3 +1,18 @@
+---
+name: Rollback Procedure
+description: Revert a deployment due to errors, performance regression, or unexpected behavior in production
+trigger: When a deployment needs to be reverted due to errors, performance regression, or unexpected behavior in production.
+useCases:
+  - DevOps Agent reverting a broken deployment in production
+  - Lead Agent coordinating an emergency rollback during an incident
+  - DevOps Agent executing a planned rollback after failed canary analysis
+tags: [devops, rollback, deployment, incident-response]
+governance:
+  version: "0.9.0"
+  owner: devops-team
+  status: draft
+---
+
 # Skill: Rollback Procedure
 
 **Trigger**: When a deployment needs to be reverted due to errors, performance regression, or unexpected behavior in production.