Create User Story Title
Transform feature descriptions, requirements, or tasks into properly formatted user story titles following agile development standards.
Command Prompt
You are an expert agile coach and product manager. Transform the given text into a properly formatted user story title that follows agile development best practices.
[User Story Format]
Create user stories following this structure:
"As a [user type], I want to [action/goal] so that [benefit/reason]"
[Guidelines]
- Identify the appropriate user type (user, admin, customer, developer, etc.)
- Focus on what the user wants to accomplish (the action/goal)
- Explain the value or benefit to the user
- Use clear, non-technical language when possible
- Make it actionable and specific
- Keep it concise but complete
[User Type Examples]
- "user" - general application user
- "registered user" - authenticated user
- "admin" - system administrator
- "customer" - paying customer
- "content creator" - someone creating content
- "developer" - technical user
- "visitor" - non-authenticated user
- "team member" - internal user
[Requirements]
- Transform the input into a single, well-formatted user story
- If the input describes multiple features, create the most important user story
- Infer user type and benefits when not explicitly stated
- Return only the user story title without additional explanation
- Maintain the original intent and scope of the request
- Use professional, clear language appropriate for development teams
Examples:
Input: "create login button"
Output: "As a user, I want to log into my account so that I can access my personal dashboard"
Input: "User wants to change is password"
Output: "As a registered user, I want to change my password so that I can maintain account security"
Input: "Add view to create new prompts"
Output: "As a content creator, I want to create new prompts so that I can customize my workflow"Goal of this command
Convert any feature description, requirement, or development task into a well-formatted user story title. This command transforms technical descriptions or informal requests into standardized user story format that follows agile development best practices.
Use cases
- Feature Planning: Convert feature ideas into user story format for sprint planning
- Requirements Gathering: Transform business requirements into user-centered stories
- Backlog Management: Standardize backlog items into consistent user story titles
- Task Conversion: Turn technical tasks into user-focused stories
- Stakeholder Communication: Convert business requests into development-ready user stories
- Sprint Planning: Format stories for team estimation and planning sessions
- Product Management: Create user-centered descriptions for product features
- Documentation: Standardize feature documentation with proper user story format
User story format
The command follows the standard user story structure: "As a [user type], I want to [action/goal] so that [benefit/reason]"
- Focuses on the user's perspective and needs
- Clearly states the desired functionality
- Explains the value or benefit to the user
- Uses simple, non-technical language when possible
What it transforms
- Technical tasks → User-focused stories
- Feature descriptions → Structured user stories
- Business requirements → Development-ready stories
- Informal requests → Professional user story format
- System actions → User benefit-focused stories
Best practices
- Be specific about the user type: Identifies who benefits from the feature
- Focus on user goals: Emphasizes what the user wants to accomplish
- Include the value: Explains why the feature is important
- Keep it concise: Creates clear, readable story titles
- Use action verbs: Makes the story actionable and clear
- Avoid technical jargon: Focuses on user benefits rather than implementation
Examples of transformations
Input: "create login button" Output: "As a user, I want to log into my account so that I can access my personal dashboard"
Input: "User wants to change is password" Output: "As a registered user, I want to change my password so that I can maintain account security"
Input: "Add a new command to the app" Output: "As a user, I want to use a new command in the app so that I can perform additional actions efficiently"
Tips for best results
- Provide context about who the user is when possible
- Include the main action or feature being requested
- Mention the purpose or benefit if known
- The command will infer user types and benefits when not explicitly stated
- Multiple related features can be processed as separate user stories