You say what kind of work this is. Super Agent decides which SDLC agents run, in what order, behind which gates, and what “done” means. Same product, eleven contracts.
A mode is your intent, not a model name. Pick one and it is authoritative for that run — no classifier quietly swaps your /dev for something slower.
super agent composer
/dev add a timezone field to the account settings form
›mode chip pinned to the run · command token stripped from the task text
you choose
the mode — your situation, urgency, working style
it composes
the agents, their order, parallelism and gates
then it routes
each agent to the engine and model that fits
Build it, spec it, fix it, design it, or think hard about it. These five cover almost every day of product work. The pipelines below are each mode’s contract — the orchestrator still drops optional steps that don’t earn their latency on a given run.
Development
A decided, bounded change — built, reviewed, released.
For work whose requirements are already clear: change a setting, add a field, adjust behavior, make a focused UI update. Lean, not careless.
default agents
optional · Test, when risk or repo policy calls for it
Specification
A rough idea becomes an approved, buildable spec.
For when the goal is real but the scope, behavior and solution are not settled yet. It explores alternatives, exposes assumptions and converges.
default agents
optional · Security and Performance for hard constraints
Defect
Reproduce it, root-cause it, fix it, keep it fixed.
For a reproducible defect, regression or test failure. It reproduces before it edits, names the cause instead of masking the symptom, and keeps the fix narrow.
default agents
optional · Discovery, Security or Performance by blast radius
Interface
A polished, responsive, accessible UI change — implemented.
For work where UI/UX quality is the point, and the expected outcome is shipped interface, not a mockup or a recommendation.
default agents
optional · Architect, Test and Performance
High-stakes
Ambiguous, cross-system work where confidence beats speed.
For the changes you would normally block out a week for. It inspects broadly, compares alternatives, documents tradeoffs and validates assumptions first.
default agents
optional · UX & Accessibility and Documentation
Emergencies, upkeep, audits, performance, releases — and one deliberate speed override for when you have already made every decision yourself.
Speed override
Already decided and scoped? Skip the review pass.
A deliberate speed override for changes you have fully specified yourself, where an independent review is overhead rather than safety.
default agents
optional · None — the absence is the point
Upkeep
Dependencies, config, cleanup, small reliability wins.
Narrow, low-ambiguity technical upkeep that preserves externally observable behavior unless you explicitly ask to change it.
default agents
optional · Security, Documentation, Release & Verify
Emergency
Contain a live outage, then restore, then investigate.
For an active production emergency — outage, attack, leaked credential, severe degradation, data-loss risk. Containment comes first.
default agents
optional · Discovery, Performance and Review
Read-only review
Prioritized, evidence-backed findings. Nothing changes.
For when you want understanding and recommendations rather than a diff. It stays read-only and separates evidence from inference.
default agents
optional · Discovery and UX & Accessibility
Measured improvement
Move a number: latency, throughput, cost, reliability.
Measure first, find the actual bottleneck, and never trade away correctness or maintainability without saying so out loud.
default agents
optional · Discovery and Release & Verify
Release
Built already? Validate, release, verify.
For finished implementation work. It does not expand scope — only release-blocking corrections get made.
default agents
optional · Security and Performance
/auto isn’t an eleventh contract — it’s the router. It weighs the request, resolves to one explicit mode before anything executes, tells you why it chose that one, and snapshots the decision on the run. You can override it in one click.
And when you do pick explicitly, that wins. If your request can’t safely satisfy the mode you chose, Super Agent explains the mismatch and recommends a different one — it never silently switches contracts on you.
what it weighs
exploratory, read-only, implementation-ready or release-ready?
is production actively on fire right now?
ambiguity, system breadth, reversibility, blast radius
is this a defect or an intended behavior change?
security, privacy, data and operational risk
is a measurable optimization the actual outcome?
›resolved: /debug — reproducible failure, narrow blast radius, regression protection required
Modes change; the underlying SDLC capabilities stay stable. Every mode is just a different composition of these — some in sequence, some in parallel, some omitted when the risk allows it.
Clarifies the problem, constraints, current behavior, affected users and success criteria.
Reproduces the failure, inspects evidence, isolates the cause, proposes the smallest sound fix.
Defines boundaries, data flow, interfaces, tradeoffs, migrations and implementation structure.
Interaction behavior, information hierarchy, states, responsive behavior, accessibility requirements.
Implements the approved change while preserving the behavior around it.
Proportionate automated and manual validation, including regression coverage.
Threats, permissions, secrets, data exposure and security-sensitive implementation details.
Baselines plus latency, throughput, resource use, scalability and cost.
Independent pass on correctness, maintainability, scope, risk and test adequacy.
Decisions, specifications, operational guidance and user-facing behavior, written down.
Deploys through your configured release path and verifies the resulting environment.
A mode describes the current state, not the permanent category of a conversation. When the outcome changes, a new run starts under the right contract — linked to everything that came before it.
spec approved and the work is bounded
spec approved but complex or high-risk
you approved the remediation
the fix landed, the follow-up improvement is next
service restored, now do it properly
the interface is implemented and reviewed
Reaching an implementation-ready spec never auto-authorizes product code. Approving it starts a linked run with its own immutable mode snapshot and plan — and changing your composer selection only affects the next run, never an active one.
Speed modes exist because the floor never moves. These four rules apply identically to the fastest and the most paranoid contract in the catalog.
Selecting a mode never grants broader authority than your actual request. Destructive, production, financial and externally visible actions keep every approval they had.
A mode may add validation. It may never bypass a required check, a repository rule, or a permission — /fast and /incident included.
The /audit mode changes nothing. If you want the findings fixed, that is a separate run you start deliberately.
Requested mode, resolved mode, agent plan, optional-agent reasoning, gates, linked artifacts and verification status — all persisted, all snapshotted for resume.
Every hour your subscriptions sit unused is shipped software you didn’t get. Wake them up.
