Farm Operations
Core operational workflows that maintain project health. Opening and closing the farm, comprehensive inspections, and production deployments.
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, preparing for market. In Farmwork, these translate to audit workflows, code inspections, and deployment preparations.
Four primary operations form the backbone of Farmwork's maintenance philosophy: opening the farm (audit), counting the herd (inspect), going to production (deploy prep), and going to market (global readiness).
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
- Go to production — Deploy preparation, strategy alignment
- Go to market — Global readiness, i18n/a11y
Opening the Farm
"open the farm" 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
- Flags stale research documents
- Reports beads issue status
- Summarizes audit scores
Daily Habit
Make "open the farm" 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
"count the herd" 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 all audit agents in parallel
- Performs code quality analysis
- Security vulnerability scan
- Performance anti-pattern detection
- Accessibility compliance check
- Dry run of quality gates (no push)
Spawning agents in parallel:
├── code-quality → CODE_QUALITY.md
├── security-auditor → SECURITY.md
├── performance-auditor → PERFORMANCE.md
└── accessibility-auditor → ACCESSIBILITY.md
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.
Go to Production
"go to production" prepares your code for deployment. It's the pre-flight checklist that ensures changes are ready for release.
What It Does
- Updates BROWNFIELD.md with implemented features
- Checks alignment with GREENFIELD strategy
- Documents impact analysis
- Generates production readiness report
- Flags any blocking issues
Unlike "count the herd" which is diagnostic, "go to production" is decision-oriented. It answers: Is this ready to ship?
Go to Market
"go to market" ensures your application is ready for a global audience. It's the final polish before releasing to the world.
What It Does
- i18n translation coverage scan
- Missing translation detection
- WCAG accessibility audit
- Global readiness report
Before Launch
Run "go to market" before any public release. Accessibility issues and missing translations are embarrassing to fix post-launch and can exclude users. Better to catch them early.