Office
Product strategy framework that maintains the gap between vision and reality, ensuring development stays aligned with goals.
Definition
The Office is Farmwork's product strategy system, housed in _OFFICE/. It maintains two key documents: GREENFIELD.md (vision) and BROWNFIELD.md (reality). The gap between these two is your roadmap.
The /office slash command launches an interactive setup wizard that guides you through defining your product vision, strategy, and optionally creates UX documentation for onboarding and user guides.
Philosophy
Core Principle
GREENFIELD is where you want to go. BROWNFIELD is where you are. Every feature decision can be evaluated against this gap: does it move us closer to the vision?
The terms come from real estate development. A "greenfield" site is undeveloped land - pure potential. A "brownfield" site is previously developed land with existing structures. In software, greenfield is your ideal future; brownfield is your current implementation with all its constraints.
Why Track Both
- Vision without reality is fantasy - you need to know where you are
- Reality without vision is aimless - you need to know where you're going
- The gap defines your work - what needs to be built
- Strategy alignment checks prevent scope creep
- New team members understand context quickly
GREENFIELD.md
GREENFIELD.md defines your product vision - the ideal state you're working toward. It's aspirational but specific:
# Product Vision
## Core Loop
**What:** Task management for remote teams
**Stopping:** Scattered communication, missed deadlines
**Why:** Teams need a single source of truth
## Strategy
- Mobile-first design
- Real-time collaboration
- Integration ecosystem
## Goals
1. Launch MVP with core task features
2. Add team collaboration
3. Build API for integrations
4. Mobile apps
## Success Metrics
- User retention > 60% at 30 days
- NPS > 40
- <2s page load timesCore Loop Framework
The "What/Stopping/Why" framework forces clarity. What does your product do? What problem does it stop? Why does that matter? If you can't answer these simply, your vision needs work.
BROWNFIELD.md
BROWNFIELD.md tracks what's actually implemented - your current reality. It's automatically updated by the brownfield-agent during "go to production":
# Current Implementation
**Last Updated:** 2024-01-15
## Implemented Features
### Task Management
- [x] Create/edit/delete tasks
- [x] Due dates and priorities
- [ ] Recurring tasks
- [ ] Task templates
### Collaboration
- [x] User accounts
- [x] Team workspaces
- [ ] Real-time updates
- [ ] Comments on tasks
### Integrations
- [ ] REST API
- [ ] Webhooks
- [ ] Slack integration
## Technical State
- Framework: Next.js 14
- Database: PostgreSQL
- Auth: NextAuth.js
- Deployment: VercelThe gap between GREENFIELD's goals and BROWNFIELD's checkboxes is your backlog. Features marked as implemented in BROWNFIELD that align with GREENFIELD goals represent progress.
Supporting Documents
The Office system includes optional UX documentation:
| Document | Agent | Purpose |
|---|---|---|
ONBOARDING.md |
onboarding-agent | Tours, tooltips, modals, empty states |
USER_GUIDE.md |
user-guide-agent | Feature documentation, help content |
These documents help maintain consistency in user-facing content. When you add a feature, the agents can suggest onboarding elements and help documentation that aligns with existing patterns.
Workflow
Initial Setup
Run /office to launch the interactive setup wizard:
- Define your product vision (GREENFIELD)
- Document current state (BROWNFIELD)
- Optionally create onboarding documentation
- Optionally create user guide structure
Ongoing Updates
Strategy Alignment
The "go to production" skill checks strategy alignment. If a change doesn't align with GREENFIELD goals, you'll be prompted to either justify the deviation or reconsider the change.