A cheat sheet and command reference for managing Agent Farm workflows and builders.

Install

mkdir -p .claude/skills/af && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13177" && unzip -o skill.zip -d .claude/skills/af && rm skill.zip

Installs to .claude/skills/af

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Agent Farm CLI quick reference. Use when running af commands to check correct syntax, subcommands, and flags. Prevents guessing at command names.
145 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Start and stop the Tower dashboard server
  • Tail Tower logs and check its status
  • Start, stop, and open the architect dashboard for the current project
  • Spawn builders for different protocols (SPIR, bugfix)
  • Resume builders in existing worktrees
  • Clean up builder worktrees

How it works

The skill provides a quick reference for `af` CLI commands, enabling users to manage the Tower server, architect dashboard, and builder processes, including spawning, resuming, and cleaning up worktrees.

Inputs & outputs

You give it
Subcommands like 'tower start', 'dash open', 'spawn 3 --protocol spir', 'cleanup --project 3'
You get back
Running Tower server, opened dashboard, spawned builders, cleaned worktrees, or status information

When to use af

  • Check CLI command syntax
  • Restart builders
  • Manage tower server
  • Cleanup worktrees

About this skill

Agent Farm Quick Reference

Tower (Dashboard Server)

af tower start             # Start Tower on port 4100
af tower stop              # Stop Tower
af tower log               # Tail Tower logs
af tower status            # Check if Tower is running

There is NO af tower restart — use af tower stop && af tower start.

Dashboard

af dash start              # Start architect dashboard for current project
af dash stop               # Stop dashboard for current project
af dash open               # Open dashboard in browser

Builder Management

af spawn 3 --protocol spir     # Spawn builder for SPIR project
af spawn 3 --protocol spir --soft  # Spawn builder (soft mode)
af spawn 3 --protocol bugfix   # Spawn builder for a bugfix
af spawn 3 --resume            # Resume builder in existing worktree
af status                      # Check all builder status
af cleanup --project 3         # Clean up builder worktree (safe)
af cleanup --project 3 -f      # Force cleanup

Resuming Builders

When a builder's Claude process dies but the worktree and porch state survive, use --resume to restart it without recreating the worktree:

af spawn 3 --resume

This reuses the existing .builders/3 worktree, creates a fresh terminal session registered with the Tower (so it appears in the dashboard), and lets porch pick up from whatever phase the builder was in. Works with all spawn modes: positional issue number, --task, --protocol, --worktree.

Utility

af util                    # Open utility shell
af open file.ts            # Open file in annotation viewer
af ports list              # List port allocations
af send <builder> "msg"    # Send message to a builder

Configuration

Edit af-config.json at project root to customize shell commands.

{
  "shell": {
    "architect": "claude",
    "builder": "claude",
    "shell": "bash"
  }
}

Pre-Spawn Checklist

Before af spawn, commit all local changes. Builders work in git worktrees branched from HEAD — uncommitted files (specs, plans, codev updates) are invisible to the builder. The spawn command will refuse if the worktree is dirty (override with --force).

Common Mistakes

  • Spawning with uncommitted changes — builder won't see specs, plans, or codev updates
  • There is NO codev tower command — Tower is managed via af tower
  • There is NO restart subcommand — stop then start
  • There is NO af start for Tower — use af tower start or af dash start

When not to use it

  • When restarting Tower (use stop then start)
  • When spawning builders with uncommitted local changes
  • When using `codev tower` command (does not exist)

Limitations

  • No `af tower restart` command exists
  • No `codev tower` command exists
  • Spawning builders with uncommitted changes is not allowed by default

How it compares

This skill acts as a direct reference for specific `af` CLI commands, preventing users from guessing syntax and ensuring correct usage for managing Agent Farm components, unlike general command-line help.

Compared to similar skills

af side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
af (this skill)04moReviewBeginner
setup121moNo flagsBeginner
tmux202moReviewIntermediate
macos-cleaner162moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry