Skip to content

Checklists Reference

Checklists define quality criteria evaluated during review gates. Each checklist item is scored as PASS, WARN, or FAIL. Checklists are stored as YAML files in .sniper/checklists/.

Available Checklists

Protocol Phase Checklists

These checklists evaluate artifacts produced during protocol phases.

ChecklistUsed ByDescription
discoverFull, Explore protocolsEvaluates discovery artifacts — brief, risks, research
defineFull, Feature protocolsEvaluates PRD and requirements
designFull, Feature protocolsEvaluates architecture document
solveFull, Feature protocolsEvaluates story breakdown and acceptance criteria
implementFull, Feature, Patch protocolsEvaluates implementation — code quality, tests
reviewAll protocols with review phaseFinal review of all phase artifacts
retroFull, Feature, Refactor protocolsEvaluates retrospective completeness

Protocol-Specific Checklists

ChecklistUsed ByDescription
multi-faceted-reviewReview gatesThree-dimension review: scope, standards, risk scoring
refactor-analyzeRefactor protocolEvaluates refactoring analysis and safety

Ingest Protocol Checklists

ChecklistUsed ByDescription
ingest-scanIngest protocol — scan phaseEvaluates codebase scanning completeness
ingest-documentIngest protocol — document phaseEvaluates generated documentation quality
ingest-extractIngest protocol — extract phaseEvaluates extracted conventions and patterns

Evaluation Scoring

During a review gate, each checklist item receives a score:

ScoreMeaningImpact
PASSCriterion is fully metNo action needed
WARNCriterion is partially met or needs attentionDoes not block in flexible mode
FAILCriterion is not metBlocks advancement in strict mode

Gate Modes

How checklist results affect phase advancement depends on the gate mode:

  • Strict — any FAIL blocks advancement; requires explicit human approval
  • Flexible — auto-advances if no FAIL items; warnings are noted
  • Auto — no evaluation performed; phase advances immediately