codemap_checklist_add_item
Add an item to a session checklist (session:start or session:close). Items guide workflow at session boundaries.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
text | string | ✅ Required | Checklist item text |
Usage Examples
MCP Usage (for AI Agents like Claude)
json
{
"name": "codemap_checklist_add_item",
"arguments": {
"trigger": "session:start",
"text": "Review project roadmap and prioritize tasks",
"priority": "high"
}
}Example Output
JSON Response
json
{
"success": true,
"item": {
"id": "3",
"text": "Run npm test before committing",
"priority": "high"
},
"trigger": "session:close",
"message": "Added item #3 to session:close checklist"
}When to Use This Tool
-
Use
- Repetitive quality gates - "Run npm test before committing", "Verify code coverage above 80%"
- Workflow enforcement - "Pull latest changes from main", "Update CHANGELOG.md"
- Team alignment - Shared checklists ensure consistent processes across all team members
- Onboarding guidance - Help new developers follow established workflows
- Project-specific gates - "Check database migration status", "Update API documentation" Session checklists are stored in
codemap_checklist_add_item to add persistent workflow reminders that appear at session boundaries. Ideal for:
.codemap/checklists.json (version controlled), making them shared across the entire team.
Common Patterns
Quality Gates at Session Close
Setup Checks at Session Start
Sprint/Release-Specific Items
{
"trigger": "session:close",
"text": "Run npm test before committing",
"priority": "high"
}{
"trigger": "session:close",
"text": "Verify code coverage above 80%",
"priority": "high"
}Setup Checks at Session Start
{
"trigger": "session:start",
"text": "Pull latest changes from main branch",
"priority": "high"
}{
"trigger": "session:start",
"text": "Review NEXT_SESSION.md for context from last session",
"priority": "high"
}Sprint/Release-Specific Items
{
"trigger": "session:close",
"text": "Update CHANGELOG.md with changes",
"priority": "high"
}Pro Tips
Priority matters - Use HIGH for must-do items (tests, builds), MEDIUM for should-do items (documentation), and LOW for nice-to-have improvements (cleanup, optimizations).
Be specific and actionable - Instead of vague reminders like "test things", use concrete commands: "Run
Review monthly - Checklists can become stale. Remove items that are automated or no longer relevant, add new patterns discovered through practice.
Version control = team sync - Since
Be specific and actionable - Instead of vague reminders like "test things", use concrete commands: "Run
npm test to verify all tests pass" or "Execute clean-build.bat to verify clean build".Review monthly - Checklists can become stale. Remove items that are automated or no longer relevant, add new patterns discovered through practice.
Version control = team sync - Since
.codemap/checklists.json is in git, your checklists benefit the whole team. Add items relevant to everyone's workflow.Best Practices
- Keep focused - Aim for 3-5 items per trigger maximum. Too many items lead to checklist fatigue.
- Reference specific tools/commands - Mention exact commands (
npm test,clean-build.bat) rather than generic actions ("test", "build").
Common Mistakes
❌ Mistake: Adding vague reminders like "check things" or "make sure everything works"
✅ Instead: Use specific, actionable items: "Run
❌ Mistake: Making all items HIGH priority, causing priority inflation
✅ Instead: Reserve HIGH for truly critical items (tests, builds, security). Use MEDIUM for important but not critical tasks (documentation updates), and LOW for optional improvements.
✅ Instead: Use specific, actionable items: "Run
npm test to verify all 47 tests pass" or "Verify API documentation updated if endpoints changed"❌ Mistake: Making all items HIGH priority, causing priority inflation
✅ Instead: Reserve HIGH for truly critical items (tests, builds, security). Use MEDIUM for important but not critical tasks (documentation updates), and LOW for optional improvements.