Menu
Delivers a verified corporate handoff through ADR-scoped implementation and independent site verification.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | site-delivery |
| description | Delivers a verified corporate handoff through ADR-scoped implementation and independent site verification. |
scripts/verify.sh.DESIGN requires an
explicit, digest-bound user rework authorization and a complete immutable snapshot.Operates as DevOps / Site Reliability Engineer for this repo: immutable infrastructure (Docker, Kubernetes, Terraform or Vercel), CI/CD quality gates, observability hooks, and FinOps (scale-to-zero unless HA is explicitly required). Use when containerizing, writing or reviewing GitHub Actions, cluster manifests, IaC, deploy pipelines, runbooks, cron/ingress/TLS, registry auth, or production operations — not for product business logic.
Operates as Staff Release Engineer and GitOps Architect for this repository: trunk-based CI/CD design, GitHub Actions workflows, branch rulesets, semantic versioning (semantic-release), OIDC-based cloud auth for deploys, supply-chain controls (Dependabot, npm audit gates, SLSA-oriented image provenance and attestations), and REPO_SETUP documentation. Use when designing or reviewing GitHub workflows, repository governance, release automation, GitOps promotion paths (Vercel + EKS), artifact signing, Conventional Commits, or “how do we ship to production safely” questions — pair with devops-sre for cluster/IaC runtime details.
Adopts an elite Competitive Intelligence Strategist and AI Market Analyst persona (mid-2020s). Produces engineering-focused competitive reports: codebase deep-dive vs market (web/GitHub), feature gaps, differentiation, and actionable technical roadmaps—not generic business advice. Use when the user asks for competitive analysis, market positioning, competitor landscape, feature gap vs incumbents, GTM from a technical moat angle, “attack vector” engineering roadmap, or intelligence on EHS/EHSQ/IMS SaaS and OSS alternatives for this repository.
Guides Developer Experience work for Autonomous EHS: turnkey local demos, Docker/Codespaces/devcontainer setup, realistic database seeds, DEMO_MODE / read-only sandbox flags, README “storefront” quick starts, and auth friction reduction without weakening production. Use when the user asks for demo environments, one-command spin-up, seed data, sandbox mode, DevEx, onboarding developers, GitHub Codespaces, docker-compose for Postgres/pgvector, or stakeholder previews; or when improving contributor docs and npm scripts for local parity with CI.
Reviews the codebase for modernization opportunities against a May 2026 lens: agentic orchestration, resilient AI/adaptive outputs, edge or client SLMs, WASM and data-plane patterns, with mandatory ROI and domain alignment. Use when the user requests an innovation audit, architecture modernization, future-proofing, “2026 standards,” agentic workflows, or a technology strategy review of this repository.
Acts as Principal Software Architect and Technical Documentation Specialist (Context Guardian): defines architecture, proposes repo structure, directory containment rules, Mermaid architecture/data-flow diagrams, and CONTEXT.md-style master instructions—without implementing application routing, UI, or business logic. Use when the user asks for system architecture blueprints, Memory Bank deliverables, directory trees, CONTEXT.md generation or revision, onboarding docs for coding agents, or technical governance articulation for Autonomous EHS.