Farm Operations
Core operational workflows that maintain project health. Opening the farm for a quick check, and counting the herd for a deep inspection.
Definition
Farm Operations are the core workflows that maintain your project's health. They're the daily rituals of the farm - checking the animals, inspecting the crops. In Farmwork, these are two commands: /audit and /inspect.
Two operations form the backbone of Farmwork's maintenance philosophy: the quick pass (/audit) and the deep pass (/inspect). Both update the same FARMHOUSE.md - only the depth changes.
Philosophy
Core Principle
A farmer doesn't guess at the health of their farm - they check. Regular audits catch problems early, maintain documentation, and ensure you always know the current state of your project.
Real farms have rhythms - morning rounds, seasonal checks, harvest preparation. Farmwork operations provide similar structure for software development, ensuring nothing falls through the cracks and quality remains consistent.
Operation Hierarchy
- Open the farm — Quick health check, start of session
- Count the herd — Deep inspection, before major changes
Opening the Farm
/audit is your morning routine - a comprehensive audit that should run at the start of each development session.
What It Does
- Updates FARMHOUSE.md with current metrics
- Checks idea garden for wilting ideas
- Summarizes audit scores
Daily Habit
Make /audit your first command each session. It takes a minute but ensures you're never surprised by the state of your project. Think of it as checking your email, but for code health.
Counting the Herd
/inspect is a deep inspection - comprehensive code review without making changes. Use it before major features, after significant refactors, or whenever you want a thorough health check.
What It Does
- Runs the code-reviewer agent (quality, security, performance, accessibility)
- Runs the code-cleaner agent to flag lingering console.logs and comments
- Dry run of quality gates (no push)
Spawning agents:
├── code-reviewer → quality, security, performance, a11y
└── code-cleaner → comments, console.logs
Collecting results...Inspection Only
"Count the herd" doesn't fix anything - it reports. It's a diagnostic, not a treatment. Use the findings to plan fixes, then run quality gates when you're ready to push.