plugin-planning

Generate DSP architecture and implementation contracts for JUCE plugins.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manual DSP architecture and implementation planning is complex, time-consuming, and error-prone. This skill automates the creation of critical contracts (architecture.md, plan.md) that guide plugin development, ensuring a solid, well-researched foundation for any new audio effect or instrument.

Core Features & Use Cases

  • Automated DSP Architecture: Generates detailed DSP architecture specifications (architecture.md) including core components, signal flow, algorithm details, and JUCE API mappings.
  • Implementation Planning: Creates a comprehensive plan.md complete with a complexity assessment, strategic phase breakdowns for development, and clear test criteria for each phase.
  • Use Case: Kickstart development for any new audio plugin idea by generating all foundational research and planning documents in minutes, instead of days of manual effort. It turns your concept into an actionable blueprint for the engineering team.

Quick Start

Plan the DSP architecture and implementation for my new 'TapeDelay' plugin.

Frequently Asked Questions about plugin-planning

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

FAQPage Schema
How do I automate DSP architecture planning for a JUCE audio plugin?

DSP architecture planning automates the creation of detailed specifications for audio plugin design, including core components, signal flow, and algorithm details. This skill generates `architecture.md` contracts that map your creative brief into a structured blueprint, eliminating manual design work and ensuring consistency across plugin development.

What should I include in an implementation plan for audio plugin development?

An implementation plan for audio plugins breaks down development into strategic phases with complexity assessments and test criteria for each stage. This skill generates `plan.md` documents that transform your plugin concept into actionable engineering tasks, phased milestones, and verification checkpoints.

Can I use this for planning plugin development from a creative brief?

Yes. This skill is designed for Stage 0 planning when you have a creative brief and need architecture specification. It performs precondition checks, assesses complexity, and generates foundational contracts that guide the engineering team from concept through implementation.

What's the difference between architecture and implementation planning for plugins?

Architecture planning specifies DSP components, signal flow, and JUCE API mappings; implementation planning adds phase breakdowns, complexity assessment, and test criteria. Together they form complementary contracts that define what to build and how to build it systematically.

How does this skill reduce plugin development time?

Manual DSP architecture and planning takes days of research and documentation. This skill generates all foundational research documents—`architecture.md` and `plan.md`—in minutes, giving your team a research-backed blueprint to start development immediately instead of debating design decisions.

Do I need existing plugin code to use the planning tool?

No. This skill operates during Stage 0 planning when you have only a creative brief or plugin concept. It generates architecture and implementation contracts from your idea, making it ideal for kickstarting development before any code exists.