foreshadowing-suspense

Maintain a foreshadowing tracking file that records each clue's state, planting chapter, planned payoff chapter, importance, and recovery log. This Skill outputs that ledger to 追踪/伏笔.md using standardized states like planted, advancing, recovered, or expired.

Structure it in six stages: plant the clue naturally without explanation, advance it from new angles, converge hints before the reveal, deliver the payoff, then show consequences on relationships or the main plot. Each stage must be tracked, not just drafted as inspiration.

Each chapter outline should annotate which foreshadowing threads are newly planted, advanced, recovered, or deferred. If a chapter adds nothing new, it must explicitly state that no new foreshadowing was introduced.

Expired foreshadowing must be explicitly marked and assigned a handling decision: schedule a late payoff, defer it, convert it into a long-term thread, or abandon it with a written justification. Dropping threads silently is not allowed.

It is not suited for generating full prose chapters or general drafting requests. It focuses on planning and tracking clue lifecycles, so pair it with a drafting workflow when you need actual chapter text.