pilgrimage-tracker

Tracks multi-session campaign progress with persistent state files.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/BertCalm/xo-ox-claude-config --skill pilgrimage-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilgrimage-tracker
Source: https://github.com/BertCalm/xo-ox-claude-config/tree/main/skills/pilgrimage-tracker
Command: npx skills add https://github.com/BertCalm/xo-ox-claude-config --skill pilgrimage-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of lost context and fragmented progress in multi-session projects, ensuring that work continues seamlessly from where it left off.

Core Features & Use Cases

  • Persistent Campaign Tracking: Maintains a record of progress across multiple sessions for projects like engine retreats or build journeys.
  • Contextual Carry-Forward: Carries forward decisions, blockers, and phase completion status to the next session.
  • Use Case: When working on a multi-week "engine retreat," this skill ensures that each day's session starts with a clear understanding of what was accomplished the previous day and what needs to be done next.

Quick Start

Use the pilgrimage tracker to resume the 'Guru Bin' campaign.

Frequently Asked Questions about pilgrimage-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track multi-session project progress without losing context?

Multi-session project progress tracking maintains canonical state and carries context forward across sessions. It logs phase completion, key decisions, and blockers to ensure work resumes seamlessly from where it left off.

Can I maintain campaign tracking state for a multi-week build journey?

Campaign tracking for build journeys uses persistent campaign files to store state. This allows multi-week projects to maintain a continuous record of progress, decisions, and blockers across separate working sessions.

How does context carry-forward work for multi-session project management?

Context carry-forward works by storing canonical state in campaign files. When resuming a session, it retrieves previous phase completion status, logged decisions, and active blockers to provide immediate continuity.

What's the best way to resume project management for an engine retreat?

Resuming project management for an engine retreat requires loading the stored campaign state. This retrieves the previous session's context, allowing you to immediately continue the build journey with clear next steps.

Do I need any dependencies to use persistent session management for campaigns?

Persistent session management for campaigns requires no external dependencies. It operates independently, utilizing internal campaign files for state management and contextual carry-forward across sessions.

When should I not use a pilgrimage tracker for progress tracking?

Progress tracking via pilgrimage tracker is not suited for single-session tasks or projects requiring no historical context. It is designed specifically for persistent, multi-session campaigns needing phase and blocker continuity.