/pm DevIntern + GitHub Issues
File GitHub Issues from AI drafts without leaving your repository workflow. @devintern/pm creates issues with the context engineers need to open a PR against the same repo.
How it works
What DevIntern does with GitHub Issues
Each product path keeps GitHub Issues as the handoff surface. No rip-and-replace, no new dashboard.
/pm Create GitHub Issues from AI drafts
- 1 Set TASK_TRACKER=github with a fine-grained or classic token.
- 2 Run devpm --interactive with your source material.
- 3 Review the draft and open the issue on your repository.
Capabilities
Built for real GitHub Issues workflows
GitHub REST API for issue creation
Issue type selection in the interactive flow
Same-repo context for engineering handoff
Pairs naturally with @devintern/code on GitHub PRs
Token scoped to the repositories you configure
Get connected
Setup guides and configuration
Credentials stay in project-local .env files. DevIntern runs on your machine or server, not a shared implementation cloud.
FAQ
Common questions about GitHub Issues
Can @devintern/code implement GitHub Issues directly?
Code implements Jira, Trello, and Markdown tasks today. A common pattern is PM filing GitHub Issues, then engineers running Code against Jira or Markdown mirrors of the same work.
What token scopes are required?
Issues read and write on the target repository. Use a fine-grained PAT limited to the repos DevIntern should touch.
Try DevIntern with GitHub Issues
Connect GitHub Issues, run your first workflow, and keep the trackers, repos, and reviewers your team already trusts.
14-day trial · perpetual license · BYO model keys