User Story Generator: Webinar Guide
The User Story Generator: Webinar Guide prompt creates detailed, INVEST-compliant user stories, acceptance criteria, and technical tasks for a webinar guide feature, tailored for expert Agile Product Owners and Business Analysts.
What is the User Story Generator: Webinar Guide prompt?
Copy the prompt below into ChatGPT, Gemini, Claude or any capable LLM, replace the bracketed variables with your own values, and run it.
ROLE: You are an expert Agile Product Owner and Business Analyst with a specialization in EdTech and digital marketing platforms. Your expertise lies in translating complex business goals into actionable, developer-ready user stories that follow the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, and Testable). GOAL: Your objective is to generate a comprehensive set of User Stories, Acceptance Criteria, and Technical Tasks for a new "Webinar Guide" feature within an existing platform. You must ensure that the output provides enough detail for both designers and developers to begin work immediately. CONTEXT: The user story generation should be based on the following project parameters: - TARGET AUDIENCE: [TARGET AUDIENCE] - CORE FUNCTIONALITY: [CORE FUNCTIONALITY] - PLATFORM ENVIRONMENT: [PLATFORM ENVIRONMENT] - BUSINESS GOAL: [BUSINESS GOAL] - CONSTRAINTS: [CONSTRAINTS] INSTRUCTIONS: 1. Review the CORE FUNCTIONALITY and BUSINESS GOAL to identify the primary user personas involved (e.g., Host, Attendee, Admin). 2. Generate a series of User Stories using the standard format: "As a [Persona], I want to [Action], so that [Value/Benefit]." 3. For each User Story, provide a detailed set of Acceptance Criteria (AC) written in a Given/When/Then format or a bulleted checklist. 4. Detail any specific UI/UX requirements relevant to the [TARGET AUDIENCE] to ensure the guide is intuitive. 5. Identify potential edge cases or error states (e.g., connection drops, invalid inputs) based on the [CONSTRAINTS] provided. 6. List high-level Technical Tasks or considerations for the engineering team, such as API integrations or database schema changes needed for the [PLATFORM ENVIRONMENT]. OUTPUT FORMAT: - USER STORY TITLE: A short, descriptive name for the story. - USER STORY: The "As a... I want... So that..." statement. - ACCEPTANCE CRITERIA: A numbered list of conditions that must be met for the story to be marked as complete. - TECHNICAL NOTES: A brief section on implementation details or constraints. - UI/UX REQUIREMENTS: Specific layout or interaction expectations. QUALITY BAR: Every story must be granular enough to be completed within a single sprint. Avoid vague language like "the system should be fast" or "user-friendly"; instead, use specific metrics or behavioral descriptions. Ensure all stories align directly with the [BUSINESS GOAL].
What variables does the User Story Generator: Webinar Guide prompt use?
| Variable | What to put | Example |
|---|---|---|
| [TARGET AUDIENCE] | The primary user group for the webinar guide feature. | e.g., K-12 Educators and School Administrators |
| [CORE FUNCTIONALITY] | The central actions and capabilities of the webinar guide. | e.g., browse upcoming webinars, register for events, view past recordings, access accompanying resources |
| [PLATFORM ENVIRONMENT] | The specific technical ecosystem or platform where the feature will be implemented. | e.g., existing EdTech LMS built on React, Node.js, and MongoDB with Stripe integration |
| [BUSINESS GOAL] | The overarching business objective this feature aims to achieve. | e.g., Increase user engagement by 15% and drive lead generation for premium courses by 10%. |
| [CONSTRAINTS] | Any limitations or restrictions for the project (e.g., budget, time, technical limitations). | e.g., Must integrate with existing authentication system; strict 4-week development timeline; mobile-first design is required. |
How do I use the User Story Generator: Webinar Guide prompt?
- 1Step 1: Clearly define the [TARGET AUDIENCE], [CORE FUNCTIONALITY], [PLATFORM ENVIRONMENT], [BUSINESS GOAL], and [CONSTRAINTS] as specifically as possible.
- 2Step 2: Copy the entire prompt body into your chosen AI model.
- 3Step 3: Replace each bracketed placeholder variable (e.g., [TARGET AUDIENCE]) with your specific project details.
- 4Step 4: Run the prompt and review the generated user stories, acceptance criteria, technical notes, and UI/UX requirements for completeness and accuracy. Make any necessary human adjustments.
When should you use the User Story Generator: Webinar Guide prompt?
Kickstarting Feature Development
Use this prompt to quickly generate a complete set of requirements for a new 'Webinar Guide' feature, enabling designers and developers to start work immediately.
Refining Existing Requirements
Apply this prompt to an existing feature concept to convert high-level ideas into detailed, INVEST-compliant user stories with acceptance criteria and technical considerations.
Training New Product Owners/BAs
This prompt serves as an excellent template and example for new Product Owners or Business Analysts to learn how to structure and detail user stories effectively.
Ensuring Agile Compliance
Leverage this prompt to guarantee that all generated requirements adhere to the INVEST criteria, promoting better sprint planning, estimation, and development.
Facilitating Cross-Functional Communication
The detailed output bridges the gap between business objectives, design requirements, and technical implementations, fostering clear communication across teams.
What does the User Story Generator: Webinar Guide prompt output look like?
USER STORY TITLE: View Upcoming Webinars USER STORY: As an K-12 Educator, I want to view a list of all upcoming webinars, so that I can easily discover relevant professional development opportunities. ACCEPTANCE CRITERIA: 1. Given I am on the Webinar Guide page, When I navigate to the 'Upcoming' tab, Then I see a list of webinars ordered by date. 2. Each webinar in the list displays its title, date, time, and a brief description. 3. Clicking on a webinar title navigates me to its dedicated detail page. 4. Webinars for which registration is closed are clearly indicated and grayed out. TECHNICAL NOTES: Requires an API endpoint to retrieve upcoming webinar data. Ensure performance optimization for retrieving a large number of events. Consider pagination for lists exceeding 20 items. UI/UX REQUIREMENTS: The upcoming webinars list should feature clear, large date stamps. Each webinar card should have a 'Register' button or a 'View Details' button. Implement a visually distinct 'Virtual' or 'In-Person' tag. Ensure accessibility standards (WCAG 2.1 AA) are met, particularly for color contrast and keyboard navigation.
Which AI model works best with the User Story Generator: Webinar Guide prompt?
Excellent for understanding nuanced instructions, detailed persona definitions, and generating structured, high-quality, and creative user stories with comprehensive acceptance criteria and technical considerations.
Strong at following complex multi-step instructions and producing detailed, well-structured outputs, making it ideal for the specific format and criteria required by this prompt.
Good balance of instruction following and content generation, capable of producing coherent and logically structured user stories that adhere to the INVEST principles and specific output format.
What are the pros and cons of the User Story Generator: Webinar Guide prompt?
Pros
- Generates INVEST-compliant user stories
- Includes detailed acceptance criteria (Given/When/Then)
- Provides technical tasks and UI/UX requirements
- Ensures alignment with business goals and constraints
- Facilitates immediate handover to design and development
- Specializes in EdTech and digital marketing contexts
Cons
- Requires specific and detailed input for best results
- May require minor human refinement for highly complex edge cases
- Output quality depends heavily on the clarity of provided context variables
How can you get better results from the User Story Generator: Webinar Guide prompt?
- Provide extremely detailed inputs for [CORE FUNCTIONALITY] and [BUSINESS GOAL] to get the most relevant stories.
- Be explicit about the [PLATFORM ENVIRONMENT] details (e.g., specific tech stack, existing integrations).
- Before running, brainstorm potential user personas beyond obvious ones (e.g., Analytics Viewer, Content Uploader).
- Iterate on the [CONSTRAINTS] input, considering technical, budget, and timeline limitations.
- If the initial output is too broad, refine the [CORE FUNCTIONALITY] to be more granular for specific user flows.
Frequently asked questions about the User Story Generator: Webinar Guide prompt
What is the User Story Generator: Webinar Guide prompt?
This prompt is designed to help Product Owners and Business Analysts create detailed, actionable user stories, acceptance criteria, and technical tasks for a new webinar guide feature, adhering to Agile's INVEST principles.
What does 'INVEST criteria' mean in this context?
'INVEST' is an acronym for Independent, Negotiable, Valuable, Estimable, Small, and Testable. These are attributes of high-quality user stories that facilitate efficient Agile development and planning.
Which AI model works best with this prompt?
GPT-4o, Gemini 2.5 Pro, and Claude Sonnet are recommended due to their strong instruction-following capabilities and ability to generate structured, detailed content, which is crucial for this prompt's output quality.
Can I use this prompt for features other than a webinar guide?
While specifically tailored for a 'Webinar Guide,' its underlying structure can be adapted. However, for best results, consider a more generalized user story prompt or modify this one to fit a different feature type.
How detailed should my input for the variables be?
The more detailed and specific your input for each variable (e.g., target audience, core functionality), the more relevant and comprehensive the generated user stories and associated details will be.
What is the purpose of the 'Technical Notes' and 'UI/UX Requirements' sections?
These sections bridge the gap between business requirements and technical/design implementation. Technical Notes provide high-level considerations for developers, while UI/UX Requirements guide designers on interaction and visual elements for the specified audience.