launch

Automate workspace setup from YAML/TOML templates with variable substitution.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/MantisWare/BizForge --skill launch-mantisware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch
Source: https://github.com/MantisWare/BizForge/tree/main/library/skills/workspace/launch
Command: npx skills add https://github.com/MantisWare/BizForge --skill launch-mantisware

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates standing up a fully configured workspace from a template, reducing setup time and manual coordination.

Core Features & Use Cases

  • Stand up a new workspace from YAML/TOML templates that define hired agents, enabled skills, initial tasks, budgets, and file structure.
  • Automatically provision resources, assign tasks, and bootstrap the operating environment with variable substitution for project-specific customization.
  • Use Case: Quickly deploy a project workspace for a new initiative without editing templates.

Quick Start

Run /launch templates/research-team.yaml to deploy a new workspace from a template.

Frequently Asked Questions about launch

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

FAQPage Schema
How do I automate workspace provisioning from a YAML template?

Automate workspace provisioning by defining a YAML template that specifies agents, skills, tasks, budgets, and file structure, then triggering it with a command like /launch templates/research-team.yaml to deploy instantly.

What is the best way to bootstrap a project workspace with agent configuration and budgets?

Bootstrap a project workspace by using a TOML or YAML template that pre-configures agent provisioning, initial tasks, and budgets, automatically provisioning resources and assigning tasks upon activation without manual editing.

Can I use variable substitution for project-specific customization when deploying workspace templates?

Variable substitution is supported when deploying workspace templates, allowing you to customize project-specific variables for resources, tasks, and file structure during the automated environment bootstrap process.

Do I need specific core primitives to activate a workspace from a template?

Activating a workspace from a template requires access to core primitives like hire, budget, spawn, heartbeat, and board, ensuring the fully configured environment provisions agents and assigns tasks correctly.

Does workspace automation work with both YAML and TOML configuration formats?

Workspace automation supports both YAML and TOML configuration formats for templates, enabling teams to define hired agents, enabled skills, initial tasks, budgets, and file structure for turnkey environment deployment.