Checklists

Validation checklists that agents use as quality gates during workflows. Checklists live in _bmad/atlassian/checklists/ and ensure artefacts meet required standards before progressing.

Checklist Reference

Checklist	File	Used By	Description
PRD Validation	prd-checklist.md	PM (John)	Validates PRD quality, completeness, and cohesion before planning proceeds
Create Story	create-story-checklist.md	SM (Bob)	Ensures story has sufficient dev context, clear ACs, and proper subtask breakdown
Sprint Planning	sprint-planning-checklist.md	SM (Bob)	Validates sprint scope, story sequencing, and capacity alignment
Dev Story	dev-story-checklist.md	Dev (Amelia)	Enhanced definition of done -- implementation complete, tests passing, docs updated
Code Review	code-review-checklist.md	QA (Quinn)	Senior developer review criteria -- correctness, security, performance, maintainability
Course Correction	correct-course-checklist.md	SM (Bob)	Change navigation checklist for mid-implementation pivots
Document Project	document-project-checklist.md	Tech Writer (Paige)	Quality gate for project documentation completeness and accuracy

How Checklists Are Used

Checklists are referenced in workflow YAML files and artefact mapping entries. When an agent reaches a validation step, it evaluates the checklist items against the current artefact:

1. Agent loads the checklist from the file path
2. Each item is evaluated against the artefact content
3. Failures are reported as Confluence comments or Jira comments
4. The overall verdict (PASS / PASS WITH NOTES / NEEDS REVISION) determines whether the workflow proceeds

Verdict Outcomes

Verdict	Meaning	Action
PASS	All checklist items satisfied	Workflow continues to next phase
PASS WITH NOTES	Minor issues that don't block progress	Workflow continues; notes recorded for follow-up
NEEDS REVISION	Critical issues found	Workflow pauses; artefact must be revised before proceeding