Templates
Start from something an agent can rewrite.
Blueprints your agent fetches, rewrites in your words, and publishes as a page you can send to someone. Browse by the job, then make them yours.
Meetings & recaps
What was said, what was decided, and who owes what by when.
Daily digestA newspaper-style daily desk: a complete story index beside four open, ruled articles with relevance, summaries and evidence, followed by a native six-item archive.
Interview notesA voice-and-interpretation spread: a broad serif quotation beside the participant identity, then paired verbatim evidence and analyst readings with timed quotes and owned next actions.
Meeting recapA working meeting handover: six owned actions lead beside complete decision minutes, with compact outcome counts, explicit deferrals and open questions that keep their owners and deadlines.
Decisions & proposals
The options, the recommendation, and the ask — with a deadline on it.
Decision briefAn evidence-first option bench: a compact recommendation above the full five-criterion comparison, the selected option marked in words, then rejected alternatives, explicit asks and the decision deadline.
One-pagerThe markdown starter, and the only built-in that takes slots: send `template` plus `title`, `subtitle` and `body` and the server merges them. Deliberately plain — it is a form to fill, not a page to rewrite.
ProposalA single argument with the dated decision first, then the problem, cost, payoff, trade-off and evidence in a numbered decision spine.
SpecA technical requirements folio: in-and-out scope, ruled ID and priority records pairing each requirement with its acceptance clause, then blocking questions with their owners and timings.
Research & reports
Long-form work somebody will read properly and probably forward.
Case StudyAn evidence spread: the customer outcome opposite five before/after metric records, followed by serif customer voices, the operational story and an equally prominent honest-cost section.
Incident PostmortemA blameless incident atlas: impact accounting beside the failure trace, a time-indexed incident record, the complete root cause and contributing factors, then owned action items with due dates and states.
ReportThe serious long document: an editorial masthead followed by a briefing band that puts the finding beside its recommendation and quarter evidence, then numbered sections with a ranked magnitude figure, a customer quote, and owned next steps with dates.
Research BriefAn evidence register: the question and answer qualified immediately by confidence and method, five claims beside their provenance, a grouped source register, and the conditions and unknowns that could change the answer.
Status & dashboards
Where things stand, with every number against a target.
Metrics DashboardA recurring performance sheet: a broad twelve-week trend beside a compact metric ledger, change commentary directly below, then a channel breakdown and service levels metered against their targets.
Project StatusA decisions-first sponsor dispatch: the changed verdict beside two owned, dated asks, followed by committed milestones, scope totals, and blockers with their owners, ages and next decisions.
Service HealthA reliability review that treats uptime as a budget rather than a state: how much unreliability is left this quarter, a burn-down showing where it went, the incidents ranked by budget consumed rather than by date.
Releases & announcements
What shipped, what broke, and what a reader has to do about it.
ChangelogA release ledger: the latest version and date beside two complete breaking-action records, followed by version, change type and release notes, with a native archive.
Launch announcementA dark launch poster pairs the headline and update links with an offline-flow diagram, then shifts to a light beta-evidence strip, open feature rows and a practical trial sequence.
Migration guideA conversion workbench: version and deadline context above paired before/after code, followed by three execution steps with exact commands and output, troubleshooting and support dates.
Plans & runbooks
What happens next, in the order it happens, with an owner on each step.
ChecklistA readiness review that leads with what is still in the way: the blocking count as the hero number, a segmented meter of every item reviewed, the blockers in full with owner and date, everything cleared listed by area, and the waivers with who signed them and when they come back.
Project planPhases, owners, dates and dependencies on one page: a seventeen-week phase-and-gate ledger with a today line and all four phases, followed by each phase's deliverables and exit criterion, cross-team dependencies, and risks with mitigations.
RunbookAn operator’s bench: static preconditions beside the procedure, labelled command/output records and a complete verification check between steps four and five, followed by rollback and escalation.
How your agent uses one
Your agent lists what is here, fetches the one that fits, rewrites it in your words and your colours, and publishes the result as its own page. These are starting points — the templates you keep are the ones you have made yours.
GET /v1/templates?category=meetings
GET /v1/templates/meeting-recapThe same call returns your own saved templates alongside these, so an agent browsing for a starting point sees your work and ours in one answer.