Advanced AI Library. Three Ways to Use It.

Plug it in as a prompt to get an answer. Set it as a goal to complete a complex task. Turn it into a reusable skill for your library.

Each resource is structured for all three.

Category counts cover all available entries.

Tag

Requirements Articulation

Entries tagged Requirements Articulation across the library, including matching entries from the original collection.

Explore entries

Develop User Story Templates for Clear Requirement Articulation

Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.

This prompt is designed to assist product development teams in crafting user story templates that clearly articulate user needs and benefits. The goal is to create a structured approach that ensures user stories are comprehensive and focused on essential requirements, while avoiding unnecessary technical constraints. By developing clear and concise user story templates, teams can better align their product development efforts with user expectations and deliver valuable solutions.

{
  "role": "You are a product development expert specializing in user story creation and requirements articulation.",
  "goal": "Design user story templates for [project name] that clearly capture user needs and benefits, ensuring that stories are comprehensive and free from unnecessary technical constraints.",
  "context": [
    "Consider the target audience's needs, pain points, and desired outcomes.",
    "Include a structure that highlights the user role, desired action, and expected benefit.",
    "Provide examples of well-crafted user stories that adhere to this structure.",
    "Factor in best practices for ensuring clarity and consistency across user stories."
  ],
  "output": [
    "A template format for user stories, including key components such as user role, action, and benefit.",
    "Examples of user stories using the template to demonstrate clarity and alignment with user needs.",
    "Guidelines for avoiding common pitfalls in user story creation.",
    "Recommendations for reviewing and refining user stories to ensure they meet project objectives."
  ],
  "toneStyle": "Clear, structured, and user-focused.",
  "constraints": [
    "Ensure the templates do not include technical jargon that may confuse non-technical stakeholders.",
    "Avoid over-complicating the structure, keeping it simple and effective."
  ],
  "startingQuestions": "Before beginning, determine whether missing information would materially improve the result. If so, ask me up to [3] concise clarifying questions in a single message and wait for my answers. Do not ask for information already provided. If no clarification is needed, proceed immediately.",
  "followUpQuestions": "After presenting the result, only if meaningful uncertainty remains or a useful refinement would improve it, ask up to [3] concise follow-up questions to refine a story example or review criterion. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
  "successCriteria": [
    "Make templates and examples clearly distinguish user role, desired action, and expected benefit.",
    "Use user-focused language tied to the project's needs without unnecessary technical constraints.",
    "Explain review and refinement practices that improve clarity while preserving a simple structure.",
    "Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
  ]
}

End of results.