seed-tracker

Record planted and retrieved campaign seeds in an append-only log.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/giodl73-repo/QUEST --skill seed-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seed-tracker
Source: https://github.com/giodl73-repo/QUEST/tree/main/.claude/skills/seed-tracker
Command: npx skills add https://github.com/giodl73-repo/QUEST --skill seed-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain an immutable, campaign-wide record of seeds planted and seeds retrieved, so no memory is lost between adventures and sessions.

Core Features & Use Cases

  • Append-only log at campaign/seed-tracker.md to record planted seeds with metadata (seed slug, type, planted-in, target, status) and retrieved seeds with retrieval context.
  • Orphan detection and hint-status tracking to surface seeds that require attention across campaigns.
  • Runs automatically during session-handoffs and can be invoked during adventure design to keep the campaign's memory synchronized.

Quick Start

Seed-tracker maintains the log at campaign/seed-tracker.md and records planted and retrieved seeds according to the documented format.

Frequently Asked Questions about seed-tracker

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

FAQPage Schema
What is an append-only log for tracking campaign seeds in adventure design?

An append-only log for campaign seeds is an immutable record at campaign/seed-tracker.md that tracks planted and retrieved seeds with metadata like seed slug, type, target, and status to prevent lost memory between sessions.

How do I track planted and retrieved seeds across multiple campaign sessions?

You track planted and retrieved seeds by recording structured entries in the campaign/seed-tracker.md log, which maintains seed metadata and retrieval context to ensure continuity across adventure sessions.

How does orphan detection work for unretrieved campaign seeds?

Orphan detection works by auto-generating alerts for seeds in the append-only log that remain unretrieved, surfacing hint-status tracking data so adventure designers can address unresolved seeds across campaigns.

Do I need a campaign spine before using a seed tracker for session handoffs?

Yes, you need a campaign spine and an initialized seed-tracker file before recording planted and retrieved seeds, as the tracker requires these prerequisites to structure entries and auto-generate orphan alerts.

Can I use seed tracking for adventure design outside of session handoffs?

Yes, you can invoke the seed tracker during adventure design to synchronize campaign memory, as it runs automatically during session handoffs and can be manually called to maintain the append-only log.

What limitations exist when managing campaign seeds with an append-only log?

The append-only log is limited to recording structured entries for planted and retrieved seeds at campaign/seed-tracker.md, meaning it cannot delete or modify past entries, only append new tracking data and orphan alerts.