Build with your agent

Bowerloom brings governance to agent workflows in files that follow you. Start with your existing project and the work you perform manually or with one agent. Your personal agent helps describe roles, handoffs, and review points, then compares them with a fixed team profile. The beta binds setup-file writes to an exact approved plan and records the resulting state. Team declarations remain separate from runtime permissions and execution.

Choose your next step

Your task	Start here
Map your current process into a team specification	Map your existing workflow
Install the CLI for your project	Install Bowerloom
Add pinned skills from npm or GitHub	Add third-party skills
Create a team, skill, or prompt	Create teams, skills, and prompts
Add the reviewed specification to your project	Integrate your first team
Change an installed goal or profile	Revise an installed setup
Understand definitions and approval	Concepts
Find a command, field, or error	Reference

What setup gives you

The fixed template includes a personal-agent profile, team roles, a working agreement, milestones, and two reading guides. The lead scopes the work, the maker prepares a draft, and the reviewer receives both scope and draft. Planning proposes 20 files, and exact approval installs them with one private receipt. The CLI does not import your project, assess goal feasibility, or start workers. Compare the specification with your existing process before approving later project work.

.bowerloom/
├── START-HERE.md
├── startup-review.md
├── working-agreement.md
├── milestones.md
├── skills/personal-assistant/
└── teams/first-team/
    ├── team.yaml
    ├── prompts/
    └── skills/

This reading map shows selected files. Files and configuration lists the full inventory.

Give your agent the docs

Ask your existing agent to read the page for your current task. Each practical guide pairs a human prompt with a precise procedure and its prerequisites. The agent index finds the relevant page, and each page offers its complete Markdown text. A copied prompt grants no new tool access or execution permission. Plans and exact approval explains the operation that you review.

Optional new workspace

If you want a separate unused workspace, follow Prepare a separate workspace. Existing-project integration remains the primary path.

Current support · Roadmap · Bug reports and feedback · Main site