mcpField
I
infra-launch-orchestrator

infra-launch-orchestrator

github.com/sergekostenchukCloud & DevOps3249 installsUpdated 18w ago
Repository

About infra-launch-orchestrator

A skill for coordinating infrastructure and launch work, intended for teams planning releases. It organizes approvals, rollback, and dependencies across operating modes, and keeps production actions on hold without explicit approval.

Key features

  1. 01Map launch scope and dependencies
  2. 02Prepare dry-run commands and checklists
  3. 03Route work to specialist skills
  4. 04Collect launch-readiness evidence
  5. 05Hold irreversible actions pending approval

Use cases

  1. 01Plan launch owners and approvals
  2. 02Prepare deployment dry-run steps
  3. 03Check rollback and monitoring before launch
  4. 04Hand off domain, DNS, or security tasks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill infra-launch-orchestrator

After installing, type/infra-launch-orchestratorin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlevals/evals.json

Details

From the project README

Infra Launch Orchestrator

This skill coordinates the infra/launch layer. It is not the central UI/UX chair and does not execute irreversible actions by default.

Operating Modes

  • plan: map launch scope, owners, approvals, rollback, and dependencies.
  • dry-run: prepare commands/checklists without applying them.
  • handoff: route to specialist infra skills.
  • launch-gate: collect readiness evidence before any production action.

Required Workflow

  1. Identify requested action: advisory, dry-run, or production execution.
  2. Route specialists:
    • domain ideas: domain-name-generator;
    • registrar choice: domain-registrar-advisor;
    • hosting choice: server-selector;
    • provisioning plan: server-provisioner;
    • deploy plan: deploy-orchestrator;
    • DNS plan: domain-dns-configurator;
    • SSL/security: ssl-and-security-hardener;
    • webmaster tools: webmaster-registrar;
    • final gate: launch-readiness-auditor.
  3. Keep all irreversible or paid steps Planned until explicit production approval is recorded.
  4. Require rollback and monitoring before launch.

Safety Rules

  • Do not buy domains, change DNS, provision paid servers, deploy production, issue destructive commands, submit webmaster changes, or store credentials without explicit approval.
  • Do not print API tokens, provider credentials, SSH keys, DNS tokens, cookies, or .env values.
  • If approval is missing, provide a dry-run plan only.

Validation

python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/infra-launch-orchestrator
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/infra-launch-orchestrator
python3 -m json.tool $CODEX_HOME/skills/infra-launch-orchestrator/evals/evals.json >/dev/null

Comments

Markdown supported