---
name: grow-factory
description: Bootstrap a personal agent workshop for building software, research, and automation with an admin computer, account access, shared guidance, and a started project. Use for initial setup or substantial environment expansion.
---

# Bootstrap the agent workshop

Operate through Claude Code or Codex with shell access. The owner directs the outcome; do the setup, research, code, and infrastructure work. Inspect existing tools, learn the first project and budget, then use [factory-stack](../factory-stack/SKILL.md) for new choices. Establish the workshop for the owner's intended work rather than assuming every project is an app.

Follow the single [ordered setup](../factory-stack/references/setup.md). Use [bootstrap.md](references/bootstrap.md) for capability checks and context layout, [provider access](../../references/access.md) for guided sign-ins, and the [box examples](../../examples/bootstrap/README.md) as the concrete starting implementation.

Start with owner-authorized broad administration of the dedicated factory account and box. Secure credentials on the box and preserve the owner's agreed scope and budget. Tighten daily roles and separate trust domains before teammates, unattended jobs, or production data enter the setup.

Use the [canonical baseline](assets/baseline.md) and [shared workflows](references/shared-workflows.md) across clients. Keep project routing short with [AGENTS.template.md](assets/AGENTS.template.md).

Bootstrap is working when the box is reachable, the chosen agent produces a real response on it, a real `just doctor` or `just check` passes, and the first project has a worktree and next action. Aim for that in the first hour, allowing for signup delays. Then use [factory-work](../factory-work/SKILL.md) to deliver the project and [factory-maintain](../factory-maintain/SKILL.md) to improve from its friction. Do not gate the initial working box on a finished product or improvement project.