skills.rest
ClipboardHealth
ClipboardHealthOFFICIAL
Explore all skills by this author →
Website𝕏@ClipboardEngGitHub

write-feature-ticket

Convert informal conversation snippets into detailed Linear feature tickets.

66|9|Updated Aug 5, 2024
Search Tags:#workflow#feature#ticket#product#ticketing#request
One-click install
npx skills add https://github.com/ClipboardHealth/core-utils --skill write-feature-ticket
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-feature-ticket
Source: https://github.com/ClipboardHealth/core-utils/tree/main/plugins/core/skills/write-feature-ticket
Command: npx skills add https://github.com/ClipboardHealth/core-utils --skill write-feature-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams and developers create clear, well-structured feature request tickets from informal discussions, saving time and reducing miscommunication.

Core Features & Use Cases

  • Automated Ticket Drafting: Converts conversation context into detailed Linear feature tickets.
  • Guided Process: Follows a step-by-step interview approach to gather necessary details.
  • Use Case: A product manager discusses a new feature idea; this Skill generates a comprehensive ticket ready for review and submission.

Quick Start

Provide conversation context, and ask this Skill to generate a Linear feature ticket draft based on the discussion.

Frequently Asked Questions about write-feature-ticket

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

FAQPage Schema
How do I create a feature ticket from an informal product discussion?▼

Creating a feature ticket from a product discussion involves extracting context and using natural language processing to structure informal conversation snippets into detailed, actionable Linear tickets. This reduces miscommunication and saves time for team review.

What is the best way to draft Linear tickets for development planning?▼

Drafting Linear tickets for development planning is best handled by converting informal product feature requests through a guided, step-by-step interview process. This approach gathers necessary details to produce clear, well-structured tickets suitable for cross-team collaboration.

Does the ticket generation process require any specific setup or dependencies?▼

The ticket generation process requires no specific setup or dependencies, operating independently to convert provided conversation context into structured tickets. You simply provide the informal discussion text to generate a comprehensive ticket draft.

Can I turn Slack conversation snippets into structured product requests?▼

Turning conversation snippets into structured product requests is supported by applying context extraction and structured guidelines to the informal text. This converts raw discussions into comprehensive feature tickets ready for team review and submission.

What are the limitations of automated ticket drafting from conversations?▼

Automated ticket drafting from conversations relies entirely on the provided conversation context, meaning incomplete or ambiguous informal discussions may yield tickets requiring manual refinement before team review. The process outputs drafts suitable for tracking but necessitates human validation.

Related Skills

Explore More Product & Management Skills→
rickyanandarickyananda
1

daily-sales-report

Format raw daily sales data into a submission-ready report.

Community
Intermediate
fixpoint-labsfixpoint-labs
2

fsd:quick-fix

Detect, log, fix, and review issues via Linear API.

Official
Advanced
CommunityToolkitCommunityToolkit
619

agent-collaboration

Standardize worktree paths, decision recording, and cross-agent communication for team agents.

Official
Intermediate
masta-g3masta-g3
1

ticket-init

Parse natural language requests and append structured tickets to features.yaml.

Community
Intermediate