plugin-planning

DSP architecture planning structures your plugin's signal flow, core components, and parameter mapping before implementation. This Skill generates a detailed architecture.md contract by researching JUCE DSP modules and analyzing professional examples, establishing a solid foundation that prevents costly rework during development.

Plugin research identifies technical approaches, suitable JUCE DSP classes, and implementation patterns by analyzing professional examples. This Skill automates guided research to document findings in an architecture contract, ensuring your design decisions are informed and documented.

Implementation planning breaks down plugin complexity into phased development stages with clear milestones. This Skill calculates complexity metrics and generates a step-by-step plan.md, enabling systematic development without scope creep or architectural drift.

You need an existing creative brief describing your plugin's purpose and core functionality. This Skill validates the brief, then orchestrates research and planning to generate architecture and implementation contracts from that starting point.

Yes. This Skill supports any JUCE plugin type. It's designed for audio effects by example—like a tape delay—but applies equally to synthesizers, instruments, and other plugin categories requiring DSP specification and phased implementation.

Architecture planning defines signal flow, components, and parameter mapping in architecture.md. Implementation planning calculates complexity and creates phased development steps in plan.md. Both are generated together to ensure design and execution align.