cogni-copywriting

Polish markdown documents for executive readability using McKinsey Pyramid Principle, or polish text fields inside JSON files via the copy-json adapter

Review a document through parallel stakeholder persona simulation with Q&A feedback and automatic improvement

Polish markdown documents for executive readability using McKinsey Pyramid Principle and messaging frameworks.

Review documents through parallel stakeholder persona Q&A simulation with synthesized feedback.

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.

Adapter skill that polishes text fields inside JSON files by extracting them, delegating to the copywriter skill for polishing, and writing the polished text back. Use when the user wants to polish, improve, or copywrite text inside a JSON file — plugin descriptions, IS/DOES/MEANS propositions, category names, claim statements, or any string fields in structured JSON data. Triggers include "polish JSON", "copywrite marketplace.json", "improve descriptions in plugin.json", "polish fields in JSON", or any /copywrite invocation targeting a .json file with --fields.

This skill should be used when the user wants to review a document from different stakeholder perspectives, simulate how different audiences would read a document, or get multi-perspective feedback before distribution. Common triggers include "review document as stakeholder", "stakeholder review", "reader review", "read as executive", "review from technical perspective", "does this document work for [audience]", "get feedback on this document", "what would [role] think of this", "check if this is ready for stakeholders", or "simulate different readers".

Polish, rewrite, or create business documents (memos, briefs, reports, proposals, one-pagers, executive summaries, emails, blog posts, business letters) using professional messaging frameworks (BLUF, McKinsey Pyramid, SCQA, STAR, PSB, FAB) and persuasion techniques (number plays, power words, rhetorical devices). Use this skill when the user asks to polish a document, improve writing, make something more readable, restructure a brief, apply BLUF or Pyramid Principle, rewrite for executives, strengthen messaging, create a proposal, write a one-pager, clean up a report, or apply any named messaging framework. Also handles German documents (Wolf Schneider style), arc-aware narrative polishing (cogni-narrative arcs with arc_id), and IS/DOES/MEANS sales messaging. Even simple requests like "make this better" about a markdown file should trigger this skill.