devintern

Get up and running with @devintern/pm in minutes

Quick Start

@devintern/pm automates story and task creation across multiple project management tools with AI. Transform Figma designs, error logs, or requirements into well-structured issues in seconds.

Prerequisites

  • Bun runtime: Required to run @devintern/pm (the tool is built with Bun)
  • AI agent CLI installed and configured (e.g., Claude Code, OpenCode, Codex, Cursor)
  • Account with at least one supported PM tool (Jira, Linear, Trello, Azure DevOps, Asana, or GitHub)
  • For Figma functionality: Figma MCP server must be installed and configured in your AI agent (Claude Code only)

Installation

Install globally with Bun:

bun install -g @getdevintern/pm

Initialize Configuration

Navigate to your project directory and run:

devpm init

In a terminal, this starts an interactive setup wizard that:

  • Detects an existing @devintern/code configuration (.devintern-code/.env) in the same project and offers to reuse those tracker credentials, so you skip straight to validation
  • Asks which tracker you use (Jira, Linear, Trello, Azure DevOps, Asana, GitHub Issues, or markdown files)
  • Links you directly to the provider’s token creation page and prompts for each credential, with a pointer to the matching setup guide in these docs
  • Validates the connection with a real API call before finishing (you can retry, edit values, or skip)
  • Writes your answers to .devintern-pm/.env and updates your .gitignore to exclude .devintern-pm/.env (to prevent leaking secrets)

For scripted or CI setups, pass --yes (or --no-interactive) to skip the prompts and write the configuration template instead. The non-interactive path also migrates matching values from .devintern-code/.env if present:

devpm init --yes

First Run

The interactive mode provides a step-by-step terminal UI for creating tasks. This is the recommended way to use @devintern/pm:

devpm --interactive

The interactive mode will guide you through:

  1. Source type selection: Choose between Figma URL, error log, or free-form prompt
  2. Source input: Enter your Figma URL, error log, or requirements
  3. Custom instructions (optional): Add additional requirements or focus areas
  4. Epic linking (optional): Link to an existing Jira epic
  5. Issue type (Jira, Azure DevOps, GitHub, Markdown only): Select Task, Story, Bug, Epic, or enter a custom type. Task is the default; press Enter to accept it. This step is skipped for Linear, Trello, and Asana, which do not support setting an issue type.
  6. Prompt style: Choose between PM style or Technical style
  7. Confirmation: Review your configuration before proceeding

What’s Next?