// 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.
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.
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.
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 | spec-tasks-to-github |
| description | 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. |
spec/tasks.md exists and user wants GitHub issues that trace to task lines or IDs.spec/tasks.md is the approved source for scope.gh label create commands.spec/tasks.md for - [ ] / - [x] items and any task IDs or requirement references.blocked-by:<N>).parallel label.gh issue create --body-file):## Spec trace
- spec/tasks.md: <!-- quote the task line or ID -->
## Acceptance criteria
- [ ] ...
## Branch
`feat/issue-<N>-short-slug` (fill N after issue is created)
## Dependencies
- Labels: <!-- parallel | sequential -->
- blocked-by: <!-- issue numbers, or none -->
## Review / verify
- [ ] pr-reviewer
- [ ] replication-verifier (if applicable)
- [ ] artifact-coherence-auditor (if paper/replication alignment)
blocked-by: on dependent issues.github-swarm-orchestration for execution, or continue in the same session following that skill's phases.gh issue create