# [CHECKLIST TYPE] Checklist: [FEATURE NAME]

**Purpose**: [Brief description of what this checklist covers]  
**Created**: [DATE]  
**Feature**: [Link to spec.md or relevant documentation]  

**Note**: This checklist is generated by the `/speckit.checklist` command based on feature context and requirements.

<!-- 
  ============================================================================
  IMPORTANT: The checklist items below are SAMPLE ITEMS for illustration only.
  
  The /speckit.checklist command MUST replace these with actual items based on:
  - User's specific checklist request
  - Feature requirements from spec.md
  - Technical context from plan.md
  - Implementation details from tasks.md
  
  DO NOT keep these sample items in the generated checklist file.
  ============================================================================
-->

## Constitutional Compliance Check

Before proceeding, verify alignment with constitutional principles:

- [ ] **Code Quality (Principle 1):** Design maintains/improves maintainability
- [ ] **Testing (Principle 2):** ≥80% coverage plan established
- [ ] **UX Consistency (Principle 3):** User impact documented and positive
- [ ] **Performance (Principle 4):** Performance budget and complexity analyzed

## [Category 1]

- [ ] CHK001 First checklist item with clear action
- [ ] CHK002 Second checklist item
- [ ] CHK003 Third checklist item

## [Category 2]

- [ ] CHK004 Another category item
- [ ] CHK005 Item with specific criteria
- [ ] CHK006 Final item in this category

## Pre-Merge Validation

Per constitutional requirements:

- [ ] All tests passing (≥80% coverage maintained)
- [ ] Linter/type checker passing (zero errors)
- [ ] Code review approved with principle verification
- [ ] Documentation updated
- [ ] Performance benchmarks met (if applicable)

## Notes

- Check items off as completed: `[x]`
- Add comments or findings inline
- Link to relevant resources or documentation
- Items are numbered sequentially for easy reference