Docs Commands
Commands
Quick reference for every ASDT command — pick a card to jump straight to its full details below.
- CLI
asdt-tuiInteractive terminal UI
The only CLI tool — checks your setup and installs or updates the ASDT specialist skills.
- Slash command
/asdt-initInitialize ASDT
Detects your stack and creates .asdt/config.yaml and .asdt/knowledge/platform.yaml.
- Slash command
/asdtPipeline routing suggestion
Analyzes the request and recommends which specialists to involve and in what order.
- Slash command
/asdt-researcherResearcher
Runs the Researcher specialist only — discovery for fuzzy problems before requirements exist.
- Slash command
/asdt-pmProduct Manager
Runs the Product Manager specialist only.
- Slash command
/asdt-architectArchitect
Runs the Architect specialist only.
- Slash command
/asdt-developerDeveloper
Runs the Developer specialist only.
- Slash command
/asdt-qaQA
Runs the QA specialist only.
- Slash command
/asdt-securitySecurity
Runs the Security specialist only.
- Slash command
/asdt-ux-uiUX/UI
Runs the UX/UI specialist only.
CLI
asdt-tui
The only CLI tool. An interactive terminal app — run it with no arguments:
asdt-tui
It checks your setup, lets you pick which assistant(s) to target (Claude Code, OpenCode, or both), and installs or updates the ASDT specialist skills. Everything is driven by the on-screen menu — there are no subcommands or flags.
Initializing a project (writing
.asdt/config.yaml) is not a CLI command — it’s the/asdt-initslash command, run inside your assistant. See below.
Slash Commands (Claude Code / OpenCode)
Slash Commands — commands you type directly into your AI assistant, prefixed with /.
/asdt-init
Initialize ASDT in the current project. Detects your stack and creates .asdt/config.yaml and .asdt/knowledge/platform.yaml. Run it inside your assistant, in your project folder.
/asdt-init
/asdt
Ask the team. Describe what you want built and it recommends which specialists to involve and in what order, waiting for your confirmation before listing the commands to run.
/asdt "add email verification to the signup flow"
It also answers questions about the state of the work, straight from what the team already worked out — no specialists are run:
/asdt "what did we decide about the password hashing?"
/asdt "how are we doing on the checkout redesign?"
/asdt "what's still open?"
/asdt-researcher
Runs the Researcher specialist only — discovery for fuzzy problems: it frames the problem, diverges into candidate directions, judges each one’s feasibility against the codebase, and converges on a single recommendation. Runs before the PM when the problem isn’t yet well-defined.
/asdt-researcher Explore ways to reduce onboarding drop-off
/asdt-pm
Runs the Product Manager specialist only.
/asdt-pm Redesign the notification settings page
/asdt-architect
Runs the Architect specialist only.
/asdt-architect Design the real-time sync architecture
/asdt-developer
Runs the Developer specialist only.
/asdt-developer Implement the sidebar component
/asdt-qa
Runs the QA specialist only.
/asdt-qa Review the checkout flow for edge cases
/asdt-security
Runs the Security specialist only.
/asdt-security Review the OAuth integration
/asdt-ux-ui
Runs the UX/UI specialist only.
/asdt-ux-ui Design the onboarding flow