gh-coalesce-labs-catalyst-plugins-meta/commands/import_workflow.md

description, category, tools, model, version, workspace_only

description	category	tools	model	version	workspace_only
Import and adapt a workflow from external repositories	workflow-discovery	Read, Write, Edit, mcp__deepwiki__ask_question	inherit	1.0.0	true

Import Workflow

You are tasked with importing and adapting workflows from external Claude Code repositories into this workspace.

Purpose

This command helps you import discovered workflows, adapt them to your workspace standards, validate frontmatter consistency, and integrate with your configuration.

Initial Response

When invoked:

I'll help you import a workflow from an external repository.

Please provide:
1. Repository name (e.g., wshobson/commands)
2. Workflow name (e.g., code-review)

Or, if you've already run /discover-workflows:
- Check the catalog: thoughts/shared/workflows/catalog.md
- Pick from discovered workflows

Process

Step 1: Identify Workflow

Get the repository and workflow name from user or parameters.

Step 2: Parallel Research & Validation

IMPORTANT: Spawn 3 parallel tasks for comprehensive analysis.

Use TodoWrite to track parallel research.

Task 1 - External Research:

Use external-research agent:
"Research {repo}/{workflow}. Explain what this workflow does, how it works, what tools it uses, and provide the complete implementation including frontmatter."

Tools: mcp__deepwiki__ask_question
Return: Full workflow understanding and implementation

Task 2 - Local Pattern Check:

Use codebase-pattern-finder agent:
"Find similar workflows in our workspace (agents/ and commands/ directories). Look for workflows that serve similar purposes or use similar patterns."

Tools: Grep, Glob, Read
Path: /Users/ryan/code-repos/ryan-claude-workspace
Return: Similar local workflows for comparison

Task 3 - Historical Context:

Use thoughts-locator agent:
"Search for any previous research, notes, or attempts related to this type of workflow. Search for keywords: {workflow-name}, {workflow-purpose}."

Tools: Grep, Glob
Path: thoughts/
Return: Any historical context or previous attempts

WAIT for all 3 tasks to complete.

Step 3: Aggregate and Analyze

Combine results from parallel tasks:

• External workflow details (Task 1)
• Similar local patterns (Task 2)
• Historical context (Task 3)

Mark all tasks complete in TodoWrite.

Analyze:

1. Purpose alignment: Does this fit our needs?
2. Duplication check: Do we already have something similar?
3. Adaptation needs: What needs to change?

Step 4: Present Analysis to User

Show comprehensive analysis:

# Import Analysis: {workflow-name}

## What It Does

[Summary from external research]

## External Implementation

- **Repository**: {repo}
- **Tools used**: [list]
- **Frontmatter**:
  ```yaml
  [original frontmatter]
  ```

Comparison with Our Workspace

Similar Local Workflows

[From Task 2 - what we already have]

Differences

• [Key differences from our patterns]

Historical Context

[From Task 3 - any previous attempts or notes]

Required Adaptations

1. Frontmatter: [what needs to change]
2. Configuration: [ticket prefix, Linear IDs, etc.]
3. Tool references: [any tool updates needed]
4. Naming: [follow our conventions]

Recommendation

[Import as-is / Import with modifications / Skip (we have similar)]

Proceed with import? (Y/n)

### Step 5: Adapt to Workspace Standards

If user approves, adapt the workflow:

#### 5a. Standardize Frontmatter

Apply consistent frontmatter based on type:

**For Agents**:
```yaml
---
name: {workflow-name}
description: |
  {Clear description from research}
  {When to invoke}
tools: {validated tool list}
model: inherit
category: {appropriate category}
version: 1.0.0
source: {repo-url}  # Track origin
---

For Commands:

---
description: { One-line summary }
category: { appropriate category }
argument-hint: { if applicable }
tools: { tool list }
model: inherit
version: 1.0.0
source: { repo-url } # Track origin
---

5b. Replace Repository-Specific Values

Check for and replace:

• Ticket prefixes (ENG-XXX → read from .claude/config.json)
• Repository paths (their paths → local paths)
• Team/project IDs (their IDs → prompt or use config)
• User names (their names → generic or config)
• Tool names (check compatibility)

5c. Add Attribution

Add source attribution in frontmatter and as comment:

---
source: https://github.com/{repo}
adapted: { date }
original-author: { if known }
---

<!--
Adapted from: {repo}/{workflow-name}
Original: {URL}
Modifications:
- {change 1}
- {change 2}
-->

Step 6: Validate Frontmatter

Before saving, validate against standard:

• Required fields present?
• Tools list valid?
• Category appropriate?
• Description clear?
• Name follows kebab-case?

If validation fails, show issues and fix.

Step 7: Save Workflow

Determine type and save location:

If Agent:

• Save to: agents/{workflow-name}.md

If Command:

• Save to: commands/{workflow-name}.md

Step 8: Create Import Record

Save import details to thoughts/shared/workflows/imports.md:

## {workflow-name}

- **Imported**: {date}
- **Source**: {repo}/{workflow}
- **Type**: {agent/command}
- **Location**: {file-path}
- **Adaptations**:
  - {adaptation 1}
  - {adaptation 2}
- **Status**: Active

**Why imported**: {reason}

Step 9: Confirmation

Present success summary:

✅ Workflow imported successfully!

**Saved to**: {file-path}

**Adaptations made**:

- Standardized frontmatter
- Updated ticket prefix: ENG → PROJ
- Added source attribution
- Validated tools list

**Next steps**:

1. Review: `{file-path}`
2. Test: Try using the workflow
3. Customize: Adjust for your specific needs
4. Commit: `git add {file-path} && git commit -m "Import {workflow-name} from {repo}"`

Import recorded in: thoughts/shared/workflows/imports.md

Advanced Usage

Import with Custom Adaptations

/import-workflow wshobson/commands code-review --adapt "Use our custom linting rules"

Import Multiple Workflows

/import-workflow wshobson/commands code-review refactor test-gen

Imports all 3 in sequence (with parallel validation for each).

Dry Run Mode

/import-workflow wshobson/commands code-review --dry-run

Shows what would be imported without actually saving files.

Important Notes

• Always validate: Never blindly import without checking compatibility
• Track provenance: Always attribute source
• Respect licenses: Check repo license before importing
• Test imported workflows: Verify they work in your environment
• Keep imports.md updated: Track what you've imported

Integration with Other Commands

• Discover first: /discover-workflows → catalog workflows
• Then import: /import-workflow (this command)
• Validate: /validate-frontmatter ensures consistency
• Create custom: /create-workflow for new workflows

Error Handling

Workflow Not Found

• Suggest running /discover-workflows {repo} first
• Check catalog for available workflows

Incompatible Tools

• List tools that don't exist in your environment
• Suggest alternatives
• Ask if should proceed with modifications

Duplicate Workflow

• Show existing similar workflow
• Ask: Replace / Rename / Skip?

Validation Failures

• Show specific issues
• Offer to auto-fix
• Request manual review if complex

This command bridges external workflows into your workspace with proper adaptation and validation!