/asdt-researcher Researcher
Explores fuzzy problems before requirements exist: divergent ideation, feasibility scans, one recommended direction.
For Claude Code and OpenCode
A full software team, in your terminal
AI specialists that pass work to each other over a shared knowledge base. You direct the route; the team forgets nothing.
Install — one command
$
curl -fsSL https://raw.githubusercontent.com/vitualizz/asdt/main/install.sh | bash Try it
~/app $ claude
> /asdt add Google login
Analyzing your request…
Recommended route
pm scope + user stories /asdt-pm
architect OAuth flow decision /asdt-architect
developer implementation /asdt-developer
security token review /asdt-security
qa test plan /asdt-qa
Each step picks up where the previous left off.
Run them in order — or jump straight to one.
> /asdt-pm
pm exploring the codebase…
✓ pm — user stories saved · knowledge base
→ next: /asdt-architect
~/app $ claude
> /asdt-pm define the offline feature
Reading project knowledge…
◆ pm — 4 steps
knowledge-recall prior memory context
user-stories 3 user stories pm/user-stories
scope-analysis scope + boundaries pm/scope-analysis
backlog requirements pm/handoff
Each artifact is saved to the shared knowledge base.
→ next: /asdt-architect
~/app $ claude
> /asdt-security review auth
security modeling STRIDE threats…
◆ security — 4 steps · STRIDE
threat-modeling 6 STRIDE threats security/stride-threats
attack-surface 3 entry points security/attack-surface
owasp-analysis A01 · A07 security/owasp-findings
hardening-checklist 1 critical · 4 med security-findings
→ next: /asdt-developer to apply the fixes
~/app $ claude
The real deal: type a request and see what route the team builds.
Try /asdt add offline mode · /asdt-developer · /help
>
01 · The team
Meet the specialists
Focused roles, each with their craft. Invoke any one directly, or ask /asdt to suggest the route.
Start here
Route Advisor
/asdt Analyzes what you ask and recommends which specialists to involve and in what order. You confirm the plan and run each command.
/asdt-pm Product Manager
Turns loose ideas into user stories with clear scope and defined criteria.
/asdt-architect Architect
Makes technical decisions: system design, API contracts, decision records.
/asdt-developer Developer
Turns specs and designs into production code, with an implementation plan.
/asdt-qa QA Engineer
Builds the safety net: test plans, acceptance criteria, quality reports.
/asdt-security Security
Finds the gaps an attacker would see first: threat models and hardening.
/asdt-ux-ui UX/UI Design
Shapes the experience: flows, components, and accessibility.
02 · How it works
Not a pipeline. A team you compose.
/asdt suggests a route for the task — you confirm it, reorder it, or go straight to a specialist.
pm → architect → ux-ui → developer → security → qa
each step saves to the knowledge base · next specialist reads automatically
> /asdt add workspace permissions per role
developer → qa
each step saves to the knowledge base · next specialist reads automatically
> /asdt fix crash on empty pagination
security
each step saves to the knowledge base · next specialist reads automatically
> /asdt-security review session handling
ux-ui → developer
each step saves to the knowledge base · next specialist reads automatically
> /asdt redesign onboarding for mobile
03 · Why ASDT
A chat improvises. A team delivers.
Code assistants are great. With method and memory, they become a team.
Just a chat
✕
Context degrades as the conversation grows — what you decided yesterday no longer exists.
✕
Each prompt reinvents the process from scratch — sometimes brilliant, sometimes chaotic.
✕
You get to a demo fast, but without stories, decisions, or tests to back it up.
With ASDT
✓
Every decision lives in a shared knowledge base the whole team consults. ASDT remembers.
✓
Each specialist works with defined steps — explore, specify, execute. Every time.
✓
Real artifacts remain — stories, decisions, tests — ready to pick up tomorrow.
Hire the team with one command
Works with Claude Code and OpenCode. Open source, MIT license.