farmlisted

# Farm One command for every input from outside the business. Work out what it is, get the content, pull the ideas, **sort each idea into its lane**, judge it, file what earns it in the canonical home for that lane. Farming is not a content activity. It is the intake for the whole business. A thing read on the internet can be something to say, or something to build, or something to remember, and the same source usually contains more than one. **Blank invocation** means review instead of harvest: look at what is staged and not yet used or promoted (Step 7 says where that lives), and say which is the strongest in each lane. ## Where things live The skill is code and stays wherever this gets kept. What it WRITES lives in one estate directory, outside any code repository, shared by every session that reads it: `~/.claude/content` by default, `SKILLS_ESTATE=/path` moves it anywhere else (a test run, a second brand, a shared machine). Nothing this skill writes goes outside that directory. The estate does not need to exist before the first run: the capture step below creates it. ## Step 0: capture, before anything else **Run this first, always, on every input:** ```sh node .claude/skills/farm/scripts/intake.mjs "<url or text>" --note "<why this got grabbed>" ``` It writes a file to `inbox/` with no network call in front of the write, then says what kind of thing it is and what to do next. It cannot fail, which is the point. **Most of the time this gets found on a phone.**