{"id":18906,"plugin_id":"plugins_6a8d93a8e8388191a09e7b25ed86e3fb","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:15:01.773Z","digest":"7d442aaaa7ed7cad736b9a71092a727426df246877684d174ef27c75efd9cdc4","against":null,"payload":{"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.","included_files":[{"relative_path":"references/anti-patterns.md","size_in_bytes":1533},{"relative_path":"references/pattern-engine.md","size_in_bytes":2082},{"relative_path":"references/quality-rubric.md","size_in_bytes":992},{"relative_path":"references/routing-map.json","size_in_bytes":852},{"relative_path":"references/voice-profile.md","size_in_bytes":2615}],"name":"series-continuity-writer","skill_md_contents":"---\nname: series-continuity-writer\ndescription: 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.\n---\n\n# Series Continuity Writer\n\nContinue the investigation instead of restarting the topic.\n\n## Read the previous state\n\nFrom supplied previous posts or summaries, identify:\n\n- what the reader already learned\n- terminology already established\n- the last unresolved question\n- what changed since the previous post\n- what evidence is genuinely new\n- the next complication\n\nDo not spend the opening summarizing the whole series.\n\n## Opening behavior\n\nUse a short continuity bridge tied to the last open loop, for example the shape:\n\n`Remember the thing I said I wanted to test next? I tested it, and the first result broke an assumption I was relying on.`\n\nDo not copy that sentence mechanically.\n\n## Advancement rule\n\nEvery part should add at least one of:\n\n- new evidence\n- new failure mode\n- new distinction\n- new implementation decision\n- changed confidence\n- a real-world test that challenges previous synthetic or theoretical results\n\nIf there is no advancement, do not disguise repetition as a new part.\n\n## Reuse rules\n\n- Reuse established terms without redefining them unless the new angle requires a sharper distinction.\n- Briefly remind the reader only when comprehension would otherwise break.\n- Keep callbacks functional, not nostalgic.\n- Preserve recurring humor and cadence without repeating signature phrases mechanically.\n\n## Ending\n\nClose on what the new evidence forces you to test next. Avoid generic “part 4 coming soon” language when a specific unresolved question is available.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}