omgkit 2.24.1 → 2.24.3

package/README.md

@@ -37,9 +37,9 @@ All coordinated through **Omega-level thinking** - a framework for finding break
 | Component | Count | Description |
 |-----------|-------|-------------|
 | **Agents** | 41 | Specialized AI team members with distinct roles |
-| **Commands** | 151 | Slash commands for every development task |
-| **Workflows** | 67 | Complete development processes from idea to deploy |
-| **Skills** | 157 | Domain expertise modules across 24 categories |
+| **Commands** | 160 | Slash commands for every development task |
+| **Workflows** | 69 | Complete development processes from idea to deploy |
+| **Skills** | 161 | Domain expertise modules across 24 categories |
 | **Modes** | 10 | Behavioral configurations for different contexts |
 | **Archetypes** | 14 | Project templates for autonomous development |
 
@@ -88,6 +88,53 @@ OMGKIT brings agile methodology to AI-assisted development:
 - **Sprints**: Time-boxed development cycles
 - **AI Team**: Autonomous execution with human oversight
 
+### 4. Testing Automation (New)
+
+OMGKIT includes a comprehensive testing automation system:
+
+#### Auto-Generate Test Tasks
+When you create a feature, OMGKIT automatically generates corresponding test tasks:
+
+```yaml
+# workflow.yaml
+testing:
+  auto_generate_tasks: true
+  required_test_types:
+    - unit
+    - integration
+```
+
+Feature tasks automatically spawn test tasks based on feature type (API → Contract tests, UI → Snapshot tests, etc.)
+
+#### Enforce Tests Before Done
+No task can be marked "done" without passing tests:
+
+```yaml
+testing:
+  enforcement:
+    level: standard  # soft | standard | strict
+  blocking:
+    on_test_failure: true
+    on_coverage_below_minimum: true
+```
+
+#### Coverage Gates
+Set minimum and target coverage thresholds:
+
+```yaml
+testing:
+  coverage_gates:
+    unit:
+      minimum: 80
+      target: 90
+    integration:
+      minimum: 60
+      target: 75
+    overall:
+      minimum: 75
+      target: 85
+```
+
 ---
 
 ## Installation
@@ -222,7 +269,7 @@ Agents are specialized AI team members, each with distinct expertise and respons
 
 ---
 
-## Commands (151)
+## Commands (160)
 
 Commands are slash-prefixed actions organized by namespace.
 
@@ -260,10 +307,13 @@ Commands are slash-prefixed actions organized by namespace.
 ### Quality (`/quality:*`)
 
 ```bash
-/quality:security-scan  # Scan for vulnerabilities
+/quality:security-scan   # Scan for vulnerabilities
 /quality:refactor <file> # Improve code structure
 /quality:optimize <file> # Performance optimization
-/quality:lint           # Run linting
+/quality:lint            # Run linting
+/quality:verify-done     # Verify test requirements before completion
+/quality:coverage-check  # Check coverage against gates
+/quality:test-plan       # Generate comprehensive test plan
 ```
 
 ### Omega (`/omega:*`)
@@ -370,7 +420,7 @@ Commands are slash-prefixed actions organized by namespace.
 
 ---
 
-## Workflows (67)
+## Workflows (69)
 
 Workflows are orchestrated sequences of agents, commands, and skills.
 
@@ -383,6 +433,12 @@ Workflows are orchestrated sequences of agents, commands, and skills.
 | `development/refactor` | Code improvement and restructuring |
 | `development/code-review` | Comprehensive code review |
 
+### Testing Automation (New)
+
+| Workflow | Description |
+|----------|-------------|
+| `testing/automated-testing` | End-to-end testing automation with task generation, enforcement, and coverage gates |
+
 ### AI Engineering
 
 | Workflow | Description |
@@ -454,7 +510,7 @@ Workflows are orchestrated sequences of agents, commands, and skills.
 
 ---
 
-## Skills (157)
+## Skills (161)
 
 Skills are domain expertise modules organized in 24 categories.
 
@@ -498,7 +554,7 @@ Based on Chip Huyen's "Designing ML Systems" and Stanford CS 329S:
 | `ml-systems/robust-ai` | Reliability, monitoring, drift detection |
 | `ml-systems/deployment-paradigms` | Batch vs real-time vs streaming |
 
-### Methodology (17 skills)
+### Methodology (19 skills)
 
 | Skill | Description |
 |-------|-------------|
@@ -507,6 +563,8 @@ Based on Chip Huyen's "Designing ML Systems" and Stanford CS 329S:
 | `methodology/debugging` | Systematic debugging approach |
 | `methodology/code-review` | Review standards and checklists |
 | `methodology/tdd` | Test-driven development |
+| `methodology/test-task-generation` | Auto-generate test tasks from features |
+| `methodology/test-enforcement` | Enforce tests before task completion |
 
 ### Frameworks (10 skills)
 
@@ -735,7 +793,7 @@ If any sync issue is detected (missing pages, wrong counts, broken links), the v
 
 ## Validation & Testing
 
-OMGKIT has 5700+ automated tests ensuring system integrity.
+OMGKIT has 7300+ automated tests ensuring system integrity.
 
 ### Run Tests
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "omgkit",
-  "version": "2.24.1",
-  "description": "Omega-Level Development Kit - AI Team System for Claude Code. 41 agents, 156 commands, 159 skills, 68 workflows.",
+  "version": "2.24.3",
+  "description": "Omega-Level Development Kit - AI Team System for Claude Code. 41 agents, 160 commands, 161 skills, 69 workflows.",
   "keywords": [
     "claude-code",
     "ai",

package/plugin/agents/sprint-master.md

@@ -6,6 +6,9 @@ model: inherit
 skills:
   - omega/omega-sprint
   - methodology/dispatching-parallel-agents
+  - methodology/test-task-generation
+  - methodology/test-enforcement
+  - devops/workflow-config
 commands:
   - /sprint:init
   - /sprint:sprint-new
@@ -198,20 +201,20 @@ Generates:
 
 ### Task Type Routing
 
-| Task Type | Primary Agent | Support Agents |
-|-----------|---------------|----------------|
-| feature | fullstack-developer | planner, tester |
-| bugfix | debugger | scout, tester |
-| research | oracle | researcher, scout |
-| design | architect | planner |
-| security | security-auditor | vulnerability-scanner |
-| docs | docs-manager | - |
-| test | tester | debugger |
-| review | code-reviewer | - |
-| deploy | git-manager | cicd-manager |
-| refactor | fullstack-developer | scout, code-reviewer |
-| optimize | fullstack-developer | architect |
-| brainstorm | brainstormer | oracle |
+| Task Type | Primary Agent | Support Agents | Auto-Generate Tests? |
+|-----------|---------------|----------------|---------------------|
+| feature | fullstack-developer | planner, tester | ✅ Yes |
+| bugfix | debugger | scout, tester | ✅ Yes (regression) |
+| research | oracle | researcher, scout | ❌ No |
+| design | architect | planner | ❌ No |
+| security | security-auditor | vulnerability-scanner | ✅ Yes (security) |
+| docs | docs-manager | - | ❌ No |
+| test | tester | debugger | ❌ No (is test) |
+| review | code-reviewer | - | ❌ No |
+| deploy | git-manager | cicd-manager | ❌ No |
+| refactor | fullstack-developer | scout, code-reviewer | ✅ Yes |
+| optimize | fullstack-developer | architect | ✅ Yes (perf) |
+| brainstorm | brainstormer | oracle | ❌ No |
 
 ### Assignment Protocol
 
@@ -231,15 +234,201 @@ Generates:
    - Balance workload
    - Ensure coverage
 
-4. SET CONTEXT
+4. AUTO-GENERATE TEST TASKS (NEW)
+   - Read workflow.yaml testing config
+   - If auto_generate_tasks: true
+   - Create corresponding TEST-XXX tasks
+   - Assign to tester agent
+
+5. SET CONTEXT
    - Provide relevant files
    - Share dependencies
    - Define success criteria
+   - Include test requirements
 
-5. MONITOR EXECUTION
+6. MONITOR EXECUTION
    - Track progress
    - Handle blockers
    - Coordinate handoffs
+   - Enforce tests before completion
+```
+
+---
+
+## Testing Automation Integration
+
+### Configuration Loading
+
+At sprint start, read `.omgkit/workflow.yaml` for testing configuration:
+
+```yaml
+# .omgkit/workflow.yaml
+testing:
+  enforcement:
+    level: standard  # soft | standard | strict
+  auto_generate_tasks: true
+  coverage_gates:
+    unit:
+      minimum: 80
+      target: 90
+    integration:
+      minimum: 60
+      target: 75
+  required_test_types:
+    - unit
+    - integration
+  blocking:
+    on_test_failure: true
+    on_coverage_below_minimum: true
+```
+
+### Auto Test Task Generation
+
+When `auto_generate_tasks: true`, automatically create test tasks:
+
+```
+FEATURE TASK CREATED:
+  TASK-042: Implement user authentication
+
+AUTO-GENERATED TEST TASKS:
+  TEST-042-UNIT: Unit tests for auth service
+  TEST-042-INT: Integration tests for auth flow
+  TEST-042-SEC: Security tests for auth (if auth feature)
+
+TASK LINKING:
+  TASK-042.tests = [TEST-042-UNIT, TEST-042-INT, TEST-042-SEC]
+  TASK-042.blocked_by = TEST-042-* (all must pass)
+```
+
+### Feature Type → Test Type Mapping
+
+| Feature Type | Auto-Generated Tests |
+|--------------|---------------------|
+| API Endpoint | Unit + Integration + Contract |
+| UI Component | Unit + Snapshot + Accessibility |
+| Database | Unit + Integration + Migration |
+| Auth/Security | Unit + Integration + Security |
+| Business Logic | Unit + Property-based |
+| External Integration | Unit + Integration + Contract |
+
+### Test Task Template
+
+```markdown
+## TEST-XXX: [Test Description]
+
+**Parent Task**: TASK-XXX
+**Type**: [unit | integration | e2e | security | performance]
+**Priority**: Same as parent
+
+### Acceptance Criteria
+- [ ] All tests pass
+- [ ] Coverage ≥ minimum threshold
+- [ ] No skipped critical tests
+- [ ] Test isolation verified
+
+### Test Scope
+- Functions/components to test
+- Edge cases to cover
+- Security scenarios (if applicable)
+```
+
+### Enforcement Levels
+
+#### Soft Enforcement
+```
+- Warn when completing without tests
+- Allow override with justification
+- Log for retrospective
+- No blocking
+```
+
+#### Standard Enforcement (Default)
+```
+- Block task completion without tests
+- Require minimum coverage
+- Allow emergency override with approval
+- Create follow-up tasks for overrides
+```
+
+#### Strict Enforcement
+```
+- Block ALL completion without full test suite
+- Require coverage above target
+- No overrides allowed
+- Auto-reject PRs without tests
+```
+
+### Definition of Done (with Testing)
+
+Before marking ANY task as DONE, verify:
+
+```
+DEFINITION OF DONE CHECKLIST:
+├── Code
+│   ├── [x] Implementation complete
+│   ├── [x] Code review passed
+│   └── [x] No lint errors
+│
+├── Tests (MANDATORY)
+│   ├── [x] Test tasks created
+│   ├── [x] All tests passing
+│   ├── [x] Coverage ≥ minimum
+│   └── [x] No skipped critical tests
+│
+├── Documentation
+│   ├── [x] Code documented
+│   └── [x] API docs updated (if API)
+│
+└── Ready for merge
+```
+
+### Completion Blocking
+
+```
+User: "Mark TASK-042 as done"
+
+Sprint Master checks:
+├── Has test tasks? → Yes (TEST-042-UNIT, TEST-042-INT)
+├── TEST-042-UNIT status? → ✅ Complete
+├── TEST-042-INT status? → ❌ In Progress
+└── Block completion
+
+Response: "Cannot mark TASK-042 as done.
+          TEST-042-INT is still in progress.
+
+          Test Status:
+          ✅ TEST-042-UNIT: Passed (45 tests, 92% coverage)
+          🔄 TEST-042-INT: In Progress
+
+          Complete all test tasks first, or use /quality:verify-done for details."
+```
+
+### Override Protocol
+
+```
+User: "Override test requirement for TASK-042"
+
+Sprint Master checks:
+├── Enforcement level? → Standard
+├── Override allowed? → Yes
+├── Justification required? → Yes
+
+Response: "Override requested for TASK-042.
+
+          Please provide:
+          1. Reason for override
+          2. Risk assessment
+          3. Follow-up plan for tests
+
+          Note: This will be logged and reviewed in retrospective."
+
+User: "Hotfix for production - tests will be added in TASK-043"
+
+Sprint Master:
+├── Log override with justification
+├── Create follow-up task: TASK-043 (Add tests for TASK-042)
+├── Mark TASK-042 as done with override flag
+└── Add to retrospective items
 ```
 
 ---
@@ -464,6 +653,12 @@ When blocker detected:
 - `/spawn [agent] [task]` - Run agent in parallel
 - `/spawn:collect` - Collect parallel results
 
+### Testing Commands
+- `/quality:verify-done` - Verify test requirements before completion
+- `/quality:coverage-check` - Check coverage against gates
+- `/quality:test-plan` - Generate test plan for feature
+- `/dev:feature-tested [desc]` - Create feature with auto-generated tests
+
 ### Omega Commands
 - `/init` - Initialize Omega mode
 - `/10x [task]` - Find 10x approach

package/plugin/commands/dev/feature-tested.md

@@ -0,0 +1,208 @@
+---
+name: Feature Tested
+description: Create a feature with automatically generated test tasks. Ensures every implementation task has corresponding test coverage before the feature can be marked complete.
+category: dev
+related_skills:
+  - methodology/test-task-generation
+  - methodology/test-enforcement
+  - methodology/executing-plans
+related_commands:
+  - /quality:test-plan
+  - /quality:verify-done
+  - /dev:feature
+  - /dev:test
+allowed-tools: Task, Read, Write, Bash, Grep, Glob
+---
+
+# /dev:feature-tested
+
+Build a feature with automatically generated test tasks. This command ensures comprehensive test coverage by creating test tasks alongside implementation tasks.
+
+## Usage
+
+```bash
+/dev:feature-tested <feature-description>
+/dev:feature-tested "Add user authentication" --coverage 90
+/dev:feature-tested "Payment processing" --test-types unit,integration,e2e
+```
+
+## Options
+
+| Option | Description | Default |
+|--------|-------------|---------|
+| `--coverage` | Minimum coverage target | 80% |
+| `--test-types` | Required test types | unit,integration |
+| `--tdd` | Use TDD approach (tests first) | false |
+| `--strict` | Strict enforcement (no overrides) | false |
+
+## How It Works
+
+### 1. Feature Analysis
+Analyzes the feature description to determine:
+- Feature type (API, UI, business logic, etc.)
+- Required test types
+- Coverage targets
+- Acceptance criteria
+
+### 2. Task Generation
+Creates implementation tasks AND corresponding test tasks:
+
+```
+Feature: Add user profile API
+
+Generated Tasks:
+┌─────────────────────────────────────────────────────────────┐
+│ Implementation Tasks                                         │
+├─────────────────────────────────────────────────────────────┤
+│ ☐ TASK-001: Create profile database schema                  │
+│ ☐ TASK-002: Implement profile service                       │
+│ ☐ TASK-003: Create profile API endpoints                    │
+│ ☐ TASK-004: Add input validation                            │
+└─────────────────────────────────────────────────────────────┘
+
+┌─────────────────────────────────────────────────────────────┐
+│ Test Tasks (Auto-Generated)                                  │
+├─────────────────────────────────────────────────────────────┤
+│ ☐ TEST-001: Unit tests for profile service                  │
+│ ☐ TEST-002: Integration tests for profile API               │
+│ ☐ TEST-003: Contract tests for API schema                   │
+│ ☐ TEST-004: Security tests for profile endpoints            │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### 3. Enforcement
+- Cannot mark feature as "done" until all test tasks complete
+- Coverage must meet minimum threshold
+- All tests must pass
+
+## Output Format
+
+```
+╔══════════════════════════════════════════════════════════════╗
+║              FEATURE WITH TESTS CREATED                       ║
+╚══════════════════════════════════════════════════════════════╝
+
+Feature: Add user profile API
+ID: FEAT-042
+Coverage Target: 90%
+
+┌─────────────────────────────────────────────────────────────┐
+│ Implementation Tasks (4)                                     │
+├─────────────────────────────────────────────────────────────┤
+│ TASK-001: Create profile database schema          [Pending] │
+│ TASK-002: Implement profile service               [Pending] │
+│ TASK-003: Create profile API endpoints            [Pending] │
+│ TASK-004: Add input validation                    [Pending] │
+└─────────────────────────────────────────────────────────────┘
+
+┌─────────────────────────────────────────────────────────────┐
+│ Test Tasks (4) - Auto-Generated                              │
+├─────────────────────────────────────────────────────────────┤
+│ TEST-001: Unit tests for profile service          [Pending] │
+│   → Coverage target: 90% for src/services/profile.ts       │
+│   → Test file: tests/unit/services/profile.test.ts         │
+│                                                              │
+│ TEST-002: Integration tests for profile API       [Pending] │
+│   → Coverage target: 75% for API endpoints                 │
+│   → Test file: tests/integration/api/profile.int.test.ts   │
+│                                                              │
+│ TEST-003: Contract tests for API schema           [Pending] │
+│   → Validates: Request/response schemas                    │
+│   → Test file: tests/contract/profile.contract.test.ts     │
+│                                                              │
+│ TEST-004: Security tests for profile endpoints    [Pending] │
+│   → Checks: Auth, injection, XSS                           │
+│   → Test file: tests/security/profile.security.test.ts     │
+└─────────────────────────────────────────────────────────────┘
+
+┌─────────────────────────────────────────────────────────────┐
+│ Completion Requirements                                      │
+├─────────────────────────────────────────────────────────────┤
+│ ☐ All implementation tasks complete                         │
+│ ☐ All test tasks complete                                   │
+│ ☐ Overall coverage ≥ 90%                                    │
+│ ☐ All tests passing                                         │
+│ ☐ No security vulnerabilities                               │
+│ ☐ Code review approved                                      │
+└─────────────────────────────────────────────────────────────┘
+
+Next: Start with TASK-001 or use --tdd to write tests first
+```
+
+## TDD Mode
+
+With `--tdd` flag, tests are created and executed first:
+
+```bash
+/dev:feature-tested "Add user profile API" --tdd
+```
+
+Flow:
+1. Generate test tasks first
+2. Write failing tests (Red)
+3. Implement to pass tests (Green)
+4. Refactor (Refactor)
+5. Verify coverage
+
+## Workflow Integration
+
+### Sprint Planning
+```bash
+/sprint:sprint-new
+# Add feature with tests
+/dev:feature-tested "User profile management"
+```
+
+### Daily Development
+```bash
+# Check what's needed
+/quality:verify-done FEAT-042
+
+# Work on implementation
+# Work on tests
+# Verify completion
+/quality:verify-done FEAT-042
+```
+
+### Feature Completion
+```bash
+# Attempt to complete
+/quality:verify-done FEAT-042
+
+# If all requirements met:
+# ✅ Feature FEAT-042 marked as DONE
+
+# If requirements not met:
+# ❌ Cannot complete: Coverage 75% below 90% minimum
+```
+
+## Examples
+
+### Basic feature with tests
+```bash
+/dev:feature-tested "Add user authentication"
+```
+
+### With strict coverage
+```bash
+/dev:feature-tested "Payment processing" --coverage 95 --strict
+```
+
+### TDD approach
+```bash
+/dev:feature-tested "Shopping cart" --tdd
+```
+
+### Specific test types
+```bash
+/dev:feature-tested "Admin dashboard" --test-types unit,e2e,security
+```
+
+## Comparison with /dev:feature
+
+| Aspect | /dev:feature | /dev:feature-tested |
+|--------|-------------|---------------------|
+| Test tasks | Manual | Auto-generated |
+| Enforcement | Soft | Hard (blocking) |
+| Coverage tracking | Manual | Automatic |
+| Completion check | Manual | Automatic |