Name: project-to-linear
Author: xats-org

Prompt file imported from xats-org/core (.claude/commands/project/project-to-linear.md). Fill in {{arguments}} before use. Copyright stays with the author.

Project to Linear

Sync project structure to Linear workspace

Instructions

Analyze Project Requirements
- Review the provided task description or project requirements: {{arguments}}
- Examine the current codebase structure and existing functionality
- Identify all major components and features needed
- Determine technical dependencies and constraints
- Assess the scope and complexity of the work
Understand User's Intent
- Ask clarifying questions about:
  - Project goals and objectives
  - Priority levels for different features
  - Timeline expectations
  - Technical preferences or constraints
  - Team structure (if relevant)
  - Definition of done for tasks
- Confirm understanding of the requirements before proceeding
Check Linear Configuration
- Verify if Linear MCP server is available and configured
- If not available, ask the user to:
  - Install the Linear MCP server if not already installed
  - Configure the Linear API key in their MCP settings
  - Provide the default team ID or workspace information
- Test the connection by listing available projects
Project Setup in Linear
- Ask the user if they want to:
  - Use an existing Linear project (request project ID)
  - Create a new project (ask for project name and description)
- For new projects, determine:
  - Project type (Feature, Bug, Task, etc.)
  - Project status (Planning, In Progress, etc.)
  - Project lead or owner
  - Any custom fields or labels to use
Generate Comprehensive Task List
- Break down the project into logical phases:
  - Planning and Design
  - Core Implementation
  - Testing and Quality Assurance
  - Documentation
  - Deployment and Release
- For each phase, create detailed tasks including:
  - Clear, actionable task titles
  - Detailed descriptions with acceptance criteria
  - Technical specifications where relevant
  - Estimated effort (if requested)
  - Dependencies between tasks
  - Priority levels (Critical, High, Medium, Low)
Create Task Hierarchy
- Organize tasks into a proper hierarchy:
  - Epic/Project level (if creating new project)
  - Parent tasks for major features or components
  - Subtasks for implementation details
  - Related tasks for cross-cutting concerns
- Ensure logical grouping and dependencies
Add Task Details
- For each task, include:
  - Title: Clear, concise description
  - Description: Detailed requirements and context
  - Acceptance Criteria: Definition of done
  - Labels: Appropriate tags (frontend, backend, testing, etc.)
  - Priority: Based on user input and analysis
  - Estimates: If sizing is requested
  - Assignee: If team members are specified
  - Due Dates: Based on timeline requirements
Create Tasks in Linear
- Use the Linear MCP server to:
  - Create the project (if new)
  - Create all parent tasks first
  - Create subtasks under appropriate parents
  - Set up dependencies between tasks
  - Apply labels and priorities
  - Add any custom fields
- Provide feedback on each task created
Review and Refinement
- Present a summary of all created tasks
- Show the task hierarchy and relationships
- Ask if any adjustments are needed:
  - Task grouping or organization
  - Priority changes
  - Additional tasks or details
  - Timeline adjustments
- Make any requested modifications
Provide Project Overview
- Generate a summary including:
  - Total number of tasks created
  - Task breakdown by type/phase
  - Critical path items
  - Estimated timeline (if applicable)
  - Link to the Linear project
  - Next recommended actions

Example Task Structure

Project: User Dashboard Feature
├── Planning & Design
│   ├── Create UI/UX mockups
│   ├── Define API requirements
│   └── Technical design document
├── Backend Development
│   ├── User API endpoints
│   │   ├── GET /api/users endpoint
│   │   ├── PUT /api/users/:id endpoint
│   │   └── User data validation
│   └── Dashboard data aggregation
├── Frontend Development
│   ├── Dashboard layout component
│   ├── User profile widget
│   ├── Activity feed component
│   └── Data visualization charts
├── Testing
│   ├── Unit tests for API
│   ├── Frontend component tests
│   ├── E2E dashboard tests
│   └── Performance testing
└── Documentation & Deployment
    ├── API documentation
    ├── User guide
    └── Production deployment

Integration Notes

This command requires the Linear MCP server to be configured
If MCP is not available, provide the task list in a format that can be manually imported
Support batch operations to avoid rate limiting
Handle errors gracefully and provide clear feedback
Maintain task relationships and dependencies properly

Install project-to-linear 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.

# Project to Linear Sync project structure to Linear workspace ## Instructions 1. **Analyze Project Requirements** - Review the provided task description or project requirements: **{{arguments}}** - Examine the current codebase structure and existing functionality - Identify all major components and features needed - Determine technical dependencies and constraints - Assess the scope and complexity of the work 2. **Understand User's Intent** - Ask clarifying questions about: - Project goals and objectives - Priority levels for different features - Timeline expectations - Technical preferences or constraints - Team structure (if relevant) - Definition of done for tasks - Confirm understanding of the requirements before proceeding 3. **Check Linear Configuration** - Verify if Linear MCP server is available and configured - If not available, ask the user to: - Install the Linear MCP server if not already installed - Configure the Linear API key in their MCP settings - Provide the default team ID or workspace information - Test the connection by listing available projects 4. **Project Setup in Linear** - Ask the user if they want to: - Use an existing Linear project (request project ID) - Create a new project (ask for project name and description) - For new projects, determine: - Project type (Feature, Bug, Task, etc.) - Project status (Planning, In Progress, etc.) - Project lead or owner - Any custom fields or labels to use 5. **Generate Comprehensive Task List** - Break down the project into logical phases: - Planning and Design - Core Implementation - Testing and Quality Assurance - Documentation - Deployment and Release - For each phase, create detailed tasks including: - Clear, actionable task titles - Detailed descriptions with acceptance criteria - Technical specifications where relevant - Estimated effort (if requested) - Dependencies between tasks - Priority levels (Critical, High, Medium, Low) 6. **Create Task Hierarchy** - Organize tasks into a proper hierarchy: - Epic/Project level (if creating new project) - Parent tasks for major features or components - Subtasks for implementation details - Related tasks for cross-cutting concerns - Ensure logical grouping and dependencies 7. **Add Task Details** - For each task, include: - **Title**: Clear, concise description - **Description**: Detailed requirements and context - **Acceptance Criteria**: Definition of done - **Labels**: Appropriate tags (frontend, backend, testing, etc.) - **Priority**: Based on user input and analysis - **Estimates**: If sizing is requested - **Assignee**: If team members are specified - **Due Dates**: Based on timeline requirements 8. **Create Tasks in Linear** - Use the Linear MCP server to: - Create the project (if new) - Create all parent tasks first - Create subtasks under appropriate parents - Set up dependencies between tasks - Apply labels and priorities - Add any custom fields - Provide feedback on each task created 9. **Review and Refinement** - Present a summary of all created tasks - Show the task hierarchy and relationships - Ask if any adjustments are needed: - Task grouping or organization - Priority changes - Additional tasks or details - Timeline adjustments - Make any requested modifications 10. **Provide Project Overview** - Generate a summary including: - Total number of tasks created - Task breakdown by type/phase - Critical path items - Estimated timeline (if applicable) - Link to the Linear project - Next recommended actions ## Example Task Structure ``` Project: User Dashboard Feature ├── Planning & Design │ ├── Create UI/UX mockups │ ├── Define API requirements │ └── Technical design document ├── Backend Development │ ├── User API endpoints │ │ ├── GET /api/users endpoint │ │ ├── PUT /api/users/:id endpoint │ │ └── User data validation │ └── Dashboard data aggregation ├── Frontend Development │ ├── Dashboard layout component │ ├── User profile widget │ ├── Activity feed component │ └── Data visualization charts ├── Testing │ ├── Unit tests for API │ ├── Frontend component tests │ ├── E2E dashboard tests │ └── Performance testing └── Documentation & Deployment ├── API documentation ├── User guide └── Production deployment ``` ## Integration Notes - This command requires the Linear MCP server to be configured - If MCP is not available, provide the task list in a format that can be manually imported - Support batch operations to avoid rate limiting - Handle errors gracefully and provide clear feedback - Maintain task relationships and dependencies properly

{ "prompt": "# Project to Linear\n\nSync project structure to Linear workspace\n\n## Instructions\n\n1. **Analyze Project Requirements**\n - Review the provided task description or project requirements: **{{arguments}}**\n - Examine the current codebase structure and existing functionality\n - Identify all major components and features needed\n - Determine technical dependencies and constraints\n - Assess the scope and complexity of the work\n\n2. **Understand User's Intent**\n - Ask clarifying questions about:\n - Project goals and objectives\n - Priority levels for different features\n - Timeline expectations\n - Technical preferences or constraints\n - Team structure (if relevant)\n - Definition of done for tasks\n - Confirm understanding of the requirements before proceeding\n\n3. **Check Linear Configuration**\n - Verify if Linear MCP server is available and configured\n - If not available, ask the user to:\n - Install the Linear MCP server if not already installed\n - Configure the Linear API key in their MCP settings\n - Provide the default team ID or workspace information\n - Test the connection by listing available projects\n\n4. **Project Setup in Linear**\n - Ask the user if they want to:\n - Use an existing Linear project (request project ID)\n - Create a new project (ask for project name and description)\n - For new projects, determine:\n - Project type (Feature, Bug, Task, etc.)\n - Project status (Planning, In Progress, etc.)\n - Project lead or owner\n - Any custom fields or labels to use\n\n5. **Generate Comprehensive Task List**\n - Break down the project into logical phases:\n - Planning and Design\n - Core Implementation\n - Testing and Quality Assurance\n - Documentation\n - Deployment and Release\n - For each phase, create detailed tasks including:\n - Clear, actionable task titles\n - Detailed descriptions with acceptance criteria\n - Technical specifications where relevant\n - Estimated effort (if requested)\n - Dependencies between tasks\n - Priority levels (Critical, High, Medium, Low)\n\n6. **Create Task Hierarchy**\n - Organize tasks into a proper hierarchy:\n - Epic/Project level (if creating new project)\n - Parent tasks for major features or components\n - Subtasks for implementation details\n - Related tasks for cross-cutting concerns\n - Ensure logical grouping and dependencies\n\n7. **Add Task Details**\n - For each task, include:\n - **Title**: Clear, concise description\n - **Description**: Detailed requirements and context\n - **Acceptance Criteria**: Definition of done\n - **Labels**: Appropriate tags (frontend, backend, testing, etc.)\n - **Priority**: Based on user input and analysis\n - **Estimates**: If sizing is requested\n - **Assignee**: If team members are specified\n - **Due Dates**: Based on timeline requirements\n\n8. **Create Tasks in Linear**\n - Use the Linear MCP server to:\n - Create the project (if new)\n - Create all parent tasks first\n - Create subtasks under appropriate parents\n - Set up dependencies between tasks\n - Apply labels and priorities\n - Add any custom fields\n - Provide feedback on each task created\n\n9. **Review and Refinement**\n - Present a summary of all created tasks\n - Show the task hierarchy and relationships\n - Ask if any adjustments are needed:\n - Task grouping or organization\n - Priority changes\n - Additional tasks or details\n - Timeline adjustments\n - Make any requested modifications\n\n10. **Provide Project Overview**\n - Generate a summary including:\n - Total number of tasks created\n - Task breakdown by type/phase\n - Critical path items\n - Estimated timeline (if applicable)\n - Link to the Linear project\n - Next recommended actions\n\n## Example Task Structure\n\n```\nProject: User Dashboard Feature\n├── Planning & Design\n│ ├── Create UI/UX mockups\n│ ├── Define API requirements\n│ └── Technical design document\n├── Backend Development\n│ ├── User API endpoints\n│ │ ├── GET /api/users endpoint\n│ │ ├── PUT /api/users/:id endpoint\n│ │ └── User data validation\n│ └── Dashboard data aggregation\n├── Frontend Development\n│ ├── Dashboard layout component\n│ ├── User profile widget\n│ ├── Activity feed component\n│ └── Data visualization charts\n├── Testing\n│ ├── Unit tests for API\n│ ├── Frontend component tests\n│ ├── E2E dashboard tests\n│ └── Performance testing\n└── Documentation & Deployment\n ├── API documentation\n ├── User guide\n └── Production deployment\n```\n\n## Integration Notes\n\n- This command requires the Linear MCP server to be configured\n- If MCP is not available, provide the task list in a format that can be manually imported\n- Support batch operations to avoid rate limiting\n- Handle errors gracefully and provide clear feedback\n- Maintain task relationships and dependencies properly", "variables": [ "arguments" ], "notes": "Sync project structure to Linear workspace", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/xats-org/core", "path": ".claude/commands/project/project-to-linear.md", "ref": "f931fc400a3cb22f138dbbe94c22d7a0a4a1e710", "url": "https://github.com/xats-org/core/blob/f931fc400a3cb22f138dbbe94c22d7a0a4a1e710/.claude/commands/project/project-to-linear.md", "key": "xats-org/core/.claude/commands/project/project-to-linear.md" } } }

project-to-linear

About