hlr-workflow
Use when starting or navigating any Harvard Law Review (HLR) article, essay, or book review and you need the right next sub-skill. Routes by lifecycle stage and the distinctive student-edited, multi-submit/expedite law-review process. It dispatches; it does not draft content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# HLR Workflow Router (hlr-workflow) The orchestrator for a Harvard Law Review submission. HLR is **student-edited, not peer-reviewed**, and generalist across all of law. The router's first job is to set the right mental model: you write a **near-final** article, run a **preemption check** before drafting, submit broadly across peer journals via **Scholastica** (but to **HLR through its own submission system**, not Scholastica), leverage offers with **expedite** requests, and then survive an intensive student-editor edit plus a full **cite-check / source-pull**. Figure out the stage, then dispatch. ## When to trigger - Starting a new HLR piece and unsure where to begin - Mid-project and unsure which skill applies next - Deciding the piece type (Article, Essay, Book Review, or a Supreme Court Foreword/Comment by invitation) - Holding an offer and deciding whether/how to expedite (route to `hlr-placement-strategy`) - An editor sent edits or a source-pull request (route to `hlr-student-editor-review`) ## First question: which piece type? | Situation | Type | Route to | |-----------|------|----------| | Full original legal argument, novel normative claim | **Article** (long, heavily fo
- When to trigger
- First question: which piece type?
- Routing map (stage → skill)
- Default order
- Law-review reality check (force this before routing)
- Anti-patterns
- Output format
- Supplementary resources
What does the hlr-workflow skill do?
Use when starting or navigating any Harvard Law Review (HLR) article, essay, or book review and you need the right next sub-skill. Routes by lifecycle stage and the distinctive student-edited, multi-submit/expedite law-review process. It dispatches; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.