The host handles models and coding
Claude Code, Cursor, Codex, and Trae still handle browsing, tool calls, file edits, and runtime execution.
AI can write code. Super Dev helps teams ship it properly.
Use Super Dev inside Claude Code, Cursor, Codex, Trae, and similar tools to move from requirement to delivery through one governed path: repo map, impact analysis, research, the three core docs, approval, spec, frontend validation, quality gates, and delivery standards.
- Works across major CLI and IDE hosts
- Pulls AI coding back into a governed workflow
- Produces auditable engineering delivery assets
Install with pip or uv, then run super-dev in the terminal to open the host onboarding flow.
- Hosts
- 17
- Pipeline phases
- 12
- Critical gates
- 3
- License
- MIT
Current host coverage
Why Super Dev
Keep the host coding. Let Super Dev straighten the workflow.
Once installed, the host follows one governed path from research to delivery.
Super Dev handles process governance
The host moves through research, the three core docs, approval, spec, implementation, quality, and delivery.
The output is auditable delivery assets
PRD, architecture, UI/UX, spec, runtime validation, quality reports, and delivery archives are written as artifacts.
Who It Is For
Built for people already using AI coding and tired of unreliable delivery.
It is for teams and individuals already shipping with AI and now trying to make the process predictable, reviewable, and repeatable.
Heavy AI coding individuals
You already use Claude Code, Cursor, Codex, or Trae a lot, and you want the output to be more stable, more complete, and closer to actual delivery.
Small teams and startup teams
You need to ship MVPs and test business viability fast, but you do not want the AI development process to drift or disappear into chat history.
Project teams standardizing host workflows
You want different members using different hosts to follow the same process discipline, quality standards, and delivery evidence model.
Use Cases
Four common ways teams actually use it.
Super Dev fits real project execution more than one-off demos. These scenarios show where it adds the most value.
Build an MVP from zero to one
Start with similar-product research, then generate the three core docs, the spec, and frontend validation to ship a demoable MVP fast.
Take over an existing project
Generate a repo map, inspect the likely impact radius, then rebuild constraints and docs before the host starts changing code.
Standardize AI development across a team
Different members can keep their preferred hosts while Super Dev standardizes triggers, protocol surfaces, quality gates, and delivery outputs.
Pull the host back from direct coding into a delivery path
When the host wants to jump into implementation, Super Dev forces research, the three core docs, approval, and only then implementation.
Pipeline
From requirement to delivery, the path stays fixed.
The trigger is short and the workflow is fixed. The host moves through research, documentation, approval, implementation, verification, and delivery.
Research and requirement hardening
Read local knowledge first, research similar products online, and close gaps in scope, edge cases, and acceptance criteria.
Three core docs and spec
Generate PRD, Architecture, and UI/UX first. After approval, create the spec and task breakdown.
Frontend first, then backend integration
Build the frontend and verify it runs before moving into backend implementation and end-to-end wiring.
Quality and delivery
UI review, red-team checks, delivery packaging, release rehearsal, and release readiness determine whether the work can actually ship.
Critical gates
Three-doc approval gate
Without explicit approval, the host cannot create the spec or start implementation.
Frontend runtime gate
Without a passing frontend runtime report, the host cannot continue into backend and later stages.
Delivery ready / rehearsal passed gate
If the delivery package is not ready or the rehearsal did not pass, the project is not done.
Host Support
Different hosts, different protocols, only two trigger styles.
Start with the practical answer: what to type. Commands, AGENTS, steering, rules, and skills are documented in detail below.
Slash hosts
/super-devThese hosts accept /super-dev your requirement.
Claude CodeCodeBuddy CLICodeBuddyCursor CLICursorGemini CLIiFlowKiro CLIOpenCodeQoder CLIQoderWindsurfAntigravity
Text-trigger hosts
super-dev:These hosts use super-dev: your requirement.
Codex CLIKimi CLIKiroTrae
Host matrix
CertifiedCompatibleExperimental
| Host | Trigger | Protocol surface | Maturity |
|---|---|---|---|
| Claude Code | /super-dev | commands + subagents | Certified |
| CodeBuddy CLI | /super-dev | commands + skills | Compatible |
| CodeBuddy | /super-dev | commands + skills | Experimental |
| Codex CLI | super-dev: | AGENTS.md + skills | Compatible |
| Cursor CLI | /super-dev | commands + rules | Compatible |
| Cursor | /super-dev | commands + rules | Experimental |
| Gemini CLI | /super-dev | commands + GEMINI.md | Compatible |
| iFlow | /super-dev | commands + skills | Experimental |
| Kimi CLI | super-dev: | AGENTS.md + text trigger | Compatible |
| Kiro CLI | /super-dev | commands + AGENTS.md | Compatible |
| Kiro | super-dev: | project steering + global steering | Experimental |
| OpenCode | /super-dev | commands + skills | Experimental |
| Qoder CLI | /super-dev | commands + skills | Compatible |
| Qoder | /super-dev | commands + rules + skills | Experimental |
| Windsurf | /super-dev | workflows + skills | Experimental |
| Antigravity | /super-dev | commands + GEMINI.md + workflows | Compatible |
| Trae | super-dev: | project rules + compatibility skill | Compatible |
Proof / Trust
Visible trust signals.
Open source, published packages, host coverage, local knowledge, quality gates, and delivery artifacts all appear directly on the page.
MIT open source and PyPI release
The code is visible, the install path is clear, and versions are traceable. This is not a black-box hosted platform.
Multi-host integration
The same governance model installs into CLI and IDE hosts without forcing the user onto a new coding tool.
Local knowledge first
knowledge/ and knowledge bundles are reused in research, the three core docs, spec generation, quality, and delivery.
UI Review and Release Readiness
The work is not done when code is generated. It must pass runtime validation, quality gates, and release checks.
Auditable delivery artifacts
Delivery manifests, quality reports, runtime validation, and release readiness are written to disk.
How it works
From install to delivery, the entry path stays short.
Install and onboard first, then trigger the flow inside the host. The workflow keeps producing documents, gates, runtime validation, and delivery artifacts after that.
Terminal
pip install -U super-dev
# or
uv tool install super-dev
# open the host installer
super-devFAQ
These answers cover positioning, integration, and workflow.
The host handles the model, browsing, tool calls, file edits, and runtime execution. Super Dev handles research order, the three core docs, approval gates, frontend runtime validation, quality gates, and delivery standards.
A prompt template only affects one conversation. Super Dev installs into host protocol surfaces and persists approval gates, runtime validation, quality gates, delivery state, and release readiness.
Spec tools mainly govern project specs. Super Dev governs the AI development process inside the host, covering research, the three core docs, spec, frontend, backend, testing, and delivery in one governed path.
Those hosts use super-dev: as the text trigger, then rely on AGENTS, rules, steering, or skills to interpret and execute the Super Dev flow. The user only needs to remember the trigger, not the underlying protocol details.
Connect the host first, then build through the governed flow.
Install Super Dev, run super-dev to onboard the host, then trigger /super-dev or super-dev: inside the host. The workflow gates take over from research through delivery.
You can also use uv tool install super-dev