From linear
Linear's proven methodology for software development and project organization. Use when helping users plan work, create issues, structure projects, set direction, prioritize tasks, or organize development workflows. Applies Linear's principles of momentum, simplicity, and focus—not API integration. For solo developers and teams organizing software projects.
npx claudepluginhub horuz-ai/claude-plugins --plugin linearThis skill uses the workspace's default tool permissions.
This skill embodies Linear's philosophy and best practices for building software with focus, momentum, and quality. Use it to help organize work according to proven principles that distinguish world-class product teams.
Generates structured PRDs and plans for new projects with repo scaffolding, features, or retrospectives using researched Q&A engine with parallel agents and issue creation.
Guides 4-step Shape Up process to shape work into pitches for betting. Supports established (fixed time, variable scope) and new product modes for cycle planning and PM coaching.
Guides software project planning with discovery questions, requirements gathering, user stories, MoSCoW prioritization, T-shirt estimation, scope management, risk assessment, and templates for briefs and epics. Use for new projects or features.
Share bugs, ideas, or general feedback.
This skill embodies Linear's philosophy and best practices for building software with focus, momentum, and quality. Use it to help organize work according to proven principles that distinguish world-class product teams.
Speed through simplicity: Tools should help creators stay productive, not create bureaucracy. Keep individuals moving fast rather than generating perfect reports.
Momentum over perfection: Take swift action daily. Ship constantly. Multiple small launches beat one big launch.
Clarity of direction: Connect every task to larger goals. Everyone should understand what matters and why.
Manageable scope: Scope projects down aggressively. Break large work into completable stages. Small, concrete tasks feel great to finish.
Issues communicate tasks clearly and concisely. NO user stories—they're cargo cult that wastes time.
Title: Plain language describing the task
Good: "Add password reset flow"
Bad: "As a user, I want to reset my password so that..."
Description (when needed):
✅ Good Issues:
❌ Bad Issues (User Stories):
Issues should be completable in 1-3 days max. If longer:
Exploration issues: "Explore design options for dashboard" or "Research authentication libraries" are valid placeholder issues that get broken down later.
Bug reports from others: Frame as problem description, let assignee determine solution and rewrite as task.
Feature requests: Include direct user quotes and link to original conversation. Focus on the pain point, not the requested solution.
Projects organize related issues toward a specific deliverable or feature.
Name: Clear, specific feature or deliverable
Good: "User Authentication System"
Bad: "Authentication Improvements"
Brief spec (1-2 paragraphs):
Timeline: Target completion date (use for planning, not pressure)
Issues: 5-15 specific tasks that deliver the project
Project: "User Authentication"
Each issue = 1-3 days of work = completable this week
Direction keeps work aligned to meaningful goals.
Initiatives (months) → Projects (weeks) → Issues (days)
Major streams of work over 2-6 months:
Purpose: Everyone understands what's most important and why
Measurable targets that push you forward:
Map initiatives and projects on a timeline:
Not all work is equal. Distinguish enablers from blockers, now from later.
Blockers: Gaps preventing someone from using your product Enablers: Features opening new opportunities or markets
Ask: "Does this prevent usage or is it nice-to-have?"
Critical questions:
Prioritize: Things that move the needle this week/month
In early stages, many features are "eventually needed."
Build the minimum to unblock progress now. Add polish later. Focus on what enables the next growth milestone.
Cycles create healthy routine and focus.
Momentum comes from consistent, visible progress.
Keep backlogs manageable—you don't need every idea forever.
Design requires structure but needs freedom to explore.
Build WITH users, not just FOR users.
For detailed examples and patterns:
references/issue_examples.md - Extensive examples of good vs bad issuesreferences/project_templates.md - Project spec templates and breakdownsreferences/solo_workflows.md - Specific workflows for solo developersApply Linear Method principles when:
This skill provides conceptual guidance, not API integration. When users ask to "create an issue about X", help them craft it according to these principles—don't write API code.