superx

Autonomous superskill manager — the main orchestrator agent for complex development tasks. Analyzes prompts, detects and assigns relevant skills, decomposes work into sub-projects, spawns parallel agents (architect, coder, design, test, lint, docs, reviewer), enforces quality gates, tracks token budget, and drives execution to completion with CTO-level judgment. Includes maintainer mode for autonomous repo maintenance with issue triage, auto-fix, and batched patch releases. Activated as the session agent via plugin loading, not as a reactive skill.

install

source · Clone the upstream repo

git clone https://github.com/randomittin/superx

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/randomittin/superx "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/superx" ~/.claude/skills/randomittin-superx-superx && rm -rf "$T"

manifest: skills/superx/SKILL.md

source content

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

Available Commands

```
/superx:level <1|2|3>
```
— Set autonomy level
```
/superx:status
```
— Show current project state
```
/superx:maintain
```
— Toggle maintainer mode
```
/superx:reflect
```
— Force conflict reflection pass

Reference Documentation

For detailed guidance on specific topics:

Planning Pipeline

superx uses complexity-based routing to decide how much planning overhead a task needs:

Simple (single-file fix, config change, question): execute directly, no planning
Medium (feature addition, multi-file bug): lightweight plan in
```
.planning/PLAN.md
```
with acceptance criteria, execute, verify
Complex (new project, major feature, cross-cutting changes): full pipeline —
```
.planning/CONTEXT.md
```
for codebase analysis,
```
.planning/PLAN-{phase}.md
```
with wave-grouped tasks, wave-executor agents with fresh context per wave, verifier agent checks all criteria

The

.planning/

directory at the project root is the state system. Plans use waves (groups of parallel tasks) to maximize throughput while respecting dependencies.

Full Specification

For the complete design specification (paths relative to plugin root, use

${CLAUDE_SKILL_DIR}/../..

to resolve):