Loading templates
Bringing in starter structures for your notes.
Ready-made markdown structures for meetings, code docs, product planning, and personal notes — pick one and start writing.
Meetings & collaboration
Structured notes for syncs, standups, retros, and 1-on-1s — so decisions and action items never get lost.
# Meeting notes
**Date:**
**Attendees:**
**Facilitator:**
## Agenda
1.
Agenda, discussion notes, decisions, and follow-up tasks in one doc.
# Standup — <date>
**Team:**
## Yesterday
-
## Today
-
Yesterday, today, and blockers — quick async updates for the team.
# Retrospective — Sprint <N>
**Date:**
**Participants:**
## What went well 🎉
-
## What did not go well
What went well, what did not, and concrete improvements for next sprint.
# 1-on-1 — <name>
**Date:**
**Next meeting:**
## Their updates
-
## My talking points
Talking points, feedback, and growth goals for manager or peer check-ins.
# Sprint planning — Sprint <N>
**Dates:**
**Sprint goal:**
## Capacity
| Member | Available days | Notes |
|--------|----------------|-------|
Capacity, sprint goal, committed stories, and risks before kickoff.
Engineering & code
Templates developers actually use — PRs, RFCs, ADRs, bug reports, and postmortems with the right sections baked in.
# PR: <title>
## Summary
What does this change and why?
## Changes
-
## Testing
Summary, changes, testing evidence, and a reviewer checklist.
# RFC: <title>
**Status:** Draft
**Author:**
**Reviewers:**
## Context
Why are we doing this?
Context, goals, proposed design, alternatives, and open questions.
# ADR 001: <decision title>
**Status:** Proposed
**Date:**
## Context
## Decision
## Consequences
Record one decision, its trade-offs, and consequences for the team.
# Bug: <short title>
**Severity:**
**Reporter:**
## Steps to reproduce
1.
2.
Repro steps, expected vs. actual behavior, environment, and logs.
# Postmortem: <incident>
**Date:**
**Severity:**
**Duration:**
**Owner:**
## Impact
Blameless timeline, root cause, resolution, and follow-up actions.
# API: <service name>
**Version:**
**Base URL:**
## Authentication
## Endpoints
### `GET /resource`
Endpoints, request/response shapes, auth, and error handling.
# Code review: <PR / branch>
**Reviewer:**
**Author:**
## Summary of change
## Correctness
- [ ] Logic matches requirements
Structured review notes for correctness, security, and maintainability.
Planning & product
Briefs, specs, user stories, and roadmaps that keep scope, stakeholders, and success metrics in one place.
# Project brief: <name>
**Owner:**
**Target date:**
## Problem statement
## Goal
## Scope
Goals, scope, stakeholders, timeline, and success metrics.
# Spec: <feature name>
**Author:**
**Status:** Draft
## Problem
What user pain are we solving?
## Proposed solution
User problem, requirements, UX notes, and acceptance criteria.
# Story: <title>
**Epic:**
**Priority:**
**Estimate:**
## Story
As a **<role>**, I want **<goal>** so that **<benefi…
Single story with context, acceptance criteria, and technical notes.
# OKRs — Q<quarter> <year>
## Objective 1: <headline>
| Key result | Target | Current | Status |
|------------|--------|---------|--------|
| KR 1 | | | 🟡 |
| KR 2 | | | ⚪ |
Objectives and measurable key results for the quarter.
# Roadmap — <product / team>
**Last updated:**
## Now (this sprint / month)
-
## Next (upcoming)
-
Now, next, and later buckets with themes and dependencies.
Personal & learning
Journals, reviews, reading lists, and research docs for staying organized outside the sprint cycle.
# Journal — <date>
## Morning
**Intention for today:**
## Highlights
-
## Challenges
Morning intentions, evening reflections, and gratitude.
# Weekly review — Week of <date>
## Wins 🎉
-
## Challenges
-
## Lessons learned
Wins, blockers, lessons, and priorities for the week ahead.
# Reading list
## To read
- [ ] **Title** — author / link
## In progress
- **Title** — notes so far
## Finished
Queue articles and books with key takeaways when finished.
# Research: <topic>
**Started:**
**Status:**
## Hypothesis / question
## Sources
1.
Hypothesis, sources, findings, and open questions.
# Interview prep — <company / role>
**Date:**
**Format:**
## About the company
-
## Role requirements
Company research, STAR stories, questions to ask, and follow-ups.
Create a free account, then use any template to spin up a structured note in seconds.