audit-copywriter

Audit arc-preservation alignment between cogni-narrative and cogni-copywriting pipelines.

12|2|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/cogni-work/insight-wave --skill audit-copywriter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-copywriter
Source: https://github.com/cogni-work/insight-wave/tree/main/cogni-copywriting/skills/audit-copywriter
Command: npx skills add https://github.com/cogni-work/insight-wave --skill audit-copywriter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit cogni-copywriting's arc-preservation references against cogni-narrative's upstream arc definitions. Detects missing arcs, heading mismatches, word target drift, technique inconsistencies, localization gaps, and validation rule conflicts (like H2 count rules that would reject valid narratives). Use whenever the user mentions "audit arc sync", "check copywriter arcs", "narrative drift check", "compare arcs upstream", "are arcs up to date", "arc contract check", "will copywriter break on this arc", or any question about whether cogni-copywriting references match cogni-narrative definitions — even if they don't say "audit" explicitly. Also use proactively after cogni-narrative version bumps.

Core Features & Use Cases

  • Surface drift: detect arc-definition drift between upstream and downstream references.
  • Validation and compliance: verify headings, word targets, techniques, and localization align with upstream contracts.
  • Remediation guidance: generate actionable fixes and improved diagnostics for narrative-copywriting cohesion.
  • Use Case: When upstream arcs are updated, run this audit to surface mismatches and prevent polish-time rejections.

Quick Start

Run the audit against the repository's arc definitions and preservation rules to surface drift and generate a remediation plan.

Frequently Asked Questions about audit-copywriter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect narrative drift between upstream story arcs and downstream copywriting?

To detect narrative drift, audit arc-preservation alignment by comparing upstream narrative arc definitions against downstream copywriting references. This surfaces missing arcs, heading mismatches, word target drift, and technique inconsistencies across multi-arc project pipelines.

What causes copywriting validation rules to reject valid upstream narratives?

Validation rule conflicts, such as rigid H2 count rules, can reject valid narratives when downstream copywriting contracts fall out of sync. Auditing arc-preservation alignment identifies these rule conflicts and enforces compliance with upstream definitions.

How do I check for localization gaps and missing arcs in a multi-arc copywriting project?

Check for localization gaps and missing arcs by running an audit against dedicated upstream and downstream contract files. The audit cross-references frontmatter metadata and per-arc sections to verify that all defined arcs are present and localized.

When should I run an arc contract check on my narrative and copywriting pipelines?

Run an arc contract check proactively whenever upstream cogni-narrative definitions receive version bumps. This prevents polish-time rejections by surfacing word target drift, heading mismatches, and validation conflicts before copywriting begins.

Can I generate remediation guidance for heading mismatches and word target drift?

Yes, auditing arc-preservation alignment generates actionable fixes and improved diagnostics for narrative-copywriting cohesion. It identifies heading mismatches and word target drift, then outputs a remediation plan to realign downstream references.