skills.rest
JaimeJunr
JaimeJunrCOMMUNITY
Explore all skills by this author →
GitHub

engineering-ticket

Generates plain-text, JIRA-ready engineering tickets from BRDs and project specifications.

2|Updated Apr 11, 2026
Search Tags:#specification#requirements#backlog#handoff#jira#ticket
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill engineering-ticket
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-ticket
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/engineering-ticket
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill engineering-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts scattered product notes and BRDs into consistent, Jira-ready engineering tickets, eliminating markdown inconsistencies and manual formatting errors.

Core Features & Use Cases

  • Plain-text tickets only: produce tickets as clean, tracker-friendly plain text with clearly defined sections.
  • Template-driven: leverage the references/ticket-template.txt to standardize structure, sections, and acceptance criteria.
  • Handoff-ready format: ensures all critical details (objective, contextual information, functional and non-functional requirements, and acceptance criteria) are included for engineering teams.

Quick Start

Generate a Jira-ready engineering ticket from the BRD summary for the new login flow.

Frequently Asked Questions about engineering-ticket

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

FAQPage Schema
How do I convert a BRD into Jira-ready engineering tickets?▼

To convert a BRD into Jira-ready engineering tickets, provide the product specification to the Skill. It outputs structured plain text covering scope, technical details, and acceptance criteria for tracker handoff.

What is the best way to format product specifications for backlog handoff?▼

The best way to format product specifications for backlog handoff is using a template-driven plain text structure. This ensures all critical details like non-functional notes and scope are consistently included for engineering teams.

Can I use a custom template for generating engineering tickets from requirements?▼

Yes, you can use a custom template for generating engineering tickets. The Skill references a ticket-template to standardize the structure, sections, and acceptance criteria for your specific requirements and handoff scenarios.

Does the generated ticket format support markdown or plain text only?▼

The generated ticket format supports plain text only. It produces clean, tracker-friendly plain text with clearly defined sections to eliminate markdown inconsistencies and manual formatting errors during Jira handoff.

What sections are included when creating engineering tickets from product notes?▼

Creating engineering tickets from product notes includes sections for objective, contextual information, functional and non-functional requirements, technical details, and acceptance criteria to ensure comprehensive handoff-ready formatting.

Related Skills

Explore More Software Engineering Skills→
SoborboSoborbo
4

competitor-analysis

Analyze up to five competitor websites to extract marketing data into YAML.

Community
Basic
pisithrpspisithrps

create-tickets

Create engineering tickets from PRDs, feature specs, or task lists.

Community
Advanced
adriangmrraaadriangmrraa

Spec Architect

Generate and validate SDD v2.0 specification files (.spec.md) for feature planning, refinement, and audit workflows.

Community
Advanced
probationer070probationer070

setup-matt-pocock-skills

Configure engineering skills with issue tracker, triage labels, and domain documentation.

Community
Intermediate