Docs Recipes
Recipes
Copy-paste command sequences for the most common ASDT scenarios. Each recipe shows the exact commands to run in Claude Code or OpenCode. Filter by what you’re trying to do, or browse all 14 below — anything touching auth, payments, PII (personally identifiable information), or external integrations should include a security review.
Showing 14 recipes for "All".Showing 5 recipes for "Start from scratch".Showing 2 recipes for "Add to existing code".Showing 5 recipes for "Review & harden".Showing 2 recipes for "Understand & document".
Ship a new user-facing feature
Start here when a feature request is in vague language and needs the full PM → Architect → Developer sequence.
Review the suggested specialist sequence, then run each in order.
/asdt "Add a contact form with email notification"
/asdt-pm "Add a contact form with email notification"
/asdt-architect
/asdt-developerBuild a new REST API endpoint
For backend-only changes where the API contract is the primary design decision.
/asdt "Add a POST /api/v1/subscriptions endpoint"
/asdt-pm "Add a POST /api/v1/subscriptions endpoint"
/asdt-architect
/asdt-developerNew screen with UX design first
For user-visible features where UI design should precede implementation.
/asdt "Add an onboarding wizard for new users"
/asdt-pm "Add an onboarding wizard for new users"
/asdt-ux-ui
/asdt-architect
/asdt-developer
/asdt-qaFeature with security review before shipping
For anything touching auth, payments, PII (personally identifiable information), or external integrations.
/asdt "Add OAuth login with GitHub"
/asdt-pm "Add OAuth login with GitHub"
/asdt-architect
/asdt-security
/asdt-developer
/asdt-qaExplore before planning (fuzzy problem)
When the problem is unclear and you need discovery before requirements.
Researcher produces a discovery brief with a recommended direction — hand it to PM next.
/asdt-researcher "We're losing users at the signup step — what could we do?"
/asdt-pm "Based on the discovery brief: add progressive disclosure to the signup flow"Lock scope and write user stories
When you have a clear feature idea and just need structured requirements.
/asdt-pm "Add dark mode toggle to user settings"Document an architecture decision
When the technical approach needs a formal ADR and system design.
/asdt-architect "Document the decision to use PostgreSQL row-level security for multi-tenancy"Write production code from a settled spec
When scope and architecture are already locked in the knowledge base.
/asdt-developer "Implement the multi-tenancy RLS policy from the Architect's ADR"Security audit on an existing feature
Run at any point — no prior specialist run required.
/asdt-security "Review the session management in the auth module"Design a new UI component
When you need a component spec before the developer starts coding.
/asdt-ux-ui "Design a data table component with sorting, filtering, and pagination"Validate test coverage before shipping
Run after Developer — QA reads the implementation artifact automatically.
/asdt-qaPick up at Developer after an existing ADR
When PM and Architect ran in a previous session. Developer loads prior artifacts automatically.
No need to re-run PM or Architect — artifacts are in the knowledge base.
/asdt-developerAdd a security review to an in-flight pipeline
Run Security at any point without restarting the pipeline.
Security reads system-design-final and dev-implementation from the knowledge base.
/asdt-securityQA a completed feature without a full pipeline
When a feature was built without ASDT — run QA against the existing code.
/asdt-pm "Add acceptance criteria for the existing checkout flow"
/asdt-qa