Builds data pipelines for ETL/ELT, manages analytics storage (data warehouse/lake), and ensures data quality. Optimizes data ingestion, transformation, and reporting. Use when the user asks to build data pipelines, design analytics infrastructure, or improve data quality.
Designs CI/CD pipelines, provisions cloud infrastructure, and manages releases. Absorbed cloud-engineer and release-manager responsibilities. Runs as the sole Ship phase agent. Use when building CI pipelines, deploying to cloud, or managing releases.
Implements complete features spanning frontend UI and backend APIs. Handles database schema, API endpoints, and component logic end-to-end. Use when the user asks to build a feature that requires both frontend and backend changes.
Conducts grill-me interview to deeply understand the feature, then decomposes it into tracer bullet slices and emits scope.json. Runs as the sole Plan phase agent. Use for /sdlc-plan to kick off any feature.
Writes cross-slice E2E tests covering flows that span multiple slices. Runs once after all feature slices complete in the Build phase. Reads implementation-log.md to understand the full shape of what was built. Flags which slices caused any E2E failures for targeted retry.
Performs SAST analysis, OWASP Top 10 audit, dependency scanning, and (when scope requires) penetration testing. Runs in the Verify phase. Always runs SAST/OWASP; pentest section is conditional on needspentest from scope.json.
Defines SLOs, designs monitoring/alerting, writes runbooks, and (when hasauth is true) sets up security monitoring. Absorbed secops-analyst responsibilities. Runs in Operate phase. Use for reliability, observability, and security operations.
Writes API documentation, SDK guides, tutorials, developer guides, and external communication. Makes technical concepts accessible to diverse audiences. Maintains docs-as-code philosophy with examples and runnable code. Use when creating API docs, writing developer guides, documenting SDKs, or creating tutorials.
Conducts user research, defines personas, creates wireframes, and produces design tokens and component specs. Runs once at the start of the Build phase when hasui is true. Covers all slices in a single pass to give fullstack-engineer a consistent design reference.
Phase 2 — Build. Reads plan-handoff.md, optionally runs ux-designer (hasui gate), then loops fullstack-engineer over each slice with ralph-loop self-correction, then runs qa-engineer for E2E tests.
Standalone issue implementation with Ralph Loop — implements a single Linear issue or free-form spec using fullstack-engineer + self-correcting retry loop.