write-ticket

Name: write-ticket
Availability: InStock
Author: fieldsphere

Draft implementation-ready tickets with structured sections from product requests or incidents.

37|20|Updated Mar 2, 2026

Search Tags:#workflow #planning #requirements #engineering #product-management #acceptance-criteria #ticketing

Ready to run

npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill write-ticket

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-ticket
Source: https://github.com/fieldsphere/cursor-team-marketplace-template/tree/main/plugins/product-management/skills/write-ticket
Command: npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill write-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts clear, implementation-ready tickets from product requests, incidents, or discovery notes, reducing back-and-forth and rework.

Core Features & Use Cases

Template-driven ticket creation that enforces a consistent structure.
Generates Title, Problem, Scope, Requirements, Acceptance Criteria, Technical Notes, and QA Notes from inputs.
Use Case: Convert a user-reported issue into a scoped, engineer-ready ticket suitable for sprint planning.

Quick Start

Draft an implementation-ready ticket based on the provided notes to guide engineers from problem to measurable outcome.

Frequently Asked Questions about write-ticket

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

FAQPage Schema

How do I write implementation-ready tickets from product discovery notes?▼

Drafting implementation-ready tickets from discovery notes requires structuring inputs into clear scope, acceptance criteria, and technical context to reduce engineering rework. This ensures engineers get measurable outcomes from product requests.

What is the best way to structure bug reports for sprint planning?▼

Structuring bug reports for sprint planning involves generating a consistent template with Title, Problem, Scope, Requirements, Acceptance Criteria, Technical Notes, and QA Notes. This converts user-reported incidents into scoped, engineer-ready tickets.

How do I convert feature requests into tickets with clear acceptance criteria?▼

Converting feature requests into tickets with clear acceptance criteria applies template-driven creation to extract technical context and requirements. This guides engineers from problem definition directly to measurable outcomes.

What should be included in engineering tickets to avoid back-and-forth communication?▼

Engineering tickets should include Scope, Requirements, Acceptance Criteria, Technical Notes, and QA Notes to avoid back-and-forth communication. Structuring these elements ensures implementation-ready outputs suitable for sprint planning.

Does template-driven ticket creation work for research findings and incident reports?▼

Template-driven ticket creation works for research findings and incident reports by applying a consistent structure to diverse inputs. It transforms raw discovery notes into scoped, actionable tickets with technical context.

Why do my engineering tickets lack clear scope and technical context?▼

Engineering tickets lack clear scope and technical context when inputs like product requests or discovery notes are not structured into standardized sections. Applying a template ensures all necessary technical and QA notes are captured.