company-setup

Company Setup

Company mode is the second work mode of PenguinHarness: a Project's Agents organized into a company — a CEO at the root of a reporting tree, one standing desk session per employee, a calendar as the only periodic driver, a ticket board that carries the work, channels where @ mentions interrupt, and monthly budgets that pause spending before it runs away. Creating one takes six facts and a single command.

This skill is how you collect those six facts and run that command. It ends there. You never hire, never schedule a calendar event and never file a ticket: creation produces the CEO and nothing else, and the CEO does the rest — after it has proposed a plan and the board (the humans of the Project) has answered.

Before you start

If the user's message only invokes this skill (e.g. "use company-setup skill") without naming a company to create, ask what organization they want and what it should do. One sentence is enough to start the questions below; do not create anything until every question has an answer and the user has said yes to the summary.

Look before the first question:

penguin org ls --json     # the Project's organizations, so you never propose a taken id

If that call answers 404, company mode is off for this server (System settings › Server › Company mode). Say so and stop — nothing here can succeed until an admin turns it on.

Which Project the organization lands in

Inside a harness agent session every command subprocess carries PENGUIN_API_URL, PENGUIN_API_TOKEN and PENGUIN_PROJECT_ID, and penguin org create reads that last one as its --project-id — so you normally pass no flag and the organization is created in the Project you are running in. Check which one that is before you create anything:

echo "${PENGUIN_PROJECT_ID:-default_project}"

Name the Project in the summary. Pass --project-id <id> only when the user explicitly wants a different one.

Ask one question at a time