devintern

Learn how to use @devintern/pm effectively

Usage

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

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 the story to an existing epic. This step is skipped for trackers that do not support a real epic/parent hierarchy (Trello, GitHub Issues, and Markdown). Supported by Jira, Linear, Azure DevOps, and Asana.
  5. Issue type (Jira, Azure DevOps, GitHub, Markdown only): Select Story, Task, Bug, Epic, or enter a custom type. 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

Features:

  • Step-by-step guided workflow
  • Keyboard navigation (Enter to confirm, ESC to go back, Ctrl+C to exit)
  • Header shows active tracker and project as Tracker/Project (e.g., Jira/PROJ, Trello/My Board) so you always know your context
  • Press Ctrl+P at any step to switch to a different project without restarting
  • Visual preview of your configuration
  • No need to remember command-line flags
  • Works great for both technical and non-technical users

CLI Usage (For Power Users)

For power users who prefer command-line flags:

devpm --figma <url> [options]
devpm --log <text> [options]
devpm --prompt <text> [options]

Source Options (one required)

  • --figma <url>: Figma design node URL to analyze
  • --log <text>: Error log or bug report text to analyze
  • --prompt <text>: Free-form text describing requirements or features

Additional Options

  • --epic, -e <key>: Link the created story to an epic (e.g., PROJ-100). Ignored for trackers that do not support a real epic/parent hierarchy (Trello, GitHub Issues, Markdown).
  • --type, -t <type>: Issue type (default: “Task”). Common types: Task, Story, Bug, Epic. Only applied by backends that support issue types (Jira, Azure DevOps, GitHub, Markdown); ignored by Linear, Trello, and Asana.
  • --custom, -c <text>: Additional custom instructions for the requirements
  • --style, -s <type>: Prompt style: “pm” (default) or “technical”
    • pm: Focuses on user stories and acceptance criteria
    • technical: Includes Technical Considerations section
  • --model, -m <model>: AI model to use (e.g., “sonnet”, “opus”, or full model name)
  • --decompose: Decompose the story into subtasks (default: off)
  • --confirm: Interactively confirm each subtask before creating
  • --verbose, -v: Enable verbose API logging for debugging (same as setting DEVINTERN_VERBOSE=1)
  • --help, -h: Show help message

Examples

Figma designs:

Note: Figma functionality requires the Figma MCP server to be installed and configured in your AI agent (Claude Code only).

devpm --figma "https://www.figma.com/design/abc/file?node-id=123-456"
devpm --figma "https://..." --epic PROJ-100
devpm --figma "https://..." -c "Focus on accessibility"
devpm --figma "https://..." --style technical --decompose
devpm --figma "https://..." --type Task

Error logs:

devpm --log "Error: Cannot read property 'id' of undefined at line 42"
devpm --log "$(cat error.log)" --epic PROJ-200 --type Bug
devpm --log "Stack trace..." --style technical --model opus

Free-form prompts:

devpm --prompt "Add user profile settings page with theme preferences"
devpm --prompt "$(cat requirements.txt)" --epic PROJ-300
devpm --prompt "Implement OAuth login" --style technical --decompose

How It Works

  1. Input Analysis: Your AI agent analyzes your input:
    • Figma designs: Uses the Figma MCP integration to extract design specifications
    • Error logs: Parses error messages and stack traces to identify root causes
    • Free-form prompts: Interprets requirements and feature descriptions
  2. Story Creation: Creates a comprehensive story with:
    • User story format
    • Acceptance criteria
    • Technical considerations
    • Design notes (for Figma) or reproduction steps (for bugs)
  3. Epic Linking (optional): Links the story to the specified epic. Only runs for trackers with a real epic/parent hierarchy (Jira, Linear, Azure DevOps, Asana). Skipped for Trello, GitHub Issues, and Markdown.
  4. Task Decomposition (optional): Breaks down the story into subtasks that are:
    • Focused on single responsibilities
    • Completable within 1-2 days
    • Properly linked to the parent story