plugin-workflow

Coordinates the end-to-end implementation of a JUCE plugin through specialized subagents and validation.

2|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/bretbouchard/plugin-freedom-system --skill plugin-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-workflow
Source: https://github.com/bretbouchard/plugin-freedom-system/tree/main/.claude/skills/plugin-workflow
Command: npx skills add https://github.com/bretbouchard/plugin-freedom-system --skill plugin-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Pure orchestrator for JUCE plugin implementation, delegating to specialized subagents and ensuring continuous validation after each stage.

Core Features & Use Cases

  • Pure Orchestrator: No direct code implementation; delegates to foundation-shell-agent, dsp-agent, and gui-agent.
  • Checkpoint & Validation: After each stage, runs enhanced runtime validation and commits state.
  • Use Case: When implementing a new JUCE plugin, this skill coordinates foundation, DSP, and GUI stages with guardrails.

Quick Start

Use /implement [PluginName] to start the staged workflow; the orchestrator coordinates stages and validations automatically.

Frequently Asked Questions about plugin-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate JUCE plugin implementation across multiple development stages?

Orchestrating JUCE plugin implementation coordinates specialized agents for foundation, DSP, and GUI stages in sequence. Use /implement [PluginName] to start the workflow; the orchestrator delegates each stage to the appropriate agent and validates output before proceeding to the next phase.

What validation happens after each stage in plugin workflow?

Enhanced runtime validation runs after each implementation stage and automatically commits state. This checkpoint process ensures each phase meets requirements before delegation to the next agent, reducing integration issues downstream.

Can I use subagents to build different parts of a JUCE plugin separately?

Yes. This orchestrator delegates foundation, DSP, and GUI implementation to specialized subagents. Each agent handles its domain independently while the orchestrator coordinates sequencing, validation, and state commits across all stages.

Do I need to write plugin code directly or does this handle implementation?

This is a pure orchestrator that does not write code directly. It delegates implementation to foundation-shell-agent, dsp-agent, and gui-agent while managing coordination, validation checkpoints, and state persistence between stages.

What happens if validation fails during plugin implementation?

The orchestrator runs enhanced runtime validation after each stage. If validation fails, the workflow halts at that checkpoint, preventing propagation of errors into subsequent stages and requiring correction before proceeding.