writing-linear-issues

Draft Linear issues through iterative dialogue and structured questioning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blaknite/agent-skills --skill writing-linear-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-linear-issues
Source: https://github.com/blaknite/agent-skills/tree/main/writing-linear-issues
Command: npx skills add https://github.com/blaknite/agent-skills --skill writing-linear-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users collaboratively draft clear, focused, and actionable issues in Linear by acting as a thinking partner and refining problem statements.

Core Features & Use Cases

  • Iterative Refinement: Guides users through clarifying questions to define the problem, customer, intent, and requirements.
  • Structured Drafting: Helps structure issues as bugs, features, tech debt, or tasks based on context.
  • Collaboration: Acts as a rubber duck to help users articulate their thoughts precisely.
  • Use Case: A product manager has a vague idea for a new feature. They use this skill to flesh out the customer need, desired outcome, and acceptance criteria before creating the Linear issue.

Quick Start

Use the writing-linear-issues skill to help me draft a new issue about improving the onboarding flow.

Frequently Asked Questions about writing-linear-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write better Linear issues for feature requests and bug reports?

This Skill helps you write better Linear issues by acting as a thinking partner, using iterative dialogue to refine problem statements, customer impact, and requirements for your bugs or features.

What is the best way to structure Linear issues for tech debt and tasks?

The best way to structure Linear issues is through collaborative drafting that categorizes items as bugs, features, tech debt, or tasks, using structured questioning to define acceptance criteria and specific requirements.

How do I define clear acceptance criteria for a Linear issue?

You define clear acceptance criteria for a Linear issue by collaboratively drafting requirements through iterative questioning, ensuring desired intent and expected behavior are precisely articulated before creation.

Can I use this to flesh out a vague product idea before creating a Linear task?

Yes, you can use this Skill to flesh out vague product ideas by acting as a rubber duck, helping you articulate customer needs, desired outcomes, and requirements before creating the final Linear issue.

Does drafting Linear issues with this Skill automatically create the task in my project?

Drafting Linear issues with this Skill does not automatically create tasks; it focuses on collaborative refinement and structuring requirements, utilizing a separate creation step for the final Linear issue.