context-switch

You can automate multi-project transitions by triggering a CLI-like surface that reads HEALTH.md, updates a JSON context store, and logs switch history. Initiating a switch requires stating the target project or epic name to guard against unknown targets.

A HEALTH check validates project status by reading HEALTH.md files before transitioning contexts. This mechanism surfaces gaps between documentation and reality, ensuring conscious switches between projects or epics while maintaining an updated JSON context store.

Trigger morning or evening phrases to load main contexts, activate weekday projects, and close current projects. The evening ritual records a victory lap and logs activity for later review, while morning loads the main context and activates additional projects.

Yes, jq is required as a dependency to manage epic transitions and project state. The skill uses jq alongside scripts to process JSON context stores and coordinate HEALTH checks across backstage contexts during project and epic switches.

Guards validate the target before transitioning, blocking switches to unknown project or epic targets. The skill reads HEALTH.md and updates a JSON context store only for recognized targets, preventing context confusion from invalid switches.

Use an evening ritual trigger to close the current project context, record a victory lap, and log switch history. This approach stores activity data in a JSON context store for later review, ensuring conscious daily closure across multiple projects.