Audit AWS, Azure, GCP, hybrid, or multi-cloud infrastructure across security, reliability, cost, efficiency, performance, operations, delivery, and developer experience. Use for read-only environment reviews, Well-Architected assessments, cloud cost and utilization reviews, DevOps/platform-engineering assessments, architecture evidence audits, technical due diligence, or ranked infrastructure remediation plans. Do not use for penetration testing, compliance certification, or executing infrastructure changes.
Audits existing systems for architecture, maintainability, reliability, security, performance, and test gaps.
Coordinate an active production incident or prepare an incident runbook using runtime evidence, explicit roles, bounded mitigations, stakeholder updates, verification, rollback, and a blameless follow-up. Use for outage command, degraded service, security or provider incidents, incident timelines, status updates, and post-incident action plans. Do not use to execute destructive remediation or claim recovery without authoritative readback.
Assess the likely consequences of a proposed or local code change with GitNexus graph evidence, then verify the result against the exact repository. Use for dependency tracing, blast-radius analysis, regression planning, and deciding whether a shared symbol is safe to change.
Assess the likely consequences of a proposed or local code change with GitNexus graph evidence, then verify the result against the exact repository. Use for dependency tracing, blast-radius analysis, regression planning, and deciding whether a shared symbol is safe to change.
Plans infrastructure-as-code setup across environments, resources, secrets, deploy flow, and rollback approach.
Implementation Plan workflow that groups context collection, production, review, and packaging tasks into one deliverable.
Plans safe migrations with compatibility, data preservation, rollout phases, verification, and rollback.
Turns requirements into implementation plans for web or mobile with milestones, files, tests, and rollout.
Defines logs, metrics, traces, alerts, dashboards, SLOs, and incident response hooks for a system.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Review QA Manager evidence with requirement-to-test traceability, fast and full gate plans, comparable performance baselines, security evidence records, workflow maps, and UI edge-case gaps.
Verify unstable framework, library, and platform facts against the installed version and current primary sources before implementation. Use when technical decisions depend on APIs, configuration, defaults, compatibility, or behavior that may have changed.
Verify unstable framework, library, and platform facts against the installed version and current primary sources before implementation. Use when technical decisions depend on APIs, configuration, defaults, compatibility, or behavior that may have changed.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Creates architecture plans with system boundaries, data flow, APIs, infrastructure, security, and tradeoffs.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
Coordinate an active production incident or prepare an incident runbook using runtime evidence, explicit roles, bounded mitigations, stakeholder updates, verification, rollback, and a blameless follow-up. Use for outage command, degraded service, security or provider incidents, incident timelines, status updates, and post-incident action plans. Do not use to execute destructive remediation or claim recovery without authoritative readback.
Run a go/no-go launch readiness check for a web app before it goes live. Use when you need one evidence-backed checklist covering domain, DNS, HTTPS and redirects, email deliverability (SPF, DKIM, DMARC), analytics and conversion tracking, error tracking, uptime and health checks, backups and a tested restore, rollback and the launch-day runbook, privacy policy, terms and cookie consent, broken links, 404 and error pages, transactional email, and owners on call, ending in a signed go/no-go decision.
Run a go/no-go launch readiness check for a web app before it goes live. Use when you need one evidence-backed checklist covering domain, DNS, HTTPS and redirects, email deliverability (SPF, DKIM, DMARC), analytics and conversion tracking, error tracking, uptime and health checks, backups and a tested restore, rollback and the launch-day runbook, privacy policy, terms and cookie consent, broken links, 404 and error pages, transactional email, and owners on call, ending in a signed go/no-go decision.
Review QA Manager evidence with requirement-to-test traceability, fast and full gate plans, comparable performance baselines, security evidence records, workflow maps, and UI edge-case gaps.
Checks a web app before launch across launch readiness, performance, technical SEO, AI search visibility, responsive layout and accessibility, then delivers an evidence-backed go or no-go recommendation with owned fixes.
Audit and improve a web app's page speed before launch with Lighthouse and PageSpeed Insights. Use when you need mobile and desktop Lighthouse runs on key URLs, Core Web Vitals (LCP, INP, CLS) read from both lab and field data, every failing audit mapped to a concrete code or config fix, a prioritized fix plan, and a re-measurement that proves the gain.
Audit and improve a web app's page speed before launch with Lighthouse and PageSpeed Insights. Use when you need mobile and desktop Lighthouse runs on key URLs, Core Web Vitals (LCP, INP, CLS) read from both lab and field data, every failing audit mapped to a concrete code or config fix, a prioritized fix plan, and a re-measurement that proves the gain.