Agent
Use this agent when the user invokes OpenSpec commands related to fast-forward (/opsx:ff) or continue (/opsx:continue). This agent should be launched to analyze spec changes, design implementation plans, and organize development tasks based on product requirements. Examples: Context: The user invokes the OpenSpec…
Agent
Specialized backend developer for the configured backend stack implementation. Use when tasks are backend-only or when splitting full-stack work across specialized developers in parallel pipelines.
Agent
Use this agent when backend files have been modified. Scan-and-report only. Scans for N+1 query patterns, connection pool safety issues, pagination safety problems, and missing database indexes. Do NOT use this agent to fix issues — it scans and reports only. Examples: Example 1: user: (orchestrator) Backend files…
Agent
Use this agent when an OpenSpec change is being applied (i.e., during the /opsx:apply phase of the OpenSpec workflow). This agent implements the actual code changes defined in OpenSpec change specifications, translating specs into production-quality code across the full stack. Examples: Example 1: user: "Apply the…
Agent
Use this agent after tests are written to detect documentation drift and update docs — changelog entries, README updates, and API docs — keeping docs in sync with code changes. Runs as Phase 3d in the implement pipeline. Examples: Example 1: user: (orchestrator) Tests complete. Update docs for the implemented files.…
Agent
Specialized frontend developer for the configured frontend stack implementation. Use when tasks are frontend-only or when splitting full-stack work across specialized developers in parallel pipelines.
Agent
Use this agent when frontend files have been modified. Scan-and-report only. Scans for bundle size regressions, accessibility violations (WCAG 2.1 AA), and render performance issues. Do NOT use this agent to fix issues — it scans and reports only. Examples: Example 1: user: (orchestrator) Frontend files were modified.…
Agent
Use this agent when the /specrails:implement pipeline produces conflict markers in Phase 4a (worktree merge), or when the user runs /specrails:merge-resolve directly. The agent reads context bundles from both features, analyzes each conflict block, and applies AI-powered resolution where confidence is sufficient.…
Agent
Use this agent to detect performance regressions after implementation. It benchmarks modified code paths, compares metrics against configured thresholds, and outputs a structured report. Runs as part of Phase 4 in the implement pipeline. Do NOT use this agent to fix regressions — it measures and reports only.…
Agent
Use this agent for read-only analysis tasks: backlog prioritization, VPC evaluation, codebase audits, spec gap analysis, dependency checks, and reporting. This agent reads specs, code, personas, and archived changes to produce structured reports. It never writes code or modifies files. Examples: Example 1: user…
Agent
Use this agent when the user invokes the opsx:explore command. This agent should be launched every time opsx:explore is used to brainstorm, ideate, explore new features, evaluate product direction, or analyze capabilities. Examples: Example 1: user: "/opsx:explore I want to think about how we could improve the user…
Agent
Use this agent as the final quality gate after developer agents complete implementation. It reviews all code changes, runs the exact CI/CD checks, fixes issues, and ensures everything will pass in the CI pipeline. Launch once after all developer worktrees have been merged into the main repo. Examples: Example 1: user…
Agent
Use this agent to scan all modified files for secrets, hardcoded credentials, and security vulnerability patterns after implementation. Runs as part of Phase 4 in the implement pipeline. Do NOT use this agent to fix issues — it scans and reports only. Examples: Example 1: user: (orchestrator) Reviewer completed. Now…
Agent
Use this agent after a developer agent completes implementation, to generate comprehensive tests for the implemented code. Runs as Phase 3c in the implement pipeline, before the reviewer. Examples: Example 1: user: (orchestrator) Developer agent completed. Write tests for the implemented files. assistant: Launching…
Agent
This agent is launched by the orchestrator with a specName argument to scaffold OpenSpec artifacts and produce an implementation design for a named change. It does NOT trigger autonomously on /opsx:ff or any other slash command — it must be invoked explicitly with the change name as a positional argument. Examples…
Agent
Use this agent when an OpenSpec change is being applied (i.e., during the /opsx:apply phase of the OpenSpec workflow). This agent implements the actual code changes defined in OpenSpec change specifications, translating specs into production-quality code across the full stack. Examples: Example 1: user: "Apply the…
Agent
Use this agent as the final quality gate after developer agents complete implementation. It reviews all code changes, runs the exact CI/CD checks, fixes issues, and ensures everything will pass in the CI pipeline. Launch once after all developer worktrees have been merged into the main repo. Examples: Example 1: user…