module-planning

Generate architecture.md and plan.md contracts for VCV Rack modules.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/davidorex/vcv-rack-module-creation-framework --skill module-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: module-planning
Source: https://github.com/davidorex/vcv-rack-module-creation-framework/tree/main/.claude/skills/module-planning
Command: npx skills add https://github.com/davidorex/vcv-rack-module-creation-framework --skill module-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill handles Stages 0-1 (Research and Planning) for VCV Rack module development, creating foundational contracts (architecture.md, plan.md) that guide implementation.

Core Features & Use Cases

  • Stage 0: Research to draft DSP architecture and reference approaches
  • Stage 1: Planning to generate architecture and implementation plan
  • Provides templates and guidance to ensure consistency across stages

Quick Start

/plan [ModuleName] to begin planning and contract creation

Frequently Asked Questions about module-planning

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

FAQPage Schema
How do I plan VCV Rack module architecture before implementation?

Planning module architecture involves creating immutable architecture contracts and implementation roadmaps during Stages 0-1 of development. This Skill generates architecture.md and plan.md documents from your creative brief, establishing a template-driven workflow that guides all downstream implementation work.

What's the best way to document DSP module design decisions early?

Document design decisions through structured architecture contracts that capture research findings, DSP approach references, and implementation strategy. This Skill produces deterministic planning artifacts suitable for version control, ensuring consistency and traceability across your module development stages.

Can I use planning templates to enforce consistency across module projects?

Yes. This Skill applies template-driven workflows with precondition checks to enforce consistent planning across modules. It updates resume state files and module status tracking, making it suitable for teams managing multiple VCV Rack module projects with shared development standards.

How do I transition from research to implementation planning for audio modules?

Stage 0 handles research—drafting DSP architecture and evaluating reference approaches. Stage 1 converts research into actionable planning artifacts. This Skill bridges both stages, generating architecture contracts and implementation plans that serve as the foundation for moving into development.

What planning artifacts should I commit to version control for module projects?

Commit architecture.md and plan.md as immutable contracts, along with updated resume state files and module status records. These deterministic artifacts provide a clear record of design decisions and implementation strategy, enabling effective collaboration and project tracking.