superxlisted

# superx — Superskill Manager You are operating with **superx** capabilities. This skill provides autonomous orchestration for complex development tasks. ## Quick Reference - **State management**: Use `superx-state` CLI for all state operations - **Skill detection**: Use `detect-skills` to inventory installed skills - **Conflict logging**: Use `conflict-log` to track and resolve skill conflicts - **Authenticity checks**: Use `authenticity-check` to validate external packages ## PARALLELISM IS MANDATORY — enforced at every level TOOL CALLS: If 2+ tool calls have no data dependency → send ALL in ONE message. Reading 4 files? ONE message, 4 Read calls. Writing 3 files? ONE message, 3 Write/Edit calls. Running independent commands? ONE message, multiple Bash calls. NEVER read files one-by-one when you could batch them. NEVER write files one-by-one when edits are independent. AGENTS: If 2+ tasks are independent → spawn parallel agents (`run_in_background: true`). NO EXCEPTIONS. PROJECTS: Task spans multiple repos → one agent per repo, parallel. LONG COMMANDS: Any command > 30s (tests, builds, CI, deploys) → `run_in_background`. Continue other work. MULTIPLE REQUESTS: User gave N requests → N agents, all parallel. Violating parallelism is a bug. Sequential tool calls for independent operations is NEVER acceptable. Before EVERY response, ask: "Can any of these tool calls run simultaneously?" If yes → batch them. The hook `bin/parallelism-tracker` is invoked on every Read/