Use as the entry point for any Field Crops Research (FCR) manuscript. Routes to the right FCR sub-skill based on where you are in the lifecycle and which article type (Original Research Paper, Review, Short Communication, Opinion, Loomis Review) fits. It checks scope-fit first — FCR rejects controlled-environment-only and single-site single-season work — then dispatches; it does not draft content.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-workflow --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fcr Workflow?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-fcr-workflow)More formats (shields.io, HTML) on the badges page.
---
name: fcr-workflow
description: Use as the entry point for any Field Crops Research (FCR) manuscript. Routes to the right FCR sub-skill based on where you are in the lifecycle and which article type (Original Research Paper, Review, Short Communication, Opinion, Loomis Review) fits. It checks scope-fit first — FCR rejects controlled-environment-only and single-site single-season work — then dispatches; it does not draft content.
---
# FCR Workflow Router (fcr-workflow)
The orchestrator for a Field Crops Research submission. Figure out the stage and the **article type**,
then send the user to the matching skill. FCR is an **empirical field-agronomy** journal — the
router's first job is a **scope gate**: is this genuine field-based research with **multi-season
and/or multi-environment** relevance? If not, fix that before anything else.
## When to trigger
- Starting a new FCR paper and unsure where to begin
- Mid-project and unsure which skill applies next
- Deciding which **article type** fits the work
- Returning with a decision letter (route to `fcr-revision-and-rebuttal`)
## Scope gate (ask first, every time)
| Question | If "no" |
|----------|---------|
| Is it **field-based** (not greenhouse/pot/root-restricting only)? | Likely out of scope → `fcr-topic-selection` |
| Does it have **≥ 2 seasons and/or multiple environments**? | Redesign or reframe → `fcr-experimental-design` |
| Is the crop a **field crop** (not horticultural/woody-perennial/non-cultivated)? | Out of scope → `fcr-topic-selection` |
| Is it more than **corroborative / descriptive / local**? | Sharpen the contribution → `fcr-topic-selection` |
## First question: which article type?
| Situation | Article type | Route to |
|-----------|--------------|----------|
| Full original field/modelling study | **Original Research Paper** | normal pipeline below |
| Concise, complete, focused study | **Short Communication** | normal pipeline, tighter scope |
| Critical synthesis of a topic | **Review** (usually invited; propose first) | `fcr-literature-positioning` + `fcr-topic-selection` |
| Perspective / position piece | **Opinion Paper** | `fcr-topic-selection` + `fcr-writing-style` |
| Invited major review | **Loomis Review** (by invitation) | `fcr-literature-positioning` |
## Routing map (stage → skill)
```text
Idea / scope fit? → fcr-topic-selection
Where does it sit in the field? → fcr-literature-positioning
Is the design defensible? → fcr-experimental-design
Are the analyses sound? → fcr-data-analysis
Are the exhibits clear? → fcr-figures-and-tables
Data availability & reporting? → fcr-reporting-and-data-policy
Does it read for agronomists? → fcr-writing-style
Need a cover letter? → fcr-cover-letter
How will it be judged? → fcr-review-process
Ready to submit? → fcr-submission
Got a decision / revision? → fcr-revision-and-rebuttal
```
## Default order
`topic-selection → literature-positioning → experimental-design → data-analysis → figures-and-tables →
reporting-and-data-policy → writing-style → cover-letter → review-process → submission →
revision-and-rebuttal`
Iterate: most papers loop design ↔ analysis ↔ figures several times before writing-style.
## Anti-patterns
- Skipping the scope gate and investing in controlled-environment-only or single-site data
- Treating one season at one site as enough (FCR expects multi-season/-environment relevance)
- Forcing a Review/Opinion frame onto what is really an Original Research Paper
- Leaving the data-availability statement and highlights to the last minute
## Output format
```
【Scope gate】field-based? multi-environment? field crop? more than local? [pass/fix]
【Stage】idea / positioning / design / analysis / exhibits / reporting / writing / cover / review / submit / revise
【Article type】Original Research / Short Communication / Review / Opinion / Loomis Review
【Route to】fcr-<skill>
【Why】one line
【Then】the next skill after that
```
## Supplementary resources
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — agronomy data + software by method
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — official FCR URLs behind every fact in this pack
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!