🗺️ Agriculture & AgTech · Journey Playbooks

Playbook: Systemize your season

Rotation design, compliant input records, and data-driven irrigation in one operating rhythm.

journey~90 minFarm ManagersAgronomistsAgTech Builders

Journey Steps

1Step 1 — Design crop rotations that build, not mine, soil: start with "Map fields with soil test history; group by capability not habit"
2Step 2 — Steward inputs with application records that protect you: start with "Read the label as law: rates, REI/PHI, buffers recorded before purchase fits use"
3Step 3 — Schedule irrigation on data instead of habit: start with "Place sensors by zone representativeness and root depth of the crop stage"
4How it fits together: Records written at application time are worth ten reconstructed after audits.

Commands

Install all referenced skills

$ npx skills add aniruddhaadak80/skills --skill crop-planning-rotation-plan-design && npx skills add aniruddhaadak80/skills --skill crop-planning-input-stewardship-records && npx skills add aniruddhaadak80/skills --skill farm-data-tech-water-scheduling-efficiency

Tags

#playbook#journey#agriculture-agtech

Install this skill

$ npx skills add aniruddhaadak80/skills --skill playbook-agriculture-agtech-season-systems -a opencode

SKILL.md

# Playbook: Systemize your season

> Rotation design, compliant input records, and data-driven irrigation in one operating rhythm.

## When to Use This Skill

Rotation design, compliant input records, and data-driven irrigation in one operating rhythm.

## Steps

1. Step 1 — Design crop rotations that build, not mine, soil: start with "Map fields with soil test history; group by capability not habit"
2. Step 2 — Steward inputs with application records that protect you: start with "Read the label as law: rates, REI/PHI, buffers recorded before purchase fits use"
3. Step 3 — Schedule irrigation on data instead of habit: start with "Place sensors by zone representativeness and root depth of the crop stage"
4. How it fits together: Records written at application time are worth ten reconstructed after audits.

View source on GitHub ↗

Take retrieval-augmented answers from empty repo to evaluated production feature.

🗺️ AI Engineering·~135m

Open →

🗺️Playbook: Harden an agent before giving it toolsjourney

Ship an autonomous agent whose failure modes are cheap, visible, and reversible.

🗺️ AI Engineering·~125m

Open →

🗺️Playbook: Cut LLM costs without quality collapsejourney

Reduce monthly inference spend measurably while keeping answer quality within tolerance.

🗺️ AI Engineering·~95m

Open →