plugin-dev-validation

You validate plugin components by enforcing domain criteria that check frontmatter requirements, structure organization, and security patterns to guide automated checks and human reviews.

Required frontmatter fields include name, description, and contextual fields necessary to drive discovery and configuration during the plugin component artifact review process.

Security and quality guardrails encode rules to prevent ambiguous or unsafe artifact evaluation, promoting repeatable reviews by standardizing checks across corrector and planner workflows.

Domain validation criteria apply directly to Skills, Agents, Hooks, Commands, and Plugin Structure workflows, standardizing reviews across all these component types within corrector processes.

Validation criteria align with planner, runbook, corrector, and handoff stages to standardize reviews, ensuring consistent artifact evaluation throughout the entire plugin development workflow.

Automated validation focuses on frontmatter, structure, and security patterns but requires human review for complex contextual judgments, ensuring repeatable and safe artifact evaluation across workflows.