# [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
- **CONSTITUTION COMPLIANCE**: All checklists must include constitution gates
DO NOT keep these sample items in the generated checklist file.
============================================================================
-->
## Constitution Compliance (Required for All Features)
### Code Quality First
- [ ] CHK001 Zero linter errors or warnings (Biome for TS/JS, ruff+black for Python)
- [ ] CHK002 Complete type annotations/declarations (strict mode)
- [ ] CHK003 All code formatted via automated tools (Biome for TS/JS, Black for Python)
- [ ] CHK004 Functions under 50 lines, single responsibility
- [ ] CHK005 All public APIs documented with examples
- [ ] CHK006 No TODOs/FIXMEs without tracking
- [ ] CHK007 Existing packages/solutions evaluated before custom implementation
### Test-First Development
- [ ] CHK007 Tests written before implementation
- [ ] CHK008 Red-Green-Refactor cycle followed
- [ ] CHK009 ≥80% code coverage achieved
- [ ] CHK010 Unit tests for all functions/methods
- [ ] CHK011 Integration tests for API/external services
- [ ] CHK012 Contract tests for MCP tools/interfaces
- [ ] CHK013 Tests are deterministic and fast (<5s suite)
### User Experience Consistency
- [ ] CHK014 MCP tool naming follows conventions (verb-based)
- [ ] CHK015 Parameters named consistently with existing tools
- [ ] CHK016 Error messages are human-readable and actionable
- [ ] CHK017 Response formats consistent with existing patterns
- [ ] CHK018 Breaking changes trigger major version bump
- [ ] CHK019 Deprecation warnings added before removal
### Latest Dependencies Always
- [ ] CHK020 **Context7 MCP consulted** for all library integrations
- [ ] CHK021 All packages use latest stable versions
- [ ] CHK022 Version pinning in lock files
- [ ] CHK023 No deprecated dependencies used
- [ ] CHK024 Security vulnerabilities checked (npm audit / pip-audit)
### Documentation-Driven Development
- [ ] CHK025 **Context7 docs retrieved** before implementing library features
- [ ] CHK026 Feature spec written and approved before code
- [ ] CHK027 API documentation complete with examples
- [ ] CHK028 Quickstart guide works in <5 minutes
- [ ] CHK029 Architecture decisions documented (ADR format)
- [ ] CHK030 CHANGELOG.md updated
### Integration Testing Discipline
- [ ] CHK031 MCP tools have integration tests against real API
- [ ] CHK032 Contract validation tests passing
- [ ] CHK033 Error scenarios tested (network failures, rate limits)
- [ ] CHK034 End-to-end user story flows validated
- [ ] CHK035 Performance baselines established
### Observability & Debuggability
- [ ] CHK036 Structured logging with correlation IDs
- [ ] CHK037 Errors include stack traces and context
- [ ] CHK038 Performance metrics tracked
- [ ] CHK039 Debug mode available via environment variable
- [ ] CHK040 Request flows traceable across async operations
## [Category 1]
- [ ] CHK041 First checklist item with clear action
- [ ] CHK042 Second checklist item
- [ ] CHK043 Third checklist item
## [Category 2]
- [ ] CHK044 Another category item
- [ ] CHK045 Item with specific criteria
- [ ] CHK046 Final item in this category
## 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
- **Constitution compliance items (CHK001-CHK040) are MANDATORY for all features**
