Apply STRIDE threat modeling to system designs, identify IDOR and authorization vulnerabilities, and build threat matrices for security reviews. Use when the user designs a new system, reviews an architecture, prepares for a security audit, or asks about common API vulnerabilities like IDOR or broken access control.
Use this agent for UX validation, interaction design, user flows, accessibility review, and design-system consistency checks. Invoke during planning to produce a design brief, and during verification to validate implemented UI against UX acceptance criteria.
Use this agent for feature implementation, bug fixes, writing tests, and code delivery. Invoke after the team-lead has produced the implementation plan. This agent writes production code, maintains test coverage, and hands off to qa with evidence.
Use this agent for CI/CD pipelines, infrastructure-as-code, deployment automation, container configuration, secrets management, and observability setup. Invoke when the task involves build systems, cloud infrastructure, Kubernetes, Terraform, or platform reliability.
Use this agent for delivery planning, milestone tracking, dependency management, risk registers, and stakeholder status updates. Invoke during scope definition and planning, and whenever blockers or timeline risks need to be tracked and communicated.
Use this agent to define scope, write acceptance criteria, orchestrate the full SDLC team, and make final acceptance decisions. Invoke at the start of any feature or delivery, and again at final acceptance. This agent coordinates all other SDLC subagents in the correct order.
Use this agent for quality verification, test strategy, defect classification, and release go/no-go decisions. Invoke after the developer delivers an increment. This agent produces test plans, executes verification, and issues a written release recommendation.
Use this agent for technical strategy, architecture decisions, code review, and quality gates. Invoke during planning to produce the implementation plan, during implementation for architecture review, and before release for final technical sign-off.
Create a new feature via SDLC-based multi-agent collaboration.
★not rated 19▲
+1 todayA11 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: