idumb-plugin

Validates iDumb plugin functionality through systematic pivotal trials and stress testing. Ensures all success criteria are met with concrete evidence. Use when testing any iDumb component or before considering implementation complete.

Guides the implementation of the iDumb plugin reboot following the 8-phase pivotal trial methodology. Use when building TypeScript engines, tools, and hooks for intelligent AI governance.

This skill should be used when the user asks to "orchestrate", "delegate", "coordinate agents", "enforce hierarchy", "mindful delegation", "hierarchical thinking", "chain of command", or "orchestrator patterns". Essential for coordinators and high-governance agents to maintain delegation integrity.

Complete iDumb governance protocols - hierarchical delegation, validation patterns, context anchoring, and expert-skeptic mode guidelines

Meta-skill for idumb-builder agent to transform confusing specifications into structured iDumb workflow modules with checkpoints, validation, and integration points. Use when creating reusable workflows, handling overlapping specs, or generating governance modules under .idumb/modules/. This skill enforces the iDumb vision: spec-driven development, context-first validation, drift detection, and hierarchical coordination.

This skill should be used when the user asks to "ingest meta-framework", "transform framework to idumb", "classify framework patterns", "create self-upgrading module", "meta-learning", "framework synthesis", "automated governance enhancement", "pattern extraction", "hierarchical framework analysis", or "iterative framework learning". Essential for idumb-builder to consume external frameworks like BMAD and transform them into iDumb-compatible governance patterns.

This skill should be used when the user asks to "ingest meta-framework", "transform framework to idumb", "classify framework patterns", "create self-upgrading module", "meta-learning", "framework synthesis", "automated governance enhancement", "pattern extraction", "hierarchical framework analysis", or "iterative framework learning". Essential for idumb-builder to consume external frameworks like BMAD and transform them into iDumb-compatible governance patterns.

CODE-QUALITY package for iDumb framework - enforces error handling standards, cross-platform compatibility, documentation completeness, and consistent error message formats. Use when: validating bash scripts, checking tool error handling, reviewing documentation coverage, or ensuring cross-platform compatibility.

Complete iDumb governance protocols - hierarchical delegation, validation patterns, context anchoring, and expert-skeptic mode guidelines

META-ORCHESTRATOR for iDumb framework - master coordinator that activates appropriate validation skills (security, code-quality, performance, validation, governance) based on context, operation type, and risk level. Use when: coordinating multi-skill validation, determining which checks to run, or orchestrating framework-level operations.

PERFORMANCE package for iDumb framework - optimizes file scanning efficiency, implements memory leak prevention, enforces cleanup policies, and validates iteration limits. Use when: optimizing grep operations, managing validation records, preventing memory accumulation, or detecting performance bottlenecks.

PROJECT package for validating user projects - works in greenfield and brownfield, ensures governance without blocking development

SECURITY package for iDumb framework - validates bash scripts against injection vulnerabilities, enforces path sanitization, prevents permission bypass, and detects information disclosure patterns. Use when: creating bash scripts, validating file operations, checking agent permissions, scanning for secrets, or preventing race conditions.

META package for stress-testing the iDumb framework itself - validates agent coordination, integration completeness, and regression prevention

Comprehensive validation and gap detection skill for iDumb meta-framework - iterative assessment, automated checklist generation, and self-healing workflows

Monitors agent responses for style compliance and provides correction hints

OpenCode plugin conflict prevention - loading order, deduplication rules, naming conventions, and troubleshooting. Use when publishing plugins or diagnosing plugin conflicts.

OpenCode TUI safety guidelines - avoid console.log pollution, use proper logging, interact with TUI events, understand 60 FPS rendering constraints, and prevent performance degradation. Use when creating or modifying OpenCode plugins/tools that interact with the Terminal UI.

OpenCode plugin development compliance - hook system, event subscriptions, tool interception, SDK usage, storage boundaries, and plugin architecture. Use when creating, modifying, or validating OpenCode plugins to ensure compliance with official plugin capabilities and limitations.

OpenCode custom tool development compliance - tool definition with Zod schemas, execute function patterns, context parameters, error handling, and TUI-safe logging. Use when creating or modifying custom tools for OpenCode plugins.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes