What is Farmwork?

A framework grounded in field-tested codebase maintenance rules—using systematic, AI-assisted workflows to keep software high quality and shippable.

Farmwork

Skills

Auto-activating workflows that respond to natural phrases. Say "open the farm" to audit systems, /push to ship to production.

Living Audits

Self-updating documentation that tracks project health. Security, performance, accessibility, and code quality audits that stay current.

Agentic Harness

Specialized AI agents for code review, security analysis, and performance optimization. Each agent has a focused role and defined tools.

Supplies

Stock your farm with tools and MCP integrations. Add just, beads, knip, or connect to Storybook, Sentry, and more.

Issue Tracking
Plan-First Development
Quality Gates

Skills

Skills auto-activate when you speak naturally. The farming metaphor makes workflows memorable and reliable.

Farmwork
🌾 "open the farm"

Audit your systems and update FARMHOUSE.md with current metrics. Run this at the start of each session.

Audit Metrics
🐄 "count the herd"

Full code inspection + dry run. Runs code review, cleanup, performance, security, and accessibility checks without pushing.

Review Security Quality
🛒 "go to market"

i18n translation scan + accessibility audit. Ensure your app is ready for a global audience.

i18n Accessibility
🏭 "go to production"

Production readiness check. Updates BROWNFIELD.md, checks strategy alignment, notes documentation impacts.

Strategy Docs

Plan Phrases

"make a plan for..." Create implementation plan in _PLANS/
"let's implement..." Load plan, create Epic + issues, start work

Idea Phrases

"I have an idea for..." Plant new idea in GARDEN.md
"let's plan this idea..." Graduate idea from GARDEN to _PLANS/
"compost this..." Reject idea, move to COMPOST.md
"water the garden" Generate 10 new ideas based on GARDEN and COMPOST

Research Phrases

"let's research..." Create or update research document in _RESEARCH/
"update research on..." Refresh existing research with new findings
"show research on..." Display research summary and staleness status

Slash Commands

/push Lint, test, build, commit, push to production (11 steps)
/office Interactive guided setup: GREENFIELD vision, strategy, optional docs

Supplies

Stock your farm with the tools you need. Built-in supplies extend your workflow, while MCP supplies connect Claude to external services.

Built-in Supplies

just Command Runner

Save and run project-specific commands with a simple justfile.

beads Issue Tracking

Local, markdown-based issue tracking. Issues live in your repo.

knip Dead Code Detection

Find unused files, dependencies, and exports. Reports to KNIP.md.

MCP Supplies

storybook Components

Connect Claude to your component library for documentation.

context7 Documentation

Up-to-date library documentation, not just training data.

sentry Error Tracking

Access error tracking to debug production problems.

images AI Generation

Generate images with Gemini or OpenAI's gpt-image-1.

bash
# Add supplies during init or anytime
farmwork supply
Learn More About Supplies

Project Structure

A clean, opinionated folder structure that keeps your AI-assisted project organized.

Farmwork
your-project/
├── CLAUDE.md              # Lean instructions (refs skills)
├── AGENTS.md              # Generic AI assistant guide
├── .claude/               # Claude Code configuration
│   ├── skills/            # Auto-activating workflows
│   │   ├── farm-audit/            # "open the farm"
│   │   ├── farm-inspect/          # "count the herd"
│   │   ├── garden/                # idea management
│   │   ├── research/              # "let's research..."
│   │   ├── production/            # "go to production"
│   │   └── market/                # "go to market"
│   ├── agents/            # 15 specialized subagents
│   │   ├── the-farmer.md          # Audit + update FARMHOUSE
│   │   ├── code-quality.md        # Review, DRY, complexity
│   │   ├── security-auditor.md    # OWASP vulnerability scan
│   │   └── ... # 12 more agents
│   └── commands/          # Slash commands (/push)
│       ├── push.md                # Lint, test, build, push
│       └── office.md              # Strategy setup
├── _AUDIT/                # Living audit documents
│   ├── FARMHOUSE.md       # Framework command center
│   ├── GARDEN.md          # Idea nursery (pre-plan)
│   ├── COMPOST.md         # Rejected ideas archive
│   └── ... # security, performance, etc.
├── _OFFICE/               # Product strategy + UX
│   ├── GREENFIELD.md      # Vision (where we want to go)
│   ├── BROWNFIELD.md      # Reality (what's implemented)
│   └── ... # onboarding, user guide
├── _PLANS/                # Implementation plans
├── _RESEARCH/             # Research documents
├── .beads/                # Issue tracking
└── justfile               # Navigation commands

Living Documents

_AUDIT/ files are living documents. Update them, don't delete them. Only track open items and include audit history.

Issue-First Workflow

Always create beads issues before starting work. This provides full visibility and historical record of changes.

Multi-Provider Support

Works with Claude Code, OpenAI Codex, Gemini CLI, and any agentic workflow supporting AGENTS.md. Skills and slash commands are Claude Code only.

Skill Activation Hook

Farmwork adds a UserPromptSubmit hook that reminds Claude to check for applicable skills on each message. This ensures reliable skill activation without context drift.

Required Tools

Claude Code Full support (skills + agents + commands)
Codex CLI Phrases + AGENTS.md
Gemini CLI Phrases + AGENTS.md

Beads

Local issue tracking

cargo install beads

Just

Command runner

brew install just

Node.js

Runtime environment

nvm install 22

You

Ready to develop

npx farmwork init

13 Specialized Agents

Each agent has a focused role, defined tools, and specific instructions. Automatically created by farmwork init. Subagents require Claude Code.

Farmwork

the-farmer

Audit and update FARMHOUSE.md metrics

code-quality

Code review, DRY violations, complexity

security-auditor

OWASP vulnerability scanning

performance-auditor

Memory leaks, re-renders, anti-patterns

accessibility-auditor

WCAG 2.1 compliance, alt text, contrast

code-cleaner

Dead code, comments, console.logs

i18n-locale-translator

Translate UI text to locales

idea-gardener

Manage GARDEN and COMPOST ideas

researcher

Systematic research before planning

strategy-agent

GREENFIELD vision + strategy alignment

brownfield-agent

Track implemented features in BROWNFIELD.md

onboarding-agent

Tours, tooltips, modals, empty states

user-guide-agent

Feature documentation for help docs

/

Slash Commands (Explicit Actions)

/push Lint, test, build, commit, push (11 steps)
/office Interactive strategy setup: GREENFIELD, BROWNFIELD, docs

Command Line Interface

Install globally via npm and use these commands to manage your Farmwork setup.

Farmwork
farmwork init

Interactive setup wizard. Creates all folders, agents, commands, and audit files.

Creates:
  • CLAUDE.md + AGENTS.md
  • .claude/skills/ (6 skills)
  • .claude/agents/ (15 agents)
  • .claude/commands/ (2 commands)
  • _AUDIT/ (8 audit files)
  • _OFFICE/ (3 strategy docs)
  • _PLANS/
  • _RESEARCH/
  • justfile
-f, --force Overwrite existing files
farmwork status

Display Farmwork status and metrics for your project.

Shows:
  • Component counts
  • Office documents
  • Research documents
  • Issue tracking status
  • FARMHOUSE score
  • Project metrics
farmwork doctor

Diagnose your Farmwork setup and check for issues.

Checks:
  • Core files & agents
  • Audit system
  • Research system
  • Office system
  • Navigation (justfile)
  • Issue tracking (beads)
  • Security (.gitignore)
farmwork supply

Add supplies to your farm - tools and MCP integrations.

Available:
  • Storybook
  • Context7
  • Sentry
  • Images (Gemini/OpenAI)
[name] Optional: install specific supply

Quick Start

Get up and running in under a minute with the Farmwork CLI.

01

Install Farmwork

bash
npm install -g farmwork
02

Initialize Your Project

Run the interactive setup wizard in your project directory.

bash
cd your-project
farmwork init
03

Verify Setup

Check that everything is configured correctly.

bash
farmwork doctor
farmwork status
04

Start Farming

Open Claude Code and speak naturally - skills auto-activate.

terminal
$ claude

Claude Code v1.0.0
Ready to assist...

> open the farm

✓ Auditing systems...
✓ Updating FARMHOUSE.md...
✓ Farm is open!
Farmwork

Farmwork Tycoon

Experience the core concepts of Farmwork in a fun, gamified way! Build and manage your agentic farm, optimize workflows, and grow your codebase empire. Powered by the Wynter Code desktop app for Mac.

Best Practices

1

Issue-First Development

Claude automatically creates beads issues and epics before starting work. Check your progress anytime, and context persists across sessions.

2

Plan Before Implement

Say "make a plan for X", review, then "let's implement X". Claude creates beads issues from the plan and works through them as todos.

3

Regular Audits

Run "open the farm" regularly to keep FARMHOUSE.md current and track project health.

4

Living Documents

Claude keeps _AUDIT/ files updated automatically. Check them anytime to track security, performance, and code quality progress.