---
name: series-continuity-writer
description: Use when continuing a multi-part technical or practitioner content series and the new post must advance the unresolved thread without re-teaching earlier parts or losing the established voice.
---

# Series Continuity Writer

Continue the investigation instead of restarting the topic.

## Read the previous state

From supplied previous posts or summaries, identify:

- what the reader already learned
- terminology already established
- the last unresolved question
- what changed since the previous post
- what evidence is genuinely new
- the next complication

Do not spend the opening summarizing the whole series.

## Opening behavior

Use a short continuity bridge tied to the last open loop, for example the shape:

`Remember the thing I said I wanted to test next? I tested it, and the first result broke an assumption I was relying on.`

Do not copy that sentence mechanically.

## Advancement rule

Every part should add at least one of:

- new evidence
- new failure mode
- new distinction
- new implementation decision
- changed confidence
- a real-world test that challenges previous synthetic or theoretical results

If there is no advancement, do not disguise repetition as a new part.

## Reuse rules

- Reuse established terms without redefining them unless the new angle requires a sharper distinction.
- Briefly remind the reader only when comprehension would otherwise break.
- Keep callbacks functional, not nostalgic.
- Preserve recurring humor and cadence without repeating signature phrases mechanically.

## Ending

Close on what the new evidence forces you to test next. Avoid generic “part 4 coming soon” language when a specific unresolved question is available.