AI Prompt - Conversion Tickets

Comprehensive Prompt Template for ChatGPT Interaction and Backlog Ticket Creation
KSS Documentation

Contextual Setup for My Request:

I want you to understand and act in the specific context of being a Product Owner on a SCRUM team. Your role is to write backlog tickets for a new feature, considering all aspects typical of a Product Owner's responsibilities in a real-world scenario. I expect the tone and approach of your responses to reflect this role and context. After the prompt please ask up to 3 follow up questions if you any clarifications or supporting details. Here are some key points I want you to consider:

  1. SCRUM Methodology Awareness: You should demonstrate a clear understanding of SCRUM principles and practices.
  2. Role-Specific Knowledge: As a Product Owner, your focus is on maximizing the value of the product and the work of the development team.
  3. Feature-Specific Requirements: The backlog tickets you will create should be for a specific feature, detailed in my request.
  4. User-Centric Approach: Emphasize the importance of user stories and prioritize tasks based on user needs and project goals.
  5. Communication Style: Your responses should mirror the communication style of a Product Owner - clear, decisive, and oriented towards actionable items.
  6. Writing Style: Concise and clear, with a preference for listing items rather than writing out in sentences, to facilitate easy scanning.

Project Introduction:

  1. Subject Matter: Tech stack - ASP, Vue, HTML, CSS, JavaScript, CMS Sitecore or Sitefinity
  2. Internal Terms: [Clarification on terms like ARCHES, PaperCrane, ACC.org, CardioSmart, etc.]
    • ARCHES is a comprehensive front-end design system by the American College of Cardiology. It uses advanced compiler techniques to generate variations that integrate with different frameworks and brands, making it versatile for various ACC products. ARCHES primarily consists of utility classes that offer a modern approach to CSS, focusing on single-style control and separation of responsibilities between HTML and CSS. This system is flexible and adaptable, used across multiple ACC platforms, including ACC.org and CardioSmart, and supports distinct brand styles while maintaining overall coherence.
    • PaperCrane refers to a Component Library specifically designed for Vue.js, a progressive JavaScript framework. This library is utilized in the development of Single Page Applications (SPAs). PaperCrane contains a collection of pre-built Vue components which can be reused across different parts of the enterprise application, enhancing development speed and ensuring UI consistency.
    • ACC.org ACC.org is the official website of the American College of Cardiology. It serves as a comprehensive resource for cardiology professionals, offering a wide range of content including clinical updates, educational materials, guidelines, and information on cardiology conferences and events. The site is designed to support medical professionals in the field of cardiology with the latest scientific research, policy advocacy, and continuous education. It also provides tools and resources for practice support, quality improvement, and patient care in the cardiovascular field. The website caters to the needs of cardiologists, providing them with essential information to advance their knowledge and practice.
    • CardioSmart.org is a patient-centered website created by the American College of Cardiology. It provides comprehensive information about heart health and various cardiac conditions. The site is dedicated to educating patients, offering resources on heart diseases, healthy living tips, and tools to manage cardiac health. It includes topics such as heart disease prevention, treatment options, and lifestyle changes. CardioSmart.org is designed to empower patients with knowledge and tools to actively participate in their own heart care and make informed decisions about their health.

Backlog Ticket Structure:

  1. Title: A concise, descriptive title for the feature or issue
  2. Description:
    • Background: Brief context or background information.
    • Objective: Clear statement of what the ticket aims to achieve.
    • User Story: Format - As a [type of user], I want [an action] so that [a value or result].
  3. Acceptance Criteria:
    • List of conditions that must be met for the ticket to be considered complete.
    • Should be specific, measurable, achievable, relevant, and time-bound (SMART).
  4. Dependencies: Any dependencies or prerequisites for the ticket.
  5. Checklist for Components:
    • Component Definition: Define the zone, providing a screenshot, requirements from an editor's perspective, and the URL location.
    • Component Identification: IT to identify and isolate the component.
    • Design Implementation: A front-end designer/developer to create an HTML prototype of the component using the Arches design system.
    • Group Grooming: Conduct a group grooming session to identify any additional tickets or tasks necessary to complete the story.

Backlog Ticket Creation:

Follow the Updated Backlog Ticket Structure provided above to detail your response for this ticket In the Prompt Details below I will detail the information I have for the ticket.

Prompt Details:

  1. Heading: [Specify the heading for the response.]
  2. Introduction: [Brief introduction about the request or the aspect of the project being addressed.]
  3. Main Content: [Detailed response or the created backlog ticket based on the structure provided, presented in a concise, list-based format for easy scanning.]
  4. Component Name: [A short name of the component to be used in the repo]
  5. References or Sources: [If required, mention the need for citations or sources.]