# For payment hotfixes
ctx-hotfix PAYMENT-1234 "Fix CyberSource validation"
# For general development
ctx create feature-name --description "Description"
ctx set-state in-progress# Mark ready for review
ctx-handoff
# Block on dependency
ctx-block
# Complete work
ctx-done# See all active team work
ctx-team
# Check current status
ctx-status
# Switch between contexts
ctx-switch context-namepayment-hotfix-template.sh- Structured payment hotfix workflowhandoff-checklist.md- Team handoff requirements
- π
pending- Not started - π»
in-progress- Active development - π
in-review- Ready for handoff/review - π«
blocked- Waiting on dependency - β
completed- Work finished
- Use structured notes:
TYPE: description | METADATA: details - Clear handoffs: Include branch, PR, and test instructions
- Update states: Keep team informed of progress
- Document decisions: Add rationale for technical choices
- Tag stakeholders: Use @mentions in notes for visibility
Your ctx contexts are connected to memory for knowledge retention:
- Technical patterns are captured automatically
- Previous solutions are searchable
- Team knowledge builds over time