jstack-subagentslisted

# JStack Subagents Treat this command as explicit user approval to deploy subagents when multi-agent tools are available. Default behavior: 1. Keep the Lead Engineer accountable for scope, synthesis, implementation decisions, verification, and handoff. 2. Deploy the right specialist team for the task, normally two or three specialists. 3. Use Code Investigator plus Reviewer for normal feature or bug work. 4. Add QA Engineer when verification risk is meaningful. 5. Use Architect for architecture, API, database, or integration-sensitive work. 6. Use Product / UX Reviewer for UI and product work. 7. Use Security Engineer for security or compliance work. 8. Use DevOps / Release Engineer for production, deploy, and release work. 9. Use Quant / Backtest Reviewer for trading, EA, quant, or backtest work. 10. Specialists are read-only by default. Only assign edits to a Builder with a disjoint write scope. Before dispatch, require a coordination packet: - `goal` - `riskClass` array - `mode: smart-subagents` - `rolesUsed` and `rolesNotUsed` - `readWritePermissions` and `fileOwnershipMap` - actual `capabilityPlan` and exact per-role `capabilityIds` - `evidenceContract`, `conflictRule`, and `stopConditions` - `verificationGate` and `handoffGate` Pass the actual packet object to `jstack_dispatch_check`; a boolean packet claim is invalid. Use `jstack_plan` with `team_mode="smart-subagents"` and the resolved learning mode: explicit `off`, `coach`, or `assessment`, otherwise `embedded`