// Coordinates multi-agent research work through GitHub issues, branches, and PRs with explicit review and verifier gates. Use when running a swarm, parallel issues, orchestration log, feat/issue-N branches, merge order, consistency pass before merge, or Day 3-style lab workflow.
Finds and synthesizes recent economics literature for a research question, prioritizing top economics journals and strong working-paper venues, resolving paywalled links through IDEAS/RePEc or author webpages, and writing a markdown review. Use when the user asks for a literature search, literature review, related-work scan, paper shortlist, bibliography, or economics article review.
Exports approved spec/tasks.md entries into GitHub issue drafts with labels, branch names, and acceptance criteria. Use when syncing SDD tasks to issues, creating a swarm milestone from spec, or generating labeled issue bodies for feat/issue-N branches.
Guides applied microeconometrics workflows for estimands, identification, specification, inference, and robustness. Use when working on DiD, IV, RD, panel regressions, treatment effects, or empirical design questions.
Structures game-theory analysis across normal-form and extensive-form settings. Use when defining players, actions, information, equilibrium concepts, or comparative statics in strategic interaction problems.
Guides HANK modeling workflows including calibration review, equilibrium checks, and transition diagnostics. Use when working on heterogeneous-agent macro models, household distributions, policy experiments, or transition-path questions.
Supports replication, result handoff, and canonical research pipelines. Use when organizing empirical or quantitative research code, preparing tables and figures, or making work rerunnable by someone else.
| name | github-swarm-orchestration |
| description | Coordinates multi-agent research work through GitHub issues, branches, and PRs with explicit review and verifier gates. Use when running a swarm, parallel issues, orchestration log, feat/issue-N branches, merge order, consistency pass before merge, or Day 3-style lab workflow. |
materials/day3 workflow.spec/tasks.md should be approved (use sdd-orchestrator / SDD skill first).gh auth status succeeds when using GitHub CLI.spec/tasks.md and map checkboxes to GitHub issues (delegate drafting to spec-tasks-to-github skill for issue bodies)..github/ISSUE_TEMPLATE/swarm-task.md fields directly.parallel.sequential and add blocked-by:<N> for the prerequisite issue number.notes/orchestration_log.md.feat/issue-<N>-short-slug unless the milestone declares rig/<stream> (then log it).notes/handoff_<from>_to_<to>.md when streams consume each other's outputs.pr-reviewer subagent on each PR (readonly review first; then apply fixes on the branch).domain:*, invoke the matching domain reviewer agent.replication-verifier: when replication paths, deps, or run instructions change.artifact-coherence-auditor: when paper text, tables/figures, and replication must agree.integration-coordinator (or human): enforce dependency order, rebase if needed, resolve conflicts.automerge-ok and CI + review requirements are satisfied..cursor/rules/research-reproducibility.mdc: relative paths, traceable outputs.notes/orchestration_log.md the durable state mirror alongside GitHub.reference.md in this folder for labels, gh snippets, and phase detail.At end of each captain iteration, report:
notes/orchestration_log.md row states