syft-storyline-backfill

Syft Storyline Backfill

Use this skill after a storyline tree already exists and the user wants one branch, one trunk, or the full tree extended with older or missing events.

Inputs

Prefer to have:

• an existing storyline tree markdown file
• optional html or notes version of the same tree
• profiles/following_topics.md
• profiles/profile_summary.md
• optional guidance rules

What this skill produces

Create:

• storylines/storyline_backfill_<date>.md
• optionally an updated storyline tree markdown file
• optionally an updated storyline tree html file
• optionally an updated storyline tree json file
• optionally storylines/backfill_keyword_strategy_<date>.md

Important:

• storyline_backfill_<date>.md is a working-facing explanation artifact
• the updated storyline tree files are user-facing final artifacts

Do not confuse the two. Working-note language is acceptable in the backfill memo. It is not acceptable in the final tree outputs.

Workflow

1. Choose the target. The user may specify:

   • one branch
   • one trunk
   • all branches

2. Restate the target meaning in one sentence before searching. Do not search from labels alone. If the branch is a hobby or travel line, restate the branch logic precisely.

   Examples:

   • not just Fate

   • but Fate official merch / collab / event cadence

   • not just Japanese onsen

   • but high-quality scenic ryokan / seasonal opening / local cuisine line

3. Use the retrieval ladder. Before broad search, check whether the branch maps to a followed topic id. Default order:

   1. existing known events
   2. topic top via syft top --topic-id <TOPIC_ID> --days <N> --limit 20 --rich
   3. targeted syft search

   Topic top should be the normal second step because it often returns higher-quality branch-local material than free-text search. Start with limit 20. In most branches, the first 20 topic-local items are enough to show whether the branch can be filled cleanly. Only widen the limit if the branch remains obviously thin after triage.