GV
Gabriela V.Verified purchase
Your cart is empty
Add prompt packs to continue
Copy, paste and use them in your favorite AI:
Just $0.08 per prompt · one-time payment
100 resources included
This master collection of Scrum prompts has been designed to radically transform the efficiency of Scrum Masters, Product Owners and development teams. Through precise instructional engineering, this resource allows you to automate the creation of artifacts, optimize the facilitation of ceremonies and deepen the analysis of critical metrics, eliminating ambiguity in each phase of the agile framework. By integrating these prompts into their workflow, professionals will be able to scale their strategic capabilities, ensuring that every User Story meets the highest standards and that every Sprint Retrospective drives real change. It is the definitive tool for those seeking to lead an agile transformation based on data, tangible results and impeccable communication with all levels of the organization.
Acts as an expert Senior Agile Coach and Product Manager with specialization in framework scaling and value stream management. Your mission is to design a robust information architecture and work hierarchy for the [Project_Name] project, whose strategic objective is [Primary_Objective]. I need you to transform a disorganized list of needs into a coherent multi-level structure that facilitates the refinement of the Product Backlog, ensuring that each element contributes directly to the product vision and is executable by the development team. First, it defines a clear taxonomy divided into four levels: Initiatives (Strategic Themes), Epics (Large blocks of functionality), User Stories (Deliverable Units of Value) and Sub-tasks (Technical Implementation Steps). For the context of [Key_Categories], break down the Epics by identifying their critical dependencies and assigning them a relative business value. It is essential that User Stories follow the INVEST standard (Independent, Negotiable, Valuable, Estimable, Small and Testable) and that they include detailed Acceptance Criteria under the Gherkin format (Given, When, Then). Second, it establishes a technical and business prioritization framework adapted to the [Average_Complexity] of the current environment. Use methods such as MoSCoW or WSJF (Weighted Shortest Job First) to organize the backlog so that the team maximizes ROI in each Sprint. Explains how this hierarchy should be displayed in the [Management_Tool] tool to maintain complete traceability, from the code to the business strategy, avoiding the creation of information silos or accumulated technical debt due to lack of decomposition. Finally, generate a 'Healthy Refinement' protocol that dictates how and when to decompose Epics into User Stories as they approach the top of the Backlog. Provides a complete practical example of a hierarchical chain: from a global Initiative of [Project_Name] to three granular technical tasks, including the definition of 'Ready' (DoR) and the definition of 'Done' (DoD) that ensure quality at each level of the proposed structure. If any key information needed to fill the bracketed fields is missing, ask me the necessary questions before answering.
Instant access after purchase from your dashboard. Just copy and paste into your AI.
ChatGPT, Claude, Gemini, DeepSeek, Grok, Qwen and any AI chat.
Yes. Every prompt includes bracketed fields where you insert your own information, context and specifics, so they fit your situation, country or industry.
Yes. Above you can read full sample prompts, exactly as you'll receive them, to check the quality before paying.
Yes. Pay once and they're yours forever, updates included.
Acts as a Senior Agile Coach and Product Owner with over 15 years of experience leading agile transformations and backlog refinements in high-scale SAFe and Scrum environments. Your main objective is to carry out an exhaustive technical and functional decomposition of the Epic titled: "[Title of the Epic]", which is framed within the product "[Name of the Project or Product]" and has as its main vision: "[Vision/Objective of the Epic]". Carefully analyze the description provided and apply the 'Vertical Slicing' technique to break down this macro-functionality into incremental User Stories (US) that deliver real value from end to end. You must ensure that each resulting story strictly complies with the INVEST (Independent, Tradeable, Valuable, Estimable, Small and Testable) standard. Consider the following business success criteria: "[KPIs or Success Criteria]" and the current technological constraints: "[Technical/Architecture Restrictions]". For each User Story generated, you must structure the information as follows: 1. ID and action-oriented descriptive Title. 2. User narrative in standard format: 'As [Person/Role], I want [Action/Functionality], so that [Value/Benefit]'. 3. Detailed Acceptance Criteria written in BDD (Behavior Driven Development) language using Gherkin syntax (Since... When... Then...). 4. Suggested estimation in Story Points following the Fibonacci series and briefly justifying the complexity. 5. Proactive identification of critical dependencies (blockers) and associated technical risks. Once the breakdown is done, organize the User Stories using the MoSCoW (Must have, Should have, Could have, Won't have this time) prioritization method based on the impact on the end user and the expected return on investment (ROI). Additionally, propose a release strategy (MVP/MMP) indicating which stories are essential for the first iteration. If you find that any aspect of the original Epic is too ambiguous, point out specifically what information is missing to complete an optimal Product Backlog refinement. If any key information needed to fill the bracketed fields is missing, ask me the necessary questions before answering.
Acts as a Senior Product Manager and high-level Agile Consultant with a specialty in value stream optimization. Your objective is to perform an audit and strategic re-prioritization of a Product Backlog based exclusively on the return on investment and the strategic impact for the organization. To begin, thoroughly analyze the following [List of PBIs/Tasks] in light of the [Strategic Business Objectives] provided, ensuring that each ordering decision is supported by solid market logic and qualitative or quantitative data. You will use the prioritization framework [Choose Framework: WSJF, RICE, MoSCoW or KANO] to evaluate each element individually and comparatively. For each backlog item, you must calculate and justify four fundamental pillars: 1. Value for the End User (Improvement in experience or resolution of pain points), 2. Value for the Business (Direct increase in revenue, reduction of Churn, operational savings or legal compliance), 3. Risk Reduction or Enabling Opportunities (Mitigation of technical debt or preparation for future markets), and 4. Estimated Effort (Based on perceived complexity or points of history). It is vital that you identify the 'Cost of Delay' for the most critical items identified in the [PBI/Task List]. The final result must be presented in a structured comparative table that includes the score broken down by each criterion of the selected framework and a 'Strategic Justification' column. Additionally, it identifies possible blocking dependencies that could override the proposed priority order. If the [Technical Context or Capacity Limitations] suggests that a high-value item is unfeasible in the short term, propose a minimalist version (MVP) or a research 'Spike' to unlock it as soon as possible. Your analysis must be robust and professional enough to be presented in a review session with C-Suite level stakeholders. Conclude the exercise with an executive summary of the top 5 absolute priorities, detailing why these specific actions maximize the value of the product in the next execution cycle or sprint. Ensure that all recommendations are aligned with the product vision described in [Product Vision or Additional Context] to maintain long-term cohesion, avoid wasted resources, and prevent feature creep. If any key information needed to fill the bracketed fields is missing, ask me the necessary questions before answering.
It's a master instruction, optimized for AI.
Prompt
your instruction
AI
Result
Based on 8 reviews
It's fine, nothing more. I had to tweak them quite a bit for my case. Works if you customize it.
Best purchase I made this month. They work just as well in ChatGPT and Claude. One hundred percent recommended.
Worth every penny. They're easy to adapt to my case by just changing the fields. Already recommended them to my team.
Happy with the purchase. The prompts are useful and practical. I'd buy again.
Very good material. The organization helps you get oriented fast. Came close to a five.
Exactly what I was looking for. They're easy to adapt to my case by just changing the fields. One hundred percent recommended.
I was impressed by the quality. The index is organized and I find what I need instantly. Totally recommend them.
Exceeded my expectations. They're easy to adapt to my case by just changing the fields. An investment that pays for itself.