Use this agent when you need a senior principal engineer's review of code changes, architecture decisions, or system design — particularly around async Python, resource lifecycles, NATS integration, failure modes, and operational concerns. Alex excels at finding what will break in production, identifying resource…
Specialist on the three Mendix Studio Pro extensibility surfaces — Model SDK (TS/JS, offline, against Team Server only), Web Extensibility API (@mendix/extensions-api 11.10.0 GA, runs as a web extension inside Studio Pro), and C# Extensibility API (Mendix.StudioPro.ExtensionsAPI 11.8.0 beta, compiles to .dll and…
Guided walkthrough of the ISO/IEC/IEEE 15288 system life cycle. Use when starting a new system, recovering an in-flight project that has lost its lifecycle discipline, or auditing SE coverage of an existing system. Reads the se-lifecycle skill, asks the current phase, then orchestrates the right Powerhouse tool for…
Use this agent when you need to manage project tasks using the llm-backlog CLI tool. This includes creating new tasks, editing tasks, ensuring tasks follow the proper format and guidelines, breaking down large tasks into atomic units, and maintaining the project's task management workflow.
A specialized sub-agent that curates the user's project memory. Use proactively after non-trivial tasks to capture decisions, constraints, and preferences.
Use this agent to curate (prune) a session's current summary snapshot — it reads the full summary, archives the original to disk, and drafts a revised version that preserves substantive history while removing process narration and redundancy. It runs in an isolated context so the large summary text never enters the…
Plans and designs a Canvas App. Discovers available controls, APIs, and data sources; calls describeapi for relevant connectors and getdatasourceschema for connected data sources; designs the aesthetic direction and screen plan; presents plan for user approval via a markdown approval prompt; calls describecontrol for…
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
Reviews code changes for correct Tailwind CSS v4 usage. Catches v3 patterns, missing accessibility attributes, and inconsistent theming. Use after generating or modifying Tailwind code.
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.
Developer agent (Agent-Dev). Use it to implement features, write or modify production code, and fix bugs. When done, it automatically commits its work with the Agent-Dev label and the LoC count.
Frontend Implementation agent that turns approved UI designs into production-ready code using the developer's chosen framework. Implements all pages, components, interactions, and responsive behavior.
A domain-specialist agent for the GovOn AX platform, using trained models for public administration and law. It is intended to answer questions about administrative procedures, permits, complaints, legislation, and court decisions.
An agent role for making the smallest needed code or documentation change. It follows existing project style and uses TDD, meaning tests are written before the implementation.
Validates task files against task template and task-creator rules. Reads sources of truth, checks structure, content quality, and consistency. Triggers: after task-creator generates files, on re-validation after fixes. Not for: security (security-auditor), spec coverage (completeness-validator).
Place subagent definition files here. Each .md file defines a specialized subagent that can be invoked via the Task tool or --agent flag.
★not rated 2 3d agoA0 tokens
originalApache-2.0
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: