e3f756488a
- Add markdownlint-cli2 as dev dependency - Add lint:md script to package.json - Add markdownlint job to CI workflow - Configure 5 rules: heading-increment, no-duplicate-heading, no-trailing-punctuation, no-bare-urls, no-space-in-emphasis - Fix existing violations across 19 markdown files - No auto-fix to prevent destructive changes Closes #1034 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>
2.4 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| V6 Idea Submission | Suggest an idea for v6 |
Idea: [Replace with a clear, actionable title]
PASS Framework
Problem:
What's broken or missing? What pain point are we addressing? (1-2 sentences)
[Your answer here]
Audience:
Who's affected by this problem and how severely? (1-2 sentences)
[Your answer here]
Solution:
What will we build or change? How will we measure success? (1-2 sentences with at least 1 measurable outcome)
[Your answer here]
[Your Acceptance Criteria for measuring success here]
Size:
How much effort do you estimate this will take?
- XS - A few hours
- S - 1-2 days
- M - 3-5 days
- L - 1-2 weeks
- XL - More than 2 weeks
Metadata
Submitted by: [Your name]
Date: [Today's date]
Priority: [Leave blank - will be assigned during team review]
Examples
Click to see a GOOD example
Idea: Add search functionality to customer dashboard
Problem:
Customers can't find their past orders quickly. They have to scroll through pages of orders to find what they're looking for, leading to 15+ support tickets per week.
Audience:
All 5,000+ active customers are affected. Support team spends ~10 hours/week helping customers find orders.
Solution:
Add a search bar that filters by order number, date range, and product name. Success = 50% reduction in order-finding support tickets within 2 weeks of launch.
Size:
- M - 3-5 days
Click to see a POOR example
Idea: Make the app better
Problem:
The app needs improvements and updates.
Audience:
Users
Solution:
Fix issues and add features.
Size:
- Unknown
Why this is poor: Too vague, no specific problem identified, no measurable success criteria, unclear scope
Tips for Success
- Be specific - Vague problems lead to vague solutions
- Quantify when possible - Numbers help us prioritize (e.g., "20 customers asked for this" vs "customers want this")
- One idea per submission - If you have multiple ideas, submit multiple templates
- Success metrics matter - How will we know this worked?
- Honest sizing - Better to overestimate than underestimate
Questions?
Reach out to @OverlordBaconPants if you need help completing this template.