Use when deciding which qe-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Quantitative Economics (QE) submission. Routes — it does not replace — the specialized skills.
Scanned 6/6/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill qe-workflow --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Qe Workflow?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-qe-workflow)More formats (shields.io, HTML) on the badges page.
---
name: qe-workflow
description: Use when deciding which qe-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Quantitative Economics (QE) submission. Routes — it does not replace — the specialized skills.
---
# QE Workflow Router (qe-workflow)
## Overview
This is the router. It tells you **which qe-* skill to use at the current stage** of a manuscript aimed at *Quantitative Economics* (QE) — the empirically and computationally oriented general-interest journal of the **Econometric Society**, the sister of *Econometrica* (more theoretical/methodological) and *Theoretical Economics* (pure theory). QE rewards papers that **develop or apply quantitative methods to substantive economic questions** — empirical, structural/computational, experimental, or simulation-based — with **documented data and reproducible code**.
Default assumption: unless the user says otherwise, treat the target as QE. Operational tells that you are at QE and not a sibling or a generic top journal: **Econometric Society membership is required to submit** (at least one author a member); there is a **submission fee** (US$100 regular / US$50 student); the manuscript must be **posted publicly during review**; the **ES Data Editor** runs a pre-acceptance reproducibility check (DCAS-compatible, not the JAE archive); QE is **Open Access (CC BY-NC)** with a per-page publication fee, not an APC. Editor as of 2026: **Bernard Salanié** (2025–2029). Re-verify volatile specifics on the official ES pages.
## When to trigger
- The user asks "what should I do next?"
- A draft needs its current bottleneck diagnosed
- Work is ping-ponging between data/estimation, framing, writing, and the response letter
- A QE decision letter arrived and the user needs to switch into revision mode
## Routing table
| Current symptom | Next skill |
|-----------------|------------|
| Question feels narrow / not clearly general-interest quantitative | `qe-topic-selection` |
| Contribution vs. the frontier is fuzzy or undersold | `qe-literature-positioning` |
| The "so what" / one-sentence claim is not sharp | `qe-contribution-framing` |
| Empirical causal design or structural identification is shaky | `qe-identification-strategy` |
| Estimation, moments, or data handling need work | `qe-data-analysis` |
| Exhibits are dense; significance asterisks still present | `qe-tables-figures` |
| Prose buries the idea; abstract/intro do not land | `qe-writing-style` |
| Data/code deposit, README, or ES Data Editor prep | `qe-replication-and-data-policy` |
| Want to understand referee timeline / desk-reject odds / transfer | `qe-review-process` |
| Ready to submit via the ES portal; need a preflight | `qe-submission` |
| Received an R&R; need a response-letter strategy | `qe-rebuttal` |
## Default order
1. `qe-topic-selection` — lock the substantive quantitative question
2. `qe-literature-positioning` — stake the contribution vs. the frontier
3. `qe-contribution-framing` — sharpen the one-sentence claim
4. `qe-identification-strategy` — causal design or structural identification
5. `qe-data-analysis` — estimation, moments, diagnostics
6. `qe-tables-figures` — exhibits without significance asterisks
7. `qe-writing-style` — make the idea land (abstract + intro last)
8. `qe-replication-and-data-policy` — assemble the ES-compliant package
9. `qe-review-process` — calibrate expectations / consider Econometrica transfer
10. `qe-submission` — ES portal preflight
11. `qe-rebuttal` — after the R&R
> `qe-writing-style` is a late-stage polish; do not rewrite the intro before identification/estimation settle.
## Anti-patterns
- Skipping `qe-replication-and-data-policy` until acceptance — the ES Data Editor checks **before** acceptance
- Letting `qe-tables-figures` polish exhibits while estimation is still moving
- Treating QE like Econometrica (method-first) or a generic fee-free top-5 journal
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!