jpube-identification-strategy

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-identification-strategy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Identification Strategy (jpube-identification-strategy) ## When to trigger - The empirical core is OLS + controls with an undefended causal claim - A reform DID uses two-way fixed effects (TWFE) on staggered timing - A bunching estimate lacks a defensible counterfactual density - An IV's policy instrument has an unargued exclusion restriction - You are unsure the design clears the JPubE public-finance bar ## The JPubE identification bar JPubE rewards **credible identification of a policy-relevant parameter**, evaluated by public-finance specialists under single anonymized review (a minimum of two reviewers, with author identity known to them). Because the field's payoff is usually a behavioral elasticity feeding a welfare formula, the design must pin down the response to a tax, transfer, or program rule cleanly. The credibility ranking referees implicitly apply (strong → weaker): 1. **Bunching / notch designs** at a known kink or eligibility threshold, recovering an elasticity from excess mass 2. **RDD / RKD** at a sharp policy cutoff (eligibility, benefit schedule kink) 3. **DID / event study** off a credibly exogenous reform rollout, with modern estimators 4. **IV** with a poli