amcs-plan-generator

Generate a deterministic execution plan from a Song Design Spec.

1|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/miethe/MeatyMusic --skill amcs-plan-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amcs-plan-generator
Source: https://github.com/miethe/MeatyMusic/tree/main/.claude/skills/workflow/plan
Command: npx skills add https://github.com/miethe/MeatyMusic --skill amcs-plan-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts a Song Design Spec (SDS) into a deterministic execution plan that guides all downstream workflow nodes (STYLE, LYRICS, PRODUCER, COMPOSE). It extracts section structure, calculates target word counts, defines evaluation targets, and creates ordered work objectives for downstream nodes.

Core Features & Use Cases

  • Section extraction: Parses SDS to ensure at least one Chorus and proper hook strategy requirements
  • Word count planning: Converts lines to target word counts, respecting max_lines
  • Evaluation targets: Pull thresholds from genre blueprint to form plan.
  • Work objectives: Produces an ordered list for downstream nodes

Quick Start

  1. Provide an SDS and seed
  2. Run the PLAN skill
  3. Read outputs: plan with section_order, target_word_counts, evaluation_targets, work_objectives

Frequently Asked Questions about amcs-plan-generator

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

FAQPage Schema
How do I generate a deterministic execution plan from a Song Design Spec?

The PLAN skill generates a deterministic execution plan by parsing your SDS to extract section order, calculate proportional word-count targets, load genre-based evaluation thresholds from a blueprint, and produce SHA-256 hashed work objectives for downstream AMCS nodes. No randomness or time-based operations are applied, ensuring reproducible results.

What validation does the plan generator apply to song structure?

The skill validates that your SDS includes at least one Chorus and meets hook strategy requirements before proceeding. This ensures the song structure is compliant with downstream workflow constraints before generating section order and work objectives.

How are target word counts calculated from an SDS?

Target word counts are derived by converting section line counts to words, respecting the max_lines constraint, then scaling proportionally across all sections. The skill computes per-section targets and a total_word_count output for consistent downstream node execution.

Can I reuse the same plan for multiple song iterations?

Yes. The plan includes a SHA-256 hash computed from deterministic logic, enabling you to verify and reuse identical plans across runs without regenerating. The _hash field provides provenance tracking for reproducible workflow execution.

What does the blueprint integration provide to the plan?

The BlueprintReaderService supplies genre-based evaluation targets and thresholds that the skill loads into the plan. These targets guide downstream STYLE, LYRICS, PRODUCER, and COMPOSE nodes with genre-specific constraints and success criteria.

What output structure should I expect from the plan generator?

The plan outputs section_order (ordered sections), target_word_counts (per-section targets), evaluation_targets (genre thresholds), work_objectives (ordered downstream tasks), total_word_count (aggregated), and _hash (SHA-256 provenance identifier) for downstream workflow nodes.