series-continuity-writer

Files (6)

• SKILL.md
• anti-patterns.md · references/
• pattern-engine.md · references/
• quality-rubric.md · references/
• routing-map.json · references/
• voice-profile.md · references/

SKILL.md (first lines)

# 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.

<!-- written-as-spoken:links start (generated by scripts/sync-links.mjs, do not edit by hand) -->

## Linked to Written as Spoken

This skill is a node in the Written as Spoken suite. The front door is `written-as-spoken` (`../../../../SKILL.md`), and the graph lives in `../../../../references/routing-map.json`.

When a request reaches this skill through `written-as-spoken`, Mamdouh's voice rules in `../../../../references/voice-dna.md` and `../../../../references/anti-slop.md` outrank this skill's own style defaults, the house profile is active, and facts come only from the user or from `story-researcher`.

Routes that pass through here:

- `series_episode` (next episode of a series or build log): after `workspace-recall`, hands off to `written-as-spoken`

Hand your output to the next node in the route. When this skill is the last node, return the result to `written-as-spoken` so the draft goes through `../../../../scripts/lint.mjs` before the user sees it. When this skill is called directly, outside the suite, ignore this block.

<!-- written-as-spoken:links end -->

From imMamdouhaboammar/written-as-spoken, MIT.

More from imMamdouhaboammar/written-as-spoken