yalla-planlisted

# /yalla-plan 4-agent adversarial planning. Produces a plan grounded in the actual codebase, challenged by a red-team, sliced into tracer bullets, mapped to public test seams, and approved by the user before any code is written. Planning must be incident-aware without becoming a universal checklist. Identify the changed workflow's success invariant, scan prior incidents/learnings for the touched subsystem, and activate only the risk gates that match the diff. Planning must also be operator-readable for non-trivial work. Apply the operator-understanding protocol (see `${CLAUDE_PLUGIN_ROOT}/knowledge/yalla/`) and choose `light`, `default`, or `deep` understanding mode based on risk. The plan should explain the business/user behavior before code details. `$REPO` and `$BASE_BRANCH` come from `.claude/YALLA.md` (`repo:` / `base_branch:`), with `$REPO` auto-detected via `gh repo view --json nameWithOwner -q .nameWithOwner` when blank and `$BASE_BRANCH` defaulting to `main`. ## Input <task_input> $ARGUMENTS </task_input> Requires a task description. If invoked from `/yalla` or `/yalla-team`, the issue number and description are already available. --- ## Step 1: Create Planning Team Before spawning agents, read: - `.claude/YALLA.md` - `${CLAUDE_PLUGIN_ROOT}/knowledge/yalla/TASK-CLASSIFICATION.md` - `${CLAUDE_PLUGIN_ROOT}/knowledge/yalla/VERTICAL-SLICES.md` - `${CLAUDE_PLUGIN_ROOT}/knowledge/yalla/TEST-SEAMS.md` - `${CLAUDE_PLUGIN_ROOT}/knowledge/yalla/ARCHITECTURE-DEPTH.md