agentstable
Template for an autonomous, one-shot subagent: frontmatter (name, description, tool allowlist, model), a numbered job, ranked priorities for when instructions conflict, shared-worktree discipline, a STATUS report contract, worked examples, red flags, a machine-readable RESULT_JSON line, and a capacity rule. For a conversational persona with a voice, use template/persona instead.
- format
- markdown
- fills
- 22 placeholders
adrstable
The MADR 4.0.0 decision-record template: metadata, context and problem statement, decision drivers, considered options, decision outcome with consequences and confirmation, pros and cons per option, more information. One file per decision under docs/adr/. Sections marked optional in the comments may be deleted.
- format
- markdown
- fills
- 23 placeholders
commit-messagestable
A Conventional Commits message: typed subject in the imperative under 72 characters, a body that explains why (not what) wrapped at 72, and the provenance trailer when an AI wrote significant code.
- format
- text
- fills
- 5 placeholders
handoffstable
Cross-session continuity document written at a context boundary: current state, next steps, open questions, files in flight, last known-good commit, audit references. The resuming session verifies every gating assertion against live state before acting on it.
- format
- markdown
- fills
- 9 placeholders
planstable
A plan with an alternatives table, scope, numbered approach, tests, risks, dependencies, and backward compatibility. No TBD or TODO in the final draft. Required before non-trivial work starts.
- format
- markdown
- fills
- 9 placeholders
postmortemstable
A blameless postmortem written within 48 hours of resolution: impact, timeline, root cause, contributing factors, what went well, and dated action items with owners.
- format
- markdown
- fills
- 11 placeholders
personastable
Template for a conversational, character-driven persona that holds a voice across many turns: who you are, how you speak, always/never behaviours, situation handling, how you think, ranked priorities, what is fixed versus what can shift, hard limits, staying in character under pressure, example exchanges, reading list, permitted change, and a closing restatement of the limits that never bend. For a one-shot task worker use template/agent.
- format
- markdown
- fills
- 26 placeholders
pull-requeststable
A PR body a reviewer can act on: a summary that names the non-obvious decisions, what changed by area, a checkable test plan, and anything the reviewer should know before merging.
- format
- markdown
- fills
- 4 placeholders
readmestable
The README every repository must have, answering four questions in order: what is this, who is it for, how do I run it, how do I contribute or extend it. Short by design; detail lives in linked documents.
- format
- markdown
- fills
- 6 placeholders
runbookstable
The operations runbook every production system must have: what healthy looks like, what sick looks like, how to recover, whom to escalate to, and what on-call is expected to do. Every alert must map to an entry here.
- format
- markdown
- fills
- 8 placeholders
Nothing matches. Clear a filter or try the global search (/).