environment-orchestrator

Generate teardown-safe docker-compose environment recipes from catalog components.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/mytechsonamy/VibeFlow --skill environment-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: environment-orchestrator
Source: https://github.com/mytechsonamy/VibeFlow/tree/main/skills/environment-orchestrator
Command: npx skills add https://github.com/mytechsonamy/VibeFlow --skill environment-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates a reproducible, teardown-safe environment recipe for test scenarios by translating catalog components into a portable docker-compose topology, while ensuring secrets are never inlined and healthchecks are declared for all components.

Core Features & Use Cases

  • Generates a docker-compose based environment topology from a catalog, pins image versions, and attaches healthchecks to every service.
  • Enforces secret handling by routing secrets through a references store rather than embedding them in the recipe.
  • Supports multiple profiles (unit, integration, e2e, uat, perf) and platforms (web, ios, android, backend) with optional components activated via test-strategy.md and a strict teardown.
  • Produces human-facing env-setup.md, a machine-readable topology (docker-compose.yml) and a setup-manifest for downstream tooling.

Quick Start

Invoke the skill with a target profile and platform to generate the environment recipe.

Frequently Asked Questions about environment-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a reproducible docker-compose test environment from a component catalog?

To generate a reproducible docker-compose test environment, this skill resolves catalog components into a portable topology recipe, pinning image versions and attaching healthchecks to every service. It outputs a docker-compose.yml file and a human-facing env-setup.md.

What's the best way to manage secrets in a docker-compose topology for test environments?

To manage secrets in a docker-compose topology safely, this skill enforces routing secrets through a references store rather than embedding them directly. It verifies secret references before emission to ensure secrets are never inlined in the recipe.

Does this environment orchestrator support multiple test profiles like e2e and performance testing?

Yes, this environment orchestrator supports multiple test profiles including unit, integration, e2e, uat, and perf. It activates optional components across web, ios, android, and backend platforms via a defined test-strategy.

How do I ensure safe teardown of test environments in docker-compose?

To ensure safe teardown of test environments, this skill validates a teardownCommand for every catalog component before emission. It enforces six strict catalog fields including teardownCommand to guarantee a teardown-safe environment recipe.

What catalog fields are required to build a valid test environment recipe?

To build a valid test environment recipe, six catalog fields are required: image, ports, env, volumes, healthcheck, and teardownCommand. The orchestrator validates healthchecks and teardowns against these fields before generating the topology.