Name: pm:import
Author: rafeekpro

Prompt file imported from rafeekpro/telegram-chat-getter (.claude/commands/pm:import.md). Fill in {{arguments}} before use. Copyright stays with the author.

Import

Import existing GitHub issues into the PM system.

Usage

/pm:import [--epic <epic_name>] [--label <label>]

Options:

--epic - Import into specific epic
--label - Import only issues with specific label
No args - Import all untracked issues

Required Documentation Access

MANDATORY: Before project management workflows, query Context7 for best practices:

Documentation Queries:

mcp://context7/agile/epic-management - epic management best practices
mcp://context7/project-management/issue-tracking - issue tracking best practices
mcp://context7/agile/task-breakdown - task breakdown best practices
mcp://context7/project-management/workflow - workflow best practices

Why This is Required:

Ensures adherence to current industry standards and best practices
Prevents outdated or incorrect implementation patterns
Provides access to latest framework/tool documentation
Reduces errors from stale knowledge or assumptions

Instructions

1. Fetch GitHub Issues

# Get issues based on filters
if [[ "{{arguments}}" == *"--label"* ]]; then
  gh issue list --label "{label}" --limit 1000 --json number,title,body,state,labels,createdAt,updatedAt
else
  gh issue list --limit 1000 --json number,title,body,state,labels,createdAt,updatedAt
fi

2. Identify Untracked Issues

For each GitHub issue:

Search local files for matching github URL
If not found, it's untracked and needs import

3. Categorize Issues

Based on labels:

Issues with "epic" label → Create epic structure
Issues with "task" label → Create task in appropriate epic
Issues with "epic:{name}" label → Assign to that epic
No PM labels → Ask user or create in "imported" epic

4. Create Local Structure

For each issue to import:

If Epic:

mkdir -p .claude/epics/{epic_name}
# Create epic.md with GitHub content and frontmatter

If Task:

# Find next available number (001.md, 002.md, etc.)
# Create task file with GitHub content

Set frontmatter:

name: {issue_title}
status: {open|closed based on GitHub}
created: {GitHub createdAt}
updated: {GitHub updatedAt}
github: https://github.com/{org}/{repo}/issues/{number}
imported: true

5. Output

📥 Import Complete

Imported:
  Epics: {count}
  Tasks: {count}
  
Created structure:
  {epic_1}/
    - {count} tasks
  {epic_2}/
    - {count} tasks
    
Skipped (already tracked): {count}

Next steps:
  Run /pm:status to see imported work
  Run /pm:sync to ensure full synchronization

Important Notes

Preserve all GitHub metadata in frontmatter. Mark imported files with imported: true flag. Don't overwrite existing local files.

Install pm:import and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Import Import existing GitHub issues into the PM system. ## Usage ``` /pm:import [--epic <epic_name>] [--label <label>] ``` Options: - `--epic` - Import into specific epic - `--label` - Import only issues with specific label - No args - Import all untracked issues ## Required Documentation Access **MANDATORY:** Before project management workflows, query Context7 for best practices: **Documentation Queries:** - `mcp://context7/agile/epic-management` - epic management best practices - `mcp://context7/project-management/issue-tracking` - issue tracking best practices - `mcp://context7/agile/task-breakdown` - task breakdown best practices - `mcp://context7/project-management/workflow` - workflow best practices **Why This is Required:** - Ensures adherence to current industry standards and best practices - Prevents outdated or incorrect implementation patterns - Provides access to latest framework/tool documentation - Reduces errors from stale knowledge or assumptions ## Instructions ### 1. Fetch GitHub Issues ```bash # Get issues based on filters if [[ "{{arguments}}" == *"--label"* ]]; then gh issue list --label "{label}" --limit 1000 --json number,title,body,state,labels,createdAt,updatedAt else gh issue list --limit 1000 --json number,title,body,state,labels,createdAt,updatedAt fi ``` ### 2. Identify Untracked Issues For each GitHub issue: - Search local files for matching github URL - If not found, it's untracked and needs import ### 3. Categorize Issues Based on labels: - Issues with "epic" label → Create epic structure - Issues with "task" label → Create task in appropriate epic - Issues with "epic:{name}" label → Assign to that epic - No PM labels → Ask user or create in "imported" epic ### 4. Create Local Structure For each issue to import: **If Epic:** ```bash mkdir -p .claude/epics/{epic_name} # Create epic.md with GitHub content and frontmatter ``` **If Task:** ```bash # Find next available number (001.md, 002.md, etc.) # Create task file with GitHub content ``` Set frontmatter: ```yaml name: {issue_title} status: {open|closed based on GitHub} created: {GitHub createdAt} updated: {GitHub updatedAt} github: https://github.com/{org}/{repo}/issues/{number} imported: true ``` ### 5. Output ``` 📥 Import Complete Imported: Epics: {count} Tasks: {count} Created structure: {epic_1}/ - {count} tasks {epic_2}/ - {count} tasks Skipped (already tracked): {count} Next steps: Run /pm:status to see imported work Run /pm:sync to ensure full synchronization ``` ## Important Notes Preserve all GitHub metadata in frontmatter. Mark imported files with `imported: true` flag. Don't overwrite existing local files.

{ "prompt": "# Import\n\nImport existing GitHub issues into the PM system.\n\n## Usage\n```\n/pm:import [--epic <epic_name>] [--label <label>]\n```\n\nOptions:\n- `--epic` - Import into specific epic\n- `--label` - Import only issues with specific label\n- No args - Import all untracked issues\n\n## Required Documentation Access\n\n**MANDATORY:** Before project management workflows, query Context7 for best practices:\n\n**Documentation Queries:**\n- `mcp://context7/agile/epic-management` - epic management best practices\n- `mcp://context7/project-management/issue-tracking` - issue tracking best practices\n- `mcp://context7/agile/task-breakdown` - task breakdown best practices\n- `mcp://context7/project-management/workflow` - workflow best practices\n\n**Why This is Required:**\n- Ensures adherence to current industry standards and best practices\n- Prevents outdated or incorrect implementation patterns\n- Provides access to latest framework/tool documentation\n- Reduces errors from stale knowledge or assumptions\n\n\n## Instructions\n\n### 1. Fetch GitHub Issues\n\n```bash\n# Get issues based on filters\nif [[ \"{{arguments}}\" == *\"--label\"* ]]; then\n gh issue list --label \"{label}\" --limit 1000 --json number,title,body,state,labels,createdAt,updatedAt\nelse\n gh issue list --limit 1000 --json number,title,body,state,labels,createdAt,updatedAt\nfi\n```\n\n### 2. Identify Untracked Issues\n\nFor each GitHub issue:\n- Search local files for matching github URL\n- If not found, it's untracked and needs import\n\n### 3. Categorize Issues\n\nBased on labels:\n- Issues with \"epic\" label → Create epic structure\n- Issues with \"task\" label → Create task in appropriate epic\n- Issues with \"epic:{name}\" label → Assign to that epic\n- No PM labels → Ask user or create in \"imported\" epic\n\n### 4. Create Local Structure\n\nFor each issue to import:\n\n**If Epic:**\n```bash\nmkdir -p .claude/epics/{epic_name}\n# Create epic.md with GitHub content and frontmatter\n```\n\n**If Task:**\n```bash\n# Find next available number (001.md, 002.md, etc.)\n# Create task file with GitHub content\n```\n\nSet frontmatter:\n```yaml\nname: {issue_title}\nstatus: {open|closed based on GitHub}\ncreated: {GitHub createdAt}\nupdated: {GitHub updatedAt}\ngithub: https://github.com/{org}/{repo}/issues/{number}\nimported: true\n```\n\n### 5. Output\n\n```\n📥 Import Complete\n\nImported:\n Epics: {count}\n Tasks: {count}\n \nCreated structure:\n {epic_1}/\n - {count} tasks\n {epic_2}/\n - {count} tasks\n \nSkipped (already tracked): {count}\n\nNext steps:\n Run /pm:status to see imported work\n Run /pm:sync to ensure full synchronization\n```\n\n## Important Notes\n\nPreserve all GitHub metadata in frontmatter.\nMark imported files with `imported: true` flag.\nDon't overwrite existing local files.", "variables": [ "arguments" ], "notes": "Import existing GitHub issues into the PM system. Tools: Bash, Read, Write, LS.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/rafeekpro/telegram-chat-getter", "path": ".claude/commands/pm:import.md", "ref": "6ddd3a99ad5a068b7db86450ff40302ddaddea4d", "url": "https://github.com/rafeekpro/telegram-chat-getter/blob/6ddd3a99ad5a068b7db86450ff40302ddaddea4d/.claude/commands/pm:import.md", "key": "rafeekpro/telegram-chat-getter/.claude/commands/pm:import.md" } } }

pm:import

About