mc-workflow

Routes music composition requests through a staged ARR-SPEC arrangement specification workflow.

128|16|Updated Sep 17, 2026
One-click install
npx skills add https://github.com/jtydhr88/music-composition-skills --skill mc-workflow-jtydhr88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mc-workflow
Source: https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-workflow
Command: npx skills add https://github.com/jtydhr88/music-composition-skills --skill mc-workflow-jtydhr88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated music often sounds generic because no deliberate compositional choices were made. This Skill replaces prompt guessing with a structured ARR-SPEC arrangement specification—key, tempo, bar-accurate section map, harmony, instrumentation entry/exit, energy curve, vocal delivery, and mix intent—that is compiled into Suno prompts, ABC scores for YuE2, or MIDI, and then used as the acceptance baseline for the generated audio. ## Core Features & Use Cases - S0–S7 Stage Workflow: Gates each phase from intent definition through skeleton, material development, harmony, arrangement, vocal/mix intent, compilation, generation, and acceptance, with explicit pass criteria per stage. - Skill Routing & Boundary Table: Maps every compositional decision to exactly one owning skill (harmony, form, orchestration, vocal direction, style layers, etc.) so no two skills claim the same decision. - 20-Point Self-Audit (SPEC-LINT): A manual checklist that counters AI-generation defaults such as uniform 8-bar sections, monotonically rising energy, grid-locked timing, and identical chorus repeats. - Use Case: Ask for a city pop track; the agent fills an ARR-SPEC with asymmetric bar counts, a descending energy point before the final chorus, per-instrument push/pull timing offsets, and a style prompt, then compiles it for Suno or YuE2 and checks the result field-by-field against the spec. ## Quick Start Ask the agent to compose a new song from a brief and have it load this workflow first to produce a complete ARR-SPEC before any generation.

Frequently Asked Questions about mc-workflow

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

FAQPage Schema
How do I write a music arrangement spec for Suno or YuE2?▼

Fill in the ARR-SPEC template starting with the intent gate (one thing, two reference tracks, listener situation, emotional arc), then define form, harmony in dual roman-numeral and letter notation, arrangement roster, vocal design, and mix intent. The render section compiles the spec into a Suno style prompt or ABC score for YuE2.

What is an ARR-SPEC in AI music generation?▼

An ARR-SPEC is a YAML arrangement specification serving four purposes: handoff document, A/B test subject, compilation source for Suno/YuE2/MIDI/MusicXML, and acceptance baseline. It records key, tempo, bar-accurate sections, chords, instrument entry and exit, energy curve, and vocal delivery.

Why does AI-generated music sound generic and how do I fix it?▼

Generic output results from unmade choices: equal 8-bar sections, monotonically rising energy, grid-locked timing, and identical chorus repeats. The 20-point self-audit forces explicit decisions against each default, such as requiring at least one energy drop, one subtraction event, and nonzero push/pull timing offsets.

Can I mix two music styles like rap and Chinese pop in one spec?▼

Yes, using the style_layers field with one base style and overlay styles, where each layer signs ownership of specific dimensions like groove, harmony, or vocal delivery. Every dimension must have exactly one owner, and a fusion_note must explain why the combination works.

Which music generation backend follows a spec most precisely?▼

YuE2 and the symbolic ABC/MIDI path honor key, tempo, meter, bars, and harmony exactly, because YuE2 can synthesize audio directly from an injected ABC score. Suno treats most fields only as hints, so control comes from prompt information density plus best-of-N selection.

What should I do when generated music does not match the spec?▼

First separate two questions: whether the backend followed the spec (compliance rate) and whether the result has machine fingerprints (AI-tell audit). Check backends.yaml for fields the backend declares as honors:none, fix compilation issues, revise the spec, and regenerate before using listening-based rework.