plugin-builder

Plugin Builder

Philosophy

• Validate the package boundary first; make install, release, or runtime claims only after the matching gate passes.

When to Use

Use for plugin scaffold conversion, hardening, and contract validation.

Route elsewhere:

• first shell only -> [[plugin-creator]]
• install/discovery -> [[plugin-installer]]

Inputs

• source path or plugin path
• requested mode: scaffold|convert|harden
• marketplace requirements (if any)

Execution Boundaries

• Own plugin contract review, bundled hook validation, minimal remediation, validation evidence, and final hardening handoff.
• Delegate first-draft shells to [[plugin-creator]]; delegate install, projection, and runtime visibility checks to [[plugin-installer]].
• Do not execute third-party install scripts or mutate marketplace policy fields without explicit request.
• Apply the plugin design contract before release claims: small public surface, distinguishable child skills, explicit side-effect classes, and compact outputs.

For non-trivial factory work, include first_principles_gate or an explicit first_principles_gate_status: not_applicable before readiness claims.

Outputs

Return: schema_version, execution_mode, plugin_path, validation, artifacts, optional blocked_by.

schema_version: 1
execution_mode: harden
plugin_path: Plugins/example-plugin
validation:
  - command: bash Infrastructure/scripts/validation-and-linting/validate_skill_authoring_family.sh
    status: pass
artifacts:
  - Plugins/example-plugin/.codex-plugin/plugin.json
blocked_by: null

Workflow

1. Confirm mode: scaffold, convert, or harden, plus plugin source path and write authority.
2. Inspect .codex-plugin/plugin.json, bundled skills, hooks, MCP/app files, and marketplace or release requirements.
3. Run the focused validation checkpoint before changing files; classify existing failures.
4. Patch the smallest source surface that fixes manifest, hook, MCP/app, routing, or validation defects.
5. Rerun the focused gate and return exact pass, fail, or blocked evidence with the next handoff.