horizon-track

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Horizon Track

长期目标跟踪(Horizon Track)

Track long-running objectives that span multiple sessions, days, or weeks.
跟踪跨越多个会话、数天或数周的长期运行目标。

When to use

使用场景

When an objective is too large for a single session — multi-week features, research programs, migration projects, or any work that requires persistent progress tracking across conversations.
当目标过于庞大,无法在单个会话内完成时——比如需要数周开发的功能、研究项目、迁移工程,或是任何需要在多轮对话中持续跟踪进度的工作。

Steps

操作步骤

  1. Initialize horizon — define the objective, target date, and 3-7 milestones
  2. Store horizon — call
    mcp__claude-flow__memory_store
    with namespace
    horizons
    and key
    horizon-[name]
    :
    json
    {
      "objective": "...",
      "created": "2026-04-28",
      "targetDate": "2026-05-15",
      "milestones": [
        {"id": "m1", "name": "...", "criteria": "...", "status": "pending"},
        {"id": "m2", "name": "...", "criteria": "...", "status": "pending"}
      ],
      "currentMilestone": "m1",
      "sessions": []
    }
  3. Session check-in — at the start of each session:
    • Recall horizon:
      mcp__claude-flow__memory_retrieve
      key
      horizon-[name]
      namespace
      horizons
    • Review milestone status
    • Assess drift (are we still on track?)
    • Plan this session's contribution
  4. Work and record — as work progresses:
    • Update milestone status
    • Record session summary
    • Store intermediate findings
  5. Session check-out — at the end of each session:
    • Update horizon state in memory
    • Record what was accomplished
    • Note blockers or scope changes
    • Estimate remaining effort
  6. Milestone completion — when a milestone is done:
    • Verify completion criteria met
    • Store learned patterns via
      mcp__claude-flow__hooks_intelligence_pattern-store
    • Advance to next milestone
  7. Drift detection — flag when:
    • Progress rate suggests target date will be missed
    • Scope has grown beyond original definition
    • Dependencies have changed
    • Approach needs fundamental rethinking
  1. 初始化长期目标 —— 定义目标内容、截止日期以及3-7个里程碑
  2. 存储长期目标 —— 调用
    mcp__claude-flow__memory_store
    ,命名空间为
    horizons
    ,键为
    horizon-[name]
    json
    {
      "objective": "...",
      "created": "2026-04-28",
      "targetDate": "2026-05-15",
      "milestones": [
        {"id": "m1", "name": "...", "criteria": "...", "status": "pending"},
        {"id": "m2", "name": "...", "criteria": "...", "status": "pending"}
      ],
      "currentMilestone": "m1",
      "sessions": []
    }
  3. 会话签到 —— 在每个会话开始时:
    • 调取长期目标:使用
      mcp__claude-flow__memory_retrieve
      获取命名空间
      horizons
      下键为
      horizon-[name]
      的内容
    • 查看里程碑状态
    • 评估偏差(我们是否仍在正轨上?)
    • 规划本次会话的任务贡献
  4. 工作与记录 —— 随着工作推进:
    • 更新里程碑状态
    • 记录会话摘要
    • 存储中间成果
  5. 会话签退 —— 在每个会话结束时:
    • 更新内存中的长期目标状态
    • 记录已完成的工作
    • 标注障碍或范围变更
    • 估算剩余工作量
  6. 里程碑完成 —— 当某个里程碑完成时:
    • 验证是否满足完成标准
    • 通过
      mcp__claude-flow__hooks_intelligence_pattern-store
      存储已总结的模式
    • 推进至下一个里程碑
  7. 偏差检测 —— 出现以下情况时发出警示:
    • 进度速率表明将无法按期完成
    • 范围超出最初定义
    • 依赖关系发生变化
    • 方法需要根本性调整

Memory namespaces

内存命名空间

  • horizons
    — active horizon definitions and state
  • horizon-sessions
    — per-session summaries keyed by
    [horizon]-[date]
  • horizon-learnings
    — patterns and insights discovered during the horizon
  • horizons
    —— 活跃的长期目标定义及状态
  • horizon-sessions
    —— 按
    [horizon]-[date]
    键存储的每会话摘要
  • horizon-learnings
    —— 在长期目标执行过程中发现的模式和见解