How do I install the Post Write Drift Check skill?

Run npx skillmds@latest add yogsoth-ai/post-write-drift-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Post Write Drift Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Post Write Drift Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Post Write Drift Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Post Write Drift Check?

yogsoth-ai (@yogsoth-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Post Write Drift Check by yogsoth-ai

Name: Post Write Drift Check
Author: yogsoth-ai

Post Write Drift Check

Back-summarize the finished article draft and diff it against the already-verified bundle to catch drift (new errors or omissions introduced during drafting/styling) — even when the bundle itself already passed precision and recall checks. Use this immediately after any drafting sop (section-drafting-with-style, or any future content-faithful/hybrid drafting sop) produces an article_draft, before considering the article final. Shared by both quality-assurance and audience-first-writing.

yogsoth-ai 9730587 2 files · 4.1 KB Updated Sep 17, 2026

File contents

Post-Write Drift Check

Back-summarization diff: read the finished article fresh, compare against the bundle, flag drift. Catches errors introduced by rewriting/styling — style is exactly where new commission/omission errors sneak in, per the design spec's ideation findings (§2 point 3).

Execution

Subagent — spawned via subagent-spawning/spawn-agent skill.

Why Subagent

The back-summarization step needs a reading of the article that isn't anchored to having just written it — the same "fresh eyes" principle as the pre-write checks, applied post-draft.

Shared Across Strategies

Defined here under quality-assurance (this task), but invoked by audience-first-writing's drafting tactics too (spec §7's "Cross-strategy dependency", §8's shared-sops table) — not redefined there, just referenced.

Scope Boundary

This sop diffs article-vs-bundle only. It does NOT re-query the raw paper — that would duplicate pre-write-precision-check's job. If the bundle itself turns out to be wrong, that should already have been caught before drafting ever started; this check assumes the bundle was correct and only asks whether the draft stayed faithful to it.

Available SOPs

Optional, no fixed order; the final leaf is always a sop.

SOP	When to use
spawn-agent	Spawn a customized CC subagent with full MCP tool access.

---name: post-write-drift-checkdescription: Back-summarize the finished article draft and diff it against the already-verified bundle to catch drift (new errors or omissions introduced during drafting/styling) — even when the bundle itself already passed precision and recall checks. Use this immediately after any drafting sop (section-drafting-with-style, or any future content-faithful/hybrid drafting sop) produces an article_draft, before considering the article final. Shared by both quality-assurance and audience-first-writing.---# Post-Write Drift CheckBack-summarization diff: read the finished article fresh, compare against the bundle, flag drift. Catches errors introduced by rewriting/styling — style is exactly where new commission/omission errors sneak in, per the design spec's ideation findings (§2 point 3).## ExecutionSubagent — spawned via subagent-spawning/spawn-agent skill.## Why SubagentThe back-summarization step needs a reading of the article that isn't anchored to having just written it — the same "fresh eyes" principle as the pre-write checks, applied post-draft.## Shared Across StrategiesDefined here under quality-assurance (this task), but invoked by `audience-first-writing`'s drafting tactics too (spec §7's "Cross-strategy dependency", §8's shared-sops table) — not redefined there, just referenced.## Scope BoundaryThis sop diffs article-vs-bundle only. It does NOT re-query the raw paper — that would duplicate pre-write-precision-check's job. If the bundle itself turns out to be wrong, that should already have been caught before drafting ever started; this check assumes the bundle was correct and only asks whether the draft stayed faithful to it.## Available SOPsOptional, no fixed order; the final leaf is always a sop.| SOP | When to use || --- | --- || spawn-agent | Spawn a customized CC subagent with full MCP tool access. |

Frequently asked questions