company

Orchestrate cross-department projects through autonomous CEO-led sub-manager governance.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/raphaelVRA/company_agents --skill company-raphaelvra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: company
Source: https://github.com/raphaelVRA/company_agents/tree/main/company
Command: npx skills add https://github.com/raphaelVRA/company_agents --skill company-raphaelvra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform a Claude session into an autonomous CEO/Founder that orchestrates a complete virtual company through department sub-managers, enabling cross-domain delivery without direct execution by individuals.

Core Features & Use Cases

  • Activate department sub-managers and align cross-department work via a shared state folder.
  • Orchestrate cross-team delivery, arbitrate conflicts, and publish executive updates without writing code.
  • Use cases include MVP projects (startup mode) and full-enterprise initiatives requiring multiple departments.

Quick Start

Provide a project mission and target departments, and I will generate the charter, activate departments, and begin execution.

Frequently Asked Questions about company

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

FAQPage Schema
How do I orchestrate cross-department workflows with multiple team handoffs in Claude?

To orchestrate cross-department workflows, this Skill transforms your Claude session into a CEO-led virtual company. It activates department sub-managers, aligns work via shared state files, and enforces charter-first execution to manage handoffs without direct code delivery.

What is a virtual company orchestration framework and when do I need it?

Virtual company orchestration is a governance mechanism where a CEO agent coordinates department sub-managers to execute cross-domain projects. You need it for complex initiatives requiring multiple teams, from startup MVPs to enterprise-scale cross-department delivery.

Can I use this orchestration approach for both startup MVPs and enterprise projects?

Yes, this orchestration approach supports both startup MVPs and full-enterprise initiatives. It scales by activating relevant department heads and applying sub-manager governance to coordinate cross-team delivery and arbitrate conflicts.

How do I set up a charter and activate departments for project execution?

To set up a charter and activate departments, provide your project mission and target departments. The Skill generates the execution charter, activates the required department sub-managers, and initiates orchestration automatically.

Why use a shared state folder for cross-team project orchestration?

You use a shared state folder to establish shared-state contracts between departments. This mechanism allows sub-managers to align cross-team work, track handoffs, and arbitrate conflicts without requiring direct execution from individual contributors.

What are the limitations of using a CEO-led autonomous orchestration for project delivery?

A limitation of CEO-led autonomous orchestration is that it enforces governance without delivering work directly. It orchestrates sub-managers and handoffs, meaning actual code or content execution relies entirely on the underlying Claude session capabilities.