↓ Skip to main content
eval ( code )
  1. Dev Handbook/

🧾 Templates: Don't Start From a Blank Page

Table of Contents

Templates exist so your team doesn’t reinvent the wheel every time they file a bug, propose a feature, or open a pull request. A good template isn’t bureaucracy. It’s a checklist that catches the things people forget when they’re moving fast.

In this section:

How to use these
#

Copy them into your project and adapt them. Remove sections that don’t apply to your team. Add sections that do. The goal is consistency, not compliance. If everyone on the team uses the same structure, reading and reviewing each other’s work gets dramatically faster.

Templates reduce back-and-forthThe most common reason a ticket or PR needs revision isn’t that the work is wrong. It’s that the author forgot to include context that the reviewer needs. A template with the right prompts catches this at writing time instead of review time. Less back-and-forth, faster cycle times.
Don't let templates become a formalityIf people are filling in template sections with placeholder text just to satisfy the format, the template is working against you. Every section should earn its place. If nobody reads the “Testing” section on your feature proposals, remove it. A half-filled template is worse than no template because it trains people to ignore the structure entirely.