Feature Checklist
Overview
Use this checklist before merging a feature.
Why It Matters
A consistent feature checklist prevents common shipping misses.
Core Concepts
- Confirm the happy path.
- Confirm loading and error states.
- Confirm accessibility and responsiveness.
Mental Models
Treat the checklist as the final quality sweep, not a substitute for understanding the feature.
Best Practices
- Keep it short enough to use every time.
- Pair it with the PR.
- Update it when bugs reveal gaps.
Common Mistakes
- Adding too many items.
- Skipping verification because the feature “looks fine.”
- Forgetting rollback or flags when the risk is high.
Trade-offs
More checklist items improve coverage, but too many items reduce compliance.
Decision Framework
| Check | Pass |
|---|---|
| Behavior | Works as intended |
| UX | Loading, empty, error covered |
| Risk | Rollback or fallback exists |
Examples
- Validate keyboard interaction.
- Confirm API failure handling.
- Check responsive layout.
Checklists
- Did I verify the main flow?
- Did I test the failure path?
- Did I confirm no obvious regressions remain?
Senior Engineer Notes
Senior engineers use checklists to protect reliability when speed is high.