Thanks for your interest in improving story breakdown for Product Owners!
Have a problem that needs a prompt solution? File an issue first.
Process:
- Go to Issues
- Select "Prompt Idea" template
- Describe your problem and how often you face it
- If it's recurring, we'll create a prompt
Why issue first?
- ✅ Focus on recurring problems (not one-time issues)
- ✅ Avoids duplicate prompts
- ✅ Others can suggest existing solutions
What happens after:
- Recurring problem → We create the prompt
- One-time issue → We explain why no prompt needed
- Duplicate → We point you to existing prompt
Found a better way to phrase a prompt?
- Fork the repository
- Edit the prompt file (
prompts/*.md) - Test it with ChatGPT/Claude
- Submit Pull Request with before/after example
PR Requirements:
- Show example output (before and after)
- Explain why your version is better
- Keep prompt under 500 words
Used a prompt successfully? Share your story!
- Fork the repository
- Add to
examples/directory - Use
before-bad-story.mdformat - Submit Pull Request
What makes a good example:
- Real project (anonymize company details)
- Shows actual impact (time saved, surprises avoided)
- Before/after comparison
- 200-300 words max
Small fixes welcome via Pull Request directly. No issue needed.
- ❌ Prompts for one-time problems (file issue first to discuss frequency)
- ❌ Overly complex prompts (> 500 words)
- ❌ Prompts for non-Product Owner audiences
- ❌ Time-to-points mappings (story points ≠ hours)
- ❌ Tool-specific instructions (keep it generic)
- ❌ Agile theory debates (link to official sources instead)
- Be respectful and constructive
- Focus on problems, not people
- Help others learn
Open a Discussion or file an Issue.