omgkit 2.15.0 → 2.17.0

package/plugin/registry.yaml

@@ -1,9 +1,85 @@
 # OMGKIT Component Registry
-# Single Source of Truth for Agents, Skills, Commands, and Workflows
-# Version: 1.0.0
+# Single Source of Truth for Agents, Skills, Commands, Workflows, and MCPs
+# Version: 2.17.0
 # Updated: 2026-01-02
 
-version: "1.0.0"
+version: "2.17.0"
+
+# =============================================================================
+# OPTIMIZED ALIGNMENT PRINCIPLE (OAP)
+# =============================================================================
+# Core architectural rule defining component relationships.
+# See: plugin/stdrules/ALIGNMENT_PRINCIPLE.md for full documentation.
+#
+# Hierarchy (lower levels are used by higher levels):
+#   Level 0: MCPs       → Foundation layer
+#   Level 1: Commands   → Use: MCPs
+#   Level 2: Skills     → Use: Commands, MCPs
+#   Level 3: Agents     → Use: Skills, Commands, MCPs
+#   Level 4: Workflows  → Use: Agents, Skills, Commands, MCPs
+#
+# Rules:
+#   1. Format Compliance  - Use correct format for each component type
+#   2. Existence Validation - All references must point to existing components
+#   3. No Cross-Type Confusion - Don't mix agents/skills/commands
+#   4. Hierarchical Respect - Only reference lower or same level components
+#   5. Optimization - Appropriate, minimal, unique, contextual references
+# =============================================================================
+
+alignment_principle:
+  version: "1.0.0"
+  enforced: true
+  documentation: "plugin/stdrules/ALIGNMENT_PRINCIPLE.md"
+  hierarchy:
+    - level: 0
+      type: mcp
+      format: "mcp-name"
+      location: "plugin/mcp/"
+      uses: []
+    - level: 1
+      type: command
+      format: "/namespace:command-name"
+      location: "plugin/commands/<namespace>/<name>.md"
+      uses: [mcp]
+    - level: 2
+      type: skill
+      format: "category/skill-name"
+      location: "plugin/skills/<category>/<name>/SKILL.md"
+      uses: [command, mcp]
+    - level: 3
+      type: agent
+      format: "kebab-case"
+      location: "plugin/agents/<name>.md"
+      uses: [skill, command, mcp]
+    - level: 4
+      type: workflow
+      format: "category/workflow-name"
+      location: "plugin/workflows/<category>/<name>.md"
+      uses: [agent, skill, command, mcp]
+
+# =============================================================================
+# MCP SERVERS (Model Context Protocol)
+# =============================================================================
+# MCPs provide external capabilities to OMGKIT components.
+# Foundation layer of the alignment hierarchy.
+# =============================================================================
+
+mcp_servers:
+  context7:
+    description: Up-to-date library documentation
+    status: supported
+  sequential-thinking:
+    description: Multi-step reasoning
+    status: supported
+  memory:
+    description: Persistent knowledge graph
+    status: supported
+  filesystem:
+    description: Secure file operations
+    status: supported
+  playwright:
+    description: Browser automation
+    status: supported
 
 # =============================================================================
 # AGENTS
@@ -373,21 +449,7 @@ agents:
   # ---------------------------------------------------------------------------
   # SPECIALIZED AGENTS
   # ---------------------------------------------------------------------------
-  autonomous-orchestrator:
-    file: agents/autonomous-orchestrator.yaml
-    description: State-driven autonomous project execution
-    skills:
-      - autonomous/project-orchestration
-    commands:
-      - /auto:init
-      - /auto:start
-      - /auto:status
-      - /auto:next
-      - /auto:approve
-      - /auto:reject
-      - /auto:verify
-      - /auto:checkpoint
-      - /auto:resume
+  # Note: autonomous-orchestrator uses YAML format and is handled separately
 
   domain-decomposer:
     file: agents/domain-decomposer.md
@@ -466,6 +528,7 @@ skill_categories:
 # All valid command namespace prefixes
 
 command_namespaces:
+  - alignment # Alignment and dependency graph
   - auto      # Autonomous orchestration
   - context   # Context management
   - data      # Data engineering
@@ -502,15 +565,15 @@ workflows:
     commands: [/planning:plan, /dev:feature, /dev:test, /dev:review, /git:pr]
 
   development/bug-fix:
-    agents: [debugger, fullstack-developer, tester, code-reviewer, git-manager]
+    agents: [debugger, fullstack-developer, tester, git-manager]
     skills:
       - methodology/systematic-debugging
       - methodology/root-cause-tracing
       - methodology/test-driven-development
-    commands: [/dev:fix, /dev:fix-hard, /dev:test, /git:cm]
+    commands: [/dev:fix, /dev:fix-hard, /dev:fix-test, /git:cm]
 
   development/refactor:
-    agents: [architect, fullstack-developer, tester, code-reviewer, git-manager]
+    agents: [code-reviewer, fullstack-developer, tester, git-manager]
     skills:
       - methodology/verification-before-completion
       - methodology/test-driven-development
@@ -542,31 +605,31 @@ workflows:
     commands: [/planning:research, /planning:plan-detailed, /dev:feature, /dev:test, /quality:security-scan]
 
   ai-engineering/fine-tuning:
-    agents: [ml-engineer, data-engineer, tester]
+    agents: [researcher, planner, fullstack-developer, tester]
     skills:
       - ai-engineering/finetuning
       - ai-engineering/dataset-engineering
       - ai-engineering/evaluation-methodology
-    commands: [/planning:plan, /ml:train, /ml:evaluate, /dev:test]
+    commands: [/planning:plan, /dev:feature, /dev:test]
 
   ai-engineering/prompt-engineering:
-    agents: [researcher, fullstack-developer, tester]
+    agents: [researcher, tester]
     skills:
       - ai-engineering/prompt-engineering
       - ai-engineering/evaluation-methodology
-    commands: [/planning:research, /dev:feature, /dev:test]
+    commands: [/planning:research, /dev:test]
 
   ai-engineering/model-evaluation:
-    agents: [ml-engineer, researcher, tester]
+    agents: [researcher, planner, tester]
     skills:
       - ai-engineering/ai-system-evaluation
       - ai-engineering/evaluation-methodology
       - ai-engineering/dataset-engineering
-    commands: [/planning:plan, /ml:evaluate, /dev:test]
+    commands: [/planning:plan, /dev:test]
 
   # Security workflows
   security/security-audit:
-    agents: [security-auditor, fullstack-developer, docs-manager]
+    agents: [security-auditor, vulnerability-scanner, code-reviewer, fullstack-developer, docs-manager]
     skills:
       - security/owasp
       - security/security-hardening
@@ -583,7 +646,7 @@ workflows:
 
   # Database workflows
   database/schema-design:
-    agents: [database-admin, architect, fullstack-developer, tester]
+    agents: [database-admin, planner, tester]
     skills:
       - databases/database-schema-design
       - databases/postgresql
@@ -591,20 +654,20 @@ workflows:
     commands: [/planning:plan, /dev:feature, /dev:test]
 
   database/migration:
-    agents: [database-admin, fullstack-developer, tester]
+    agents: [database-admin, planner, tester]
     skills:
       - databases/database-migration
-    commands: [/planning:plan, /dev:feature, /dev:test]
+    commands: [/planning:plan, /dev:test]
 
   database/optimization:
-    agents: [database-admin, performance-engineer, tester]
+    agents: [database-admin, tester]
     skills:
       - databases/database-optimization
-    commands: [/quality:optimize, /perf:profile, /dev:test]
+    commands: [/quality:optimize, /dev:test]
 
   # API workflows
   api/api-design:
-    agents: [api-designer, architect, docs-manager, code-reviewer]
+    agents: [api-designer, planner, docs-manager, code-reviewer]
     skills:
       - backend/api-architecture
     commands: [/planning:plan, /quality:api-gen, /planning:doc, /dev:review]
@@ -618,21 +681,21 @@ workflows:
 
   # Omega workflows
   omega/10x-improvement:
-    agents: [oracle, brainstormer, fullstack-developer, tester]
+    agents: [oracle, architect, brainstormer, fullstack-developer, tester, journal-writer]
     skills:
       - omega/omega-thinking
       - omega/omega-coding
     commands: [/omega:10x, /planning:brainstorm, /dev:feature, /dev:test]
 
   omega/100x-architecture:
-    agents: [oracle, architect, researcher]
+    agents: [oracle, architect, planner, researcher]
     skills:
       - omega/omega-architecture
       - omega/omega-thinking
     commands: [/omega:100x, /planning:plan-detailed]
 
   omega/1000x-innovation:
-    agents: [oracle, researcher, brainstormer]
+    agents: [oracle, researcher, brainstormer, architect]
     skills:
       - omega/omega-thinking
       - omega/omega-architecture
@@ -640,27 +703,27 @@ workflows:
 
   # Sprint workflows
   sprint/sprint-setup:
-    agents: [sprint-master, planner]
+    agents: [sprint-master, planner, project-manager]
     skills:
       - omega/omega-sprint
     commands: [/sprint:vision-set, /sprint:backlog-add, /sprint:backlog-prioritize, /sprint:sprint-new, /sprint:sprint-start]
 
   sprint/sprint-execution:
-    agents: [sprint-master, fullstack-developer, tester, debugger]
+    agents: [sprint-master, fullstack-developer, tester, debugger, project-manager]
     skills:
       - omega/omega-sprint
       - methodology/executing-plans
     commands: [/sprint:sprint-current, /sprint:team-run, /sprint:team-status, /dev:fix, /sprint:sprint-end]
 
   sprint/sprint-retrospective:
-    agents: [sprint-master, journal-writer, docs-manager]
+    agents: [sprint-master, project-manager, journal-writer]
     skills:
       - omega/omega-sprint
     commands: [/sprint:sprint-end, /planning:doc]
 
   # Fullstack workflows
   fullstack/full-feature:
-    agents: [planner, architect, fullstack-developer, tester, code-reviewer, git-manager]
+    agents: [planner, database-admin, api-designer, ui-ux-designer, fullstack-developer, tester, code-reviewer, git-manager]
     skills:
       - methodology/writing-plans
       - databases/database-schema-design
@@ -669,7 +732,7 @@ workflows:
     commands: [/planning:plan-detailed, /dev:feature, /dev:test, /dev:review, /git:pr]
 
   fullstack/authentication:
-    agents: [architect, fullstack-developer, security-auditor, tester]
+    agents: [planner, fullstack-developer, security-auditor, tester]
     skills:
       - security/oauth
       - security/better-auth
@@ -679,21 +742,21 @@ workflows:
 
   # Quality workflows
   quality/performance-optimization:
-    agents: [performance-engineer, fullstack-developer, tester]
+    agents: [fullstack-developer, tester]
     skills:
       - ai-engineering/inference-optimization
       - databases/database-optimization
-    commands: [/quality:optimize, /perf:profile, /dev:test]
+    commands: [/quality:optimize, /dev:test]
 
   # Research workflows
   research/technology-research:
-    agents: [researcher, architect, docs-manager]
+    agents: [researcher, oracle, docs-manager]
     skills:
       - methodology/research-validation
     commands: [/planning:research, /planning:doc]
 
   research/best-practices:
-    agents: [researcher, fullstack-developer]
+    agents: [researcher, planner, fullstack-developer]
     skills:
       - methodology/research-validation
     commands: [/planning:research, /planning:plan, /dev:feature]

package/plugin/stdrules/ALIGNMENT_PRINCIPLE.md

@@ -0,0 +1,240 @@
+# Optimized Alignment Principle (OAP)
+
+**Version:** 1.0.0
+**Status:** Core Principle
+**Enforcement:** Mandatory (validated by tests)
+
+---
+
+## Overview
+
+The **Optimized Alignment Principle (OAP)** is a core architectural rule that defines how OMGKIT components relate to each other. This principle ensures consistency, maintainability, and scalability across all components.
+
+---
+
+## Component Hierarchy
+
+```
+┌─────────────────────────────────────────────────────────────────────┐
+│                     OPTIMIZED ALIGNMENT HIERARCHY                    │
+├─────────────────────────────────────────────────────────────────────┤
+│                                                                      │
+│  Level 0: MCPs (Model Context Protocol Servers)                      │
+│           └── Foundation layer, used by all other components         │
+│                                                                      │
+│  Level 1: Commands                                                   │
+│           └── Use: zero-to-many MCPs                                 │
+│           └── Format: /namespace:command-name                        │
+│                                                                      │
+│  Level 2: Skills                                                     │
+│           └── Use: zero-to-many Commands, MCPs                       │
+│           └── Format: category/skill-name                            │
+│                                                                      │
+│  Level 3: Agents                                                     │
+│           └── Use: zero-to-many Skills, Commands, MCPs               │
+│           └── Format: kebab-case name                                │
+│                                                                      │
+│  Level 4: Workflows                                                  │
+│           └── Use: zero-to-many Agents, Skills, Commands, MCPs       │
+│           └── Format: category/workflow-name                         │
+│                                                                      │
+└─────────────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## Alignment Rules
+
+### Rule 1: Format Compliance
+
+All component references MUST use the correct format:
+
+| Component | Format | Example |
+|-----------|--------|---------|
+| MCP | `mcp-name` | `context7`, `sequential-thinking` |
+| Command | `/namespace:command-name` | `/dev:feature`, `/omega:10x` |
+| Skill | `category/skill-name` | `methodology/writing-plans` |
+| Agent | `kebab-case` | `fullstack-developer` |
+| Workflow | `category/workflow-name` | `development/feature` |
+
+### Rule 2: Existence Validation
+
+All referenced components MUST exist:
+
+- Skills → Must exist in `/plugin/skills/<category>/<name>/SKILL.md`
+- Commands → Must exist in `/plugin/commands/<namespace>/<name>.md`
+- Agents → Must exist in `/plugin/agents/<name>.md`
+- Workflows → Must exist in `/plugin/workflows/<category>/<name>.md`
+- MCPs → Must be registered in `/plugin/mcp/`
+
+### Rule 3: No Cross-Type Confusion
+
+Components MUST NOT be confused with other types:
+
+- ❌ Agent names in `skills:` field
+- ❌ Skill names in `agents:` field
+- ❌ Commands without proper `/namespace:` prefix
+
+### Rule 4: Hierarchical Respect
+
+Components can only reference components from their level or below:
+
+| Component | Can Reference |
+|-----------|---------------|
+| MCP | (none - foundation layer) |
+| Command | MCPs |
+| Skill | Commands, MCPs |
+| Agent | Skills, Commands, MCPs |
+| Workflow | Agents, Skills, Commands, MCPs |
+
+### Rule 5: Optimization Requirements
+
+References should be:
+
+1. **Appropriate** - Only reference what is needed
+2. **Minimal** - Avoid redundant dependencies
+3. **Unique** - No duplicate references
+4. **Contextual** - Match the component's purpose
+
+---
+
+## Frontmatter Specifications
+
+### Skill Frontmatter
+
+```yaml
+---
+name: skill-name
+description: What the skill does
+category: category-name
+commands:          # Optional: commands this skill uses
+  - /namespace:cmd
+mcps:              # Future: MCPs this skill uses
+  - mcp-name
+---
+```
+
+### Agent Frontmatter
+
+```yaml
+---
+name: agent-name
+description: What the agent does
+tools: Tool1, Tool2
+model: inherit
+skills:            # Skills this agent uses
+  - category/skill-name
+commands:          # Commands this agent can trigger
+  - /namespace:cmd
+mcps:              # Future: MCPs this agent uses
+  - mcp-name
+---
+```
+
+### Workflow Frontmatter
+
+```yaml
+---
+name: workflow-name
+description: What the workflow does
+category: category-name
+agents:            # Agents this workflow orchestrates
+  - agent-name
+skills:            # Skills used across the workflow
+  - category/skill-name
+commands:          # Commands triggered by the workflow
+  - /namespace:cmd
+mcps:              # Future: MCPs used by the workflow
+  - mcp-name
+---
+```
+
+---
+
+## Validation
+
+### Automated Tests
+
+The alignment principle is enforced by automated tests in:
+- `tests/validation/alignment.test.js`
+- `tests/validation/format.test.js`
+- `tests/validation/existence.test.js`
+- `tests/validation/hierarchy.test.js`
+
+### Pre-Publish Check
+
+Before publishing to npm, ALL alignment tests MUST pass:
+
+```bash
+npm test
+```
+
+### CI/CD Integration
+
+GitHub Actions validates alignment on every PR.
+
+---
+
+## Examples
+
+### Correct Alignment
+
+```yaml
+# Agent: fullstack-developer.md
+skills:
+  - methodology/executing-plans      # ✓ Valid skill format
+  - languages/typescript             # ✓ Exists in skills directory
+commands:
+  - /dev:feature                     # ✓ Valid command format
+  - /dev:fix                         # ✓ Exists in commands directory
+```
+
+### Incorrect Alignment
+
+```yaml
+# WRONG - Common mistakes
+skills:
+  - planner                          # ✗ This is an agent name, not skill
+  - writing-plans                    # ✗ Missing category prefix
+  - methodology/nonexistent          # ✗ Skill doesn't exist
+
+commands:
+  - feature                          # ✗ Missing /namespace: prefix
+  - /dev/feature                     # ✗ Wrong separator (/ not :)
+```
+
+---
+
+## Future: MCP Alignment
+
+When MCP support is fully implemented:
+
+1. MCPs will be registered in `/plugin/mcp/`
+2. All components can declare `mcps:` in frontmatter
+3. Tests will validate MCP references exist
+4. Registry will track MCP-component mappings
+
+---
+
+## Enforcement
+
+This principle is:
+
+1. **Documented** - In this file and public docs
+2. **Tested** - 400+ automated tests
+3. **Required** - Must pass before publish
+4. **Versioned** - Changes tracked in changelog
+
+---
+
+## Changelog
+
+### 1.0.0 (2026-01-02)
+- Initial definition of Optimized Alignment Principle
+- Established 5 core alignment rules
+- Created comprehensive test suite
+- Added MCP future support placeholder
+
+---
+
+*Think Omega. Build Omega. Be Omega.* 🔮

package/plugin/workflows/ai-ml/experiment-cycle.md

@@ -5,7 +5,7 @@ triggers:
   - ml:experiment
 agents:
   - ml-engineer
-  - data-scientist
+  - data-engineer
 ---
 
 # Experiment Cycle Workflow

package/plugin/workflows/ai-ml/model-deployment.md

@@ -5,7 +5,7 @@ triggers:
   - ml:deploy
 agents:
   - ml-engineer
-  - site-reliability-engineer
+  - observability-engineer
 ---
 
 # Model Deployment Workflow
@@ -79,7 +79,7 @@ base_images:
 
 ### Step 3.1: Deploy to Staging
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: deploy
 environment: staging
 infrastructure:
@@ -105,7 +105,7 @@ tests:
 
 ### Step 4.1: Canary Deployment
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: deploy
 strategy: canary
 configuration:
@@ -119,7 +119,7 @@ configuration:
 
 ### Step 4.2: Shadow Deployment (Optional)
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: deploy
 strategy: shadow
 configuration:
@@ -131,7 +131,7 @@ configuration:
 
 ### Step 4.3: Full Rollout
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: promote
 after:
   - Canary success
@@ -147,7 +147,7 @@ steps:
 
 ### Step 5.1: Configure Monitoring
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: configure
 monitoring:
   - Prediction latency
@@ -163,7 +163,7 @@ dashboards:
 
 ### Step 5.2: Configure Alerts
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: configure
 alerts:
   - High error rate

package/plugin/workflows/ai-ml/monitoring-setup.md

@@ -5,7 +5,7 @@ triggers:
   - ml:monitoring
 agents:
   - ml-engineer
-  - site-reliability-engineer
+  - observability-engineer
 ---
 
 # ML Monitoring Setup Workflow
@@ -127,7 +127,7 @@ detection:
 
 ### Step 4.1: System Metrics
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: configure
 metrics:
   - Request latency (p50, p95, p99)
@@ -140,7 +140,7 @@ metrics:
 
 ### Step 4.2: SLI/SLO Definition
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: define
 slis:
   - Availability: Successful requests / Total requests
@@ -156,7 +156,7 @@ slos:
 
 ### Step 5.1: Alert Configuration
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: configure
 alert_rules:
   - model_drift_detected:
@@ -175,7 +175,7 @@ alert_rules:
 
 ### Step 5.2: Response Playbooks
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: document
 playbooks:
   - drift_detected:
@@ -196,7 +196,7 @@ playbooks:
 
 ### Step 6.1: Create Dashboards
 ```yaml
-agent: site-reliability-engineer
+agent: observability-engineer
 action: create
 dashboards:
   - model_health: