max-lifecycle

Manage MAX project lifecycle tasks including creation, tracking, switching, and test checklists.

41|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/taylorbrook/MAX-MSP_CC_Framework --skill max-lifecycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: max-lifecycle
Source: https://github.com/taylorbrook/MAX-MSP_CC_Framework/tree/main/.claude/skills/max-lifecycle
Command: npx skills add https://github.com/taylorbrook/MAX-MSP_CC_Framework --skill max-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates and centralizes MAX project lifecycle tasks—creation, status tracking, project switching, versioning, and manual test checklist generation—so developers and sound designers do not need to manually edit project files or track progress across multiple directories.

Core Features & Use Cases

  • Project scaffolding: Create a new project directory structure and an initial .maxpat file so users can open work immediately in MAX.
  • Package configuration and gating: Guide package selection, enforce extraction requirements for community packages, and save package selections to config.json.
  • Status and version tracking: Read and update status.md, manage semver versions via versions.json, and switch the active project reliably.
  • Test protocol execution: Generate manual test checklists from generated patches and save test results into test-results/ for verification and audit.
  • Use Case: Start a new synth project, select BEAP and Vizzie, generate patches via specialist agents, produce a manual test checklist for the generated files, and record the results while bumping the project version.

Quick Start

Use the max-lifecycle skill to create a new project, configure packages, and generate a manual test checklist for the generated patches.

Frequently Asked Questions about max-lifecycle

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

FAQPage Schema
How do I manage project lifecycle and versioning for Max/MSP development workflows?

Max/MSP project lifecycle management involves scaffolding new project directories, tracking status via status.md, and applying semver versioning through versions.json. This Skill automates creation, status tracking, project switching, and version bumping so developers avoid manually editing project files across multiple directories.

Can I configure community packages like BEAP or Vizzie when creating a new Max project?

Yes, Max project scaffolding includes guided package configuration where you select community packages like BEAP or Vizzie. The system enforces extraction requirements for selected packages, runs extraction scripts, and saves your package selections directly to the project's config.json file for immediate use.

How do I generate manual test checklists for generated .maxpat patch files?

Manual test checklists for .maxpat files are generated from the patches created during project scaffolding. The system produces a structured testing protocol that you execute manually, then saves the recorded test results into a dedicated test-results/ directory for verification and audit purposes.

What files and directory access does Max project lifecycle automation require?

Max project lifecycle automation requires read and write access to src/maxpat/project.py and src/maxpat/testing.py, access to the patches/.active-project.json file for active project tracking, and the ability to execute package extraction scripts when community packages are selected during configuration.

Does this approach support switching between multiple active Max projects?

Yes, active project switching is a core lifecycle feature that reliably updates the .active-project.json file. This allows developers and sound designers to switch context between different Max projects without manually tracking which directory or configuration file is currently active.

When should I use automated Max project scaffolding instead of manual directory setup?

Automated Max project scaffolding is best when you need consistent directory structures, initial .maxpat files, and integrated package configuration without manual file editing. It centralizes status tracking and versioning, making it ideal for developers managing multiple Max/MSP projects simultaneously.