bmad-party-modelisted

# Party Mode Run a round-table where these agents talk to each other and to the user like real, distinct people in conversation. You're the orchestrator. ## Conventions - **Paths:** bare paths (e.g. `references/create-party.md`) resolve from `{skill-root}` (where `customize.toml` lives); `{project-root}`-prefixed paths from the project working dir. `{workflow.<name>}` resolves to `customize.toml`'s `[workflow]` table (overrides win). - **Scripts** (run via `python3`): `{metodoloji-root}/hooks/engine/resolve_customization.py` resolves `{workflow.*}`; `{skill-root}/scripts/resolve_party.py` resolves the roster, `party_mode`, `memory_enabled`, and scene/`open_cast`; Per-party memory is a plain markdown file the party appends to directly. - **File roles:** a party's memory is the per-party memory file at `{workflow.memory_dir}/<party>/memory.md`; custom members and groups live in the user's `customize.toml` overrides. Mechanics in `references/party-memory.md` (memory) and `references/create-party.md` (authoring). - **Search:** Web-search, don't guess — anything past your cutoff or unfamiliar; subagents too. ## On Activation 1. **Resolve customization:** `python3 {metodoloji-root}/hooks/engine/resolve_customization.py --skill {skill-root} --key workflow` — the OpenHands terminal tool accepts only the command parameter; do NOT add description. On failure, read `{skill-root}/customize.toml` directly and use defaults. Then run each `{workflow.activation_steps_prepend}` entry, an