Task List Markdown Template
A GFM-compliant checklist formatting layout. Perfect for project roadmaps, pre-launch checklists, QA test scripts, and dev todo lists.
Why Use This Task List Template?
Task checklists keep deployment procedures structured. Rather than relying on memory during sensitive releases, a code-tracked markdown checklist lists every step, check, and verification. Because it is simple text, you can track it in git branches alongside deployment updates, providing audit trails.
When to Use This Format
Use this layout inside repository readme files, deployment guides, issue templates, and QA checklists. It parses natively inside standard developer platforms like GitHub and GitLab.
Common Formatting Mistakes to Avoid
- Incorrect Case inside Checkboxes: In GFM, an incomplete task requires a space between brackets (
[ ]), while a complete task requires a lowercase x ([x]). Capital X ([X]) may fail in some parsers. - Missing Space after Bracket: There must always be a space after the closing bracket, e.g.
- [ ] Task name. Omitting this space will fail to render checkboxes. - Not Nesting Lists Correctly: For nested checkboxes, indent the sub-items by exactly 2 or 4 spaces to preserve sub-hierarchies.
Customization Steps
- Set section H2 names to represent your dev phases (e.g. Pre-Release, QA, Deploy).
- Update check status in brackets: set complete items as
[x]. - Add nested task items by applying 2 spaces of indentation to list items.
- Save files inside your project repository as standard `.md` checklists.