Backlog.md MCP Workflow Skill

Core Principle: Track Commitments, Not Activity

Backlog tracks what will be built. Use it when work requires planning, decisions, or coordination across sessions. Skip it for trivial mechanical changes that can be completed immediately.

Use Backlog when:

• Work requires planning or architectural decisions
• Multiple deliverables need coordination
• Other sessions might duplicate effort
• Progress tracking benefits stakeholders
• Work spans multiple sessions

Skip Backlog when:

• Single trivial change (typo fix, simple config update)
• Immediate execution with no planning needed
• Work completes in < 5 minutes
• No coordination required