A comprehensive set of Claude Code commands for generating well-structured Linear issues following established patterns. Transform ideas, requirements, and bugs into properly formatted Linear issues with consistent structure and documentation.
This system streamlines Linear issue creation by:
- Issue Type Templates: Standardized formats for FRs, User Stories, PRDs, and Bugs
- Quick Issue Generation: Minimal input for rapid idea capture
- Conversion Tools: Transform existing documents into proper Linear format
- Analysis & Improvement: Review and enhance existing issues
- Consistent Structure: Follow established patterns for team consistency
# Generate a quick issue from minimal input
/quick-issue FR: Add rate limiting to API endpoints
# Create detailed Feature Request
/generate-fr
# Generate comprehensive User Story
/generate-us
# Create Product Requirements Document
/generate-prd
# Convert existing content to Linear format
/convert-to-linear
# Analyze and improve existing issues
/analyze-issueclaude-code-linear-commands/
├── commands/ # Claude command definitions
│ ├── quick-issue.md # Quick issue generator
│ ├── generate-fr.md # Feature Request generator
│ ├── generate-us.md # User Story generator
│ ├── generate-prd.md # Product Requirements Document
│ ├── convert-to-linear.md # Convert existing content
│ └── analyze-issue.md # Analyze existing issues
│
└── README.md # This documentation
Each command follows a specific pattern to generate well-structured Linear issues:
User: /quick-issue FR: Add rate limiting to API endpoints
Claude generates a properly formatted Feature Request with basic structure, ready for refinement.
User: /generate-fr
Claude: I need information about the feature...
User: [Provides details]
Claude: [Generates comprehensive issue with all sections]
User: /convert-to-linear
[Pastes email thread or meeting notes]
Claude: [Converts to structured Linear issue format]
User: /analyze-issue
[Pastes existing Linear issue]
Claude: [Provides improvement suggestions and enhanced sections]
Generate a quick Linear issue with minimal input. Perfect for capturing ideas.
Example:
/quick-issue FR: Add rate limiting to API endpoints
/quick-issue Bug: Login fails with special characters
/quick-issue US: User needs to export data as CSV
Create a comprehensive Feature Request with technical requirements and implementation plan.
Output includes:
- Strategic context and business value
- Phased technical requirements
- Implementation details with code examples
- Security and performance considerations
Generate a detailed User Story with acceptance criteria and success metrics.
Output includes:
- User-focused story format
- Clear acceptance criteria
- Technical implementation notes
- Success metrics and KPIs
Create a Product Requirements Document for complex features.
Output includes:
- Executive summary and problem statement
- Detailed feature specifications
- Implementation timeline
- Risk assessment and mitigations
Transform existing content into proper Linear issue format.
Accepts:
- Meeting notes
- Email threads
- Technical specifications
- Bug reports from other systems
Review and improve existing Linear issues.
Provides:
- Structure and content analysis
- Specific improvement suggestions
- Enhanced sections following best practices
Every issue type follows established patterns:
- Consistent structure and sections
- Appropriate metadata and labels
- Clear acceptance criteria
- Feature Requests (FR): Technical requirements with implementation details
- User Stories (US): User-focused functionality with success metrics
- Product Requirements (PRD): Comprehensive product specifications
- Quick Issues: Rapid capture for later refinement
- Automatic issue type detection
- Smart section population
- Missing information identification
- Follows established Linear patterns
- Maintains organizational standards
- Reduces review cycles
- Be Specific: Clear descriptions lead to better structured issues
- Choose Right Command: Use
/quick-issuefor rapid capture, detailed commands for thorough specs - Provide Context: Include business value and technical constraints
- Review Output: Check generated issues before adding to Linear
- One Feature Per Issue: Keep scope focused and manageable
- Include Examples: Add code snippets and implementation details
- Define Success: Clear acceptance criteria and success metrics
- Link Dependencies: Reference related issues and blockers
These commands require the Linear MCP server to be configured in your Claude Code setup. The Linear MCP server enables Claude to directly interact with your Linear workspace.
Setup the Linear MCP server: Follow the official Linear documentation at linear.app/changelog/2025-05-01-mcp to configure the Linear integration.
- Clone this repository:
git clone https://github.com/svnlto/claude-code-linear-commands.git- Copy the commands to your project:
cp -r commands ~/.claude/commands/
# OR for project-specific
cp -r commands /your/project/.claude/commands/- Start using the commands in Claude Code:
/quick-issue Your first issue description/quick-issue FR: Add caching to product API endpoints
/quick-issue Bug: Users can't upload files larger than 5MB
/quick-issue US: Admin needs bulk user management tools
/generate-fr
# Provide feature details
# Get comprehensive FR with technical specs, implementation phases, and acceptance criteria
/convert-to-linear
[Paste meeting notes about new dashboard feature]
# Get structured Linear issue with proper sections and requirements
/generate-us
# Define user type, need, and value
# Get detailed user story with acceptance criteria and success metrics
- Fork the repository
- Create your feature branch
- Add new commands or improve existing ones
- Submit a pull request
- Add templates for additional issue types
- Create issue validation commands
- Build integrations with Linear API
- Add team-specific customizations
MIT License - Feel free to use and modify for your projects.