Checklists
QA, release, security, and review checklists written as simple Markdown task lists.
Checklists cover QA checklists, release checklists, security verification, deployment verification, and review checklists.
What a Checklist is for
A Checklist uses the same Markdown content field as every other resource type — write your items as a standard GitHub-flavored Markdown task list:
- [ ] Run the full test suite
- [ ] Confirm environment variables are set
- [ ] Notify the on-call engineer
There's no separate structured "checklist item" data model — it's plain Markdown task-list syntax, which renders as checkboxes and is easy for both people and AI tools to parse. You can group items under headings (e.g. "Before you deploy" / "After you deploy") the same way you would in any other Markdown document.
Creating a Checklist
- Open a project and go to its Checklists tab.
- Click Create, give it a title and description, and write your items as
- [ ]lines (optionally grouped under##headings) in the Markdown editor. - Save — created as v1, in draft.
Editing, versions, and publishing
Same model as every content-bearing resource: title/description edits are separate from content edits, a content save creates a new version rather than replacing the live one, and an org admin promotes a version to Main to publish it. See Versioning & Publishing.
Who can write
Creating, editing, publishing, and deleting a Checklist requires org-admin-level project access (owner/moderator). Everyone with project access can read every Checklist, draft or published.
Bundling into an Agent Profile
A Checklist can be bundled into an Agent Profile — for example, a "QA" profile that combines your test-plan Checklist with the relevant Instructions and Contexts a tester needs.