suno-band-manager: Instructions file for Codex

Suno Band Manager — Project Standing Orders

This file contains standing orders that apply to any LLM agent working in this repository. It is loaded automatically by Gemini CLI, Claude Code (CLAUDE.md), and Codex CLI / OpenCode (AGENTS.md) — three separate files with identical content for cross-tool compatibility.

Skill Activation Discipline (MANDATORY)

When activating any skill in this module — suno-agent-band-manager, suno-band-profile-manager, suno-style-prompt-builder, suno-lyric-transformer, suno-feedback-elicitor, or suno-playlist-sequencer — you MUST follow the "On Activation" instructions in the skill's SKILL.md exactly:

1. Execute any scripts referenced in the activation block (e.g., pre-activate.py, check-memory-health.py, validate-path.py) using your shell tool. Do not skip these — they emit dynamic menu data and pre-load required state. The menu you present to the user MUST come from the script output, not from a hardcoded approximation derived from SKILL.md text.

2. Follow the agent's own activation protocol exactly — for the suno-agent-band-manager ("Mac") agent this is the skill's On Activation block plus references/activation.md. On every waking uv run {skill-root}/scripts/pre-activate.py --wake prints, in one pass, the identity files of his sanctum (_bmad/memory/suno-agent-band-manager/) in load order — PERSONA.md, CREED.md (slim core, including the Dominion: his access boundaries), BOND.md, HOW-I-REMEMBER.md, CAPABILITIES.md — followed by the generated memory map and memory/pending.md. That output IS the load set: read it in full, and open files under memory/ only when the conversation calls for them, as HOW-I-REMEMBER.md says. Do NOT blanket-read every file under the skill's references/ directory or the sanctum's memory/ and raw/ folders. In particular, references/creed.md (~395 lines) is authored SOURCE — it seeds the sanctum's creed disciplines at First Breath and is consulted only when (re)seeding the sanctum, NOT loaded on every activation (the sanctum's PERSONA.md is seeded from assets/PERSONA-template.md). Force-loading it re-imposes the per-waking cost the lean sanctum was designed to eliminate. The agent's living identity (how it communicates) comes from the sanctum's CREED.md core and PERSONA.md, which the wake already prints.