Team Infrastructure
Infrastructure team: deployment safety, capacity, observability, platform setup, and data-operational risk in one production-readiness assessment.
Install
$ agentstack add skill-saemihemma-lead-producer-oss-team-infrastructure ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Infrastructure Team
Purpose
Judge whether a system can be deployed, observed, scaled, and recovered safely in production.
Composition
- role-devops-engineer: release flow, observability, incident readiness
- role-railway-deployment: Railway-specific deployment, platform risk
- role-scalability-engineer: capacity, bottlenecks, load behavior
- role-security-engineer: security posture, operational exposure
- role-data-engineer: data reliability, operational data-surface risk
- Synthesis: conflict handling, acceptance
Use When
- Auditing production readiness or deployment risk
- Reviewing infrastructure after incident or before major launch
- Checking scaling, observability, rollback, platform setup together
Do NOT Use When
- Feature implementation or product prioritization
- Code quality with no production-operations angle
- Architecture design with no deployment concern
Workflow
- Map release path, runtime dependencies, recovery path.
- Review deployment safety, observability, scale, security, data ops together.
- Make cost, risk, operational complexity trade-offs explicit.
- Synthesize one production-readiness verdict.
Default Output
INFRASTRUCTURE REVIEW
=====================
Deployment: release/rollback risks
Operations: observability/incident-readiness gaps
Scale/Data: capacity risks, data-operational concerns
Security: operational security blockers
Recommendation: ready / rework / escalate, required fixesConflict Resolution
- DevOps Engineer owns release flow and rollback decisions. Security Engineer can block on operational exposure.
- Scalability Engineer owns capacity assessment. Railway Deployment Engineer owns platform-specific constraints.
- Data Engineer owns data-operational risk. When deployment urgency conflicts with security, security wins.
Anti-Drift Rules
- Do not expand into application architecture under infrastructure review label.
- Treat rollback failures and observability gaps as release blockers, not follow-ups.
- Cost analysis is part of the verdict, not a separate nice-to-have.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: saemihemma
- Source: saemihemma/lead-producer-oss
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.