horizon-track

Track long-horizon objectives across sessions with milestone checkpoints and drift detection.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill horizon-track
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: horizon-track
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-goals/skills/horizon-track
Command: npx skills add https://github.com/ruvnet/claude-flow --skill horizon-track

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running objectives that span multiple sessions, days, or weeks lose context between conversations, making it hard to know what was done, what remains, and whether the work is still on track. This Skill persists objective state, milestones, and session summaries in memory so progress survives across sessions.

Core Features & Use Cases

  • Milestone-based tracking: Define an objective with a target date and 3-7 milestones, each with completion criteria and status, stored in a persistent memory namespace.
  • Session check-in and check-out: Recall horizon state at session start, record accomplishments and blockers at session end, and keep per-session summaries keyed by date.
  • Drift detection: Flag when progress rate threatens the target date, scope grows beyond the original definition, or dependencies change.
  • Use Case: A multi-week migration project is split into milestones; at the start of each working session the agent recalls the horizon state, plans that session's contribution, and at the end records progress and learned patterns for future recall.

Quick Start

Ask the agent to start tracking a long-term objective named 'api-migration' with a target date and a set of milestones using the horizon-track skill.

Frequently Asked Questions about horizon-track

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

FAQPage Schema
How do I track a long-term project across multiple AI sessions?

Define the objective with a target date and 3-7 milestones, then store it in the horizons memory namespace. At each session start, retrieve the horizon state to review milestone status, and at session end record accomplishments and blockers.

How does drift detection work for long-running objectives?

Drift is flagged when the progress rate suggests the target date will be missed, scope grows beyond the original definition, dependencies change, or the approach needs fundamental rethinking. The agent surfaces these signals during session check-ins.

What data is stored for each tracked objective?

Each horizon stores the objective, creation and target dates, a milestone list with completion criteria and status, the current milestone, and a session log. Separate namespaces hold per-session summaries and learned patterns.

When should I not use cross-session objective tracking?

It is unnecessary for tasks completable in a single session, since the memory writes and check-in overhead add no value. Use it only for work spanning multiple sessions, days, or weeks.

Can milestone completion feed back into future work?

Yes. When a milestone completes, learned patterns are stored via the intelligence pattern-store tool, making insights from the horizon available for recall in later sessions and related objectives.