Format Converter Brief
What This Skill Does
Produces a clear, step-by-step brief explaining exactly how to convert a finished article or document from one format (Word, plain text, InDesign export) into a specified target format (Markdown, HTML, or structured plain text), preserving all editorial elements correctly.
When To Use This Skill
- You need to move a finished article from a Word document into a CMS that uses Markdown or HTML
- A web editor has sent you a piece that needs to be posted to a platform with specific markup requirements
- You are handing off formatted copy to a developer or digital producer and need to give them precise conversion instructions
- You are preparing archival versions of published articles in multiple formats
What You Need To Provide
Required: The source format (e.g., Word .docx, InDesign exported .txt, plain email text) and the target format (Markdown, HTML, or structured plain text). A description or paste of the article's structural elements — headings, subheadings, pull quotes, captions, byline, bullet lists, embedded links, footnotes.
Optional: The name or type of CMS the output will be pasted into (WordPress, Arc, Contentful, Ghost). Any house style rules that affect markup — for example, whether <h2> or ## is used for section heads, or whether links open in new tabs.
How the Assistant Approaches This
- Identifies every structural element in the source document — body paragraphs, headlines, subheadings, captions, bylines, pull quotes, bullet lists, links, footnotes — and maps each to its correct equivalent in the target format.
- Flags any elements that have no clean equivalent in the target format (for example, multi-column layouts or decorated drop caps in Word have no Markdown equivalent) and recommends a practical workaround.
- Produces a brief structured as a numbered conversion checklist: one instruction per element type, written in plain language so that any editor — not just a developer — can follow it without ambiguity.
Output Format
A numbered conversion checklist, typically 8–15 items. Each item names the source element, states the target markup or convention, and includes a short example showing before and after. Ends with a short "Watch out for" section listing two or three common conversion errors specific to this format pair. Plain, professional language — no technical jargon beyond the markup itself.
Quality Criteria
Example
Input
Source format: Word document (.docx)
Target format: Markdown (for Ghost CMS)
Article structure:
- Headline in Title style
- Byline below headline (Author Name, Date)
- Three section subheadings in Heading 2 style
- Body paragraphs in Normal style
- One pull quote (italicised, indented in Word)
- One bulleted list (Word auto-bullets)
- Three hyperlinks embedded in body text
- Two image captions below photos (Caption style in Word)
- One author bio paragraph at the end (italicised Normal)
No footnotes. No footnotes. CMS is Ghost 5. Links should open in the same tab.
Output
Format Conversion Brief: Word → Markdown (Ghost 5)
Source: Word .docx
Target: Markdown for Ghost 5 CMS
Prepared for: Editorial handoff
Conversion Checklist
Headline (Title style → # heading)
Word: Urban Heat: How Cities Are Rewriting the Climate Rulebook
Markdown: # Urban Heat: How Cities Are Rewriting the Climate Rulebook
Paste this as the first line of your Markdown file. Ghost will use it as the article title.
Byline (below headline → plain text block)
Word has no standard Markdown equivalent for bylines. In Ghost, enter the author in the post settings panel — do not include it in the body text. The date is set in the post settings as well. Delete the byline line from the Markdown body entirely.
Section subheadings (Heading 2 → ##)
Word: subheading in Heading 2 style
Markdown: ## Your Subheading Here
Apply this to all three subheadings. Use ## only — do not use ### unless you have a third level of heading in the original.
Body paragraphs (Normal style → plain paragraphs)
No markup needed. Paste body text as-is, with a blank line between each paragraph. Remove any double spaces after full stops — use single spaces throughout.
Pull quote (italicised indent → blockquote)
Word: indented italicised paragraph
Markdown: > "No city has solved this alone — the answers are regional or they are nothing."
Place the > symbol at the start of the line. Do not use quotation marks unless they appear in the original text.
Bulleted list (Word auto-bullets → Markdown list)
Word: auto-formatted bullet points
Markdown:
- First item
- Second item
- Third item
Use a hyphen and a space before each item. Remove any tab indentation Word may have added.
Hyperlinks (embedded links → inline Markdown links)
Word: underlined blue text with a URL attached
Markdown: [link text](https://example.com)
Example: [a 2023 IPCC report](https://ipcc.ch/report/ar6) — links open in the same tab by default in Ghost Markdown, which matches your requirement. Do not add {:target="_blank"}.
Image captions (Caption style → italic text below image card)
In Ghost, captions are entered directly in the image card after uploading the photo — not in the Markdown body. Remove caption text from the Markdown file. Keep the captions in a separate notes document to paste into Ghost after upload.
Markdown caption format (if your Ghost theme uses it): *A caption describing the image.*
Author bio (italicised paragraph → italic Markdown)
Word: italicised Normal paragraph at article end
Markdown: *Firstname Lastname is a journalist covering urban planning and climate adaptation. They are based in [City].*
Wrap the entire paragraph in single asterisks. Place it after a horizontal rule: --- on its own line, then the bio.
Watch Out For
- Smart quotes. Word uses curly quotation marks (
" "). Some Markdown parsers handle these fine; others display them as garbled characters. If you see strange symbols in Ghost preview, do a find-and-replace: swap " for " and ' for ' throughout.
- Hidden line breaks. Word sometimes inserts a soft return (Shift+Enter) inside paragraphs. These paste as
<br> tags in some editors, breaking your paragraph spacing. Check that each paragraph is separated by a full blank line, not a single line break.
- Table formatting. If the article contains any tables not mentioned above, contact the digital producer before converting — Word tables require manual Markdown table markup and are not covered by this brief.
Known Limitations
- This skill produces a conversion brief — instructions for a human to follow — not an automated conversion. It will not paste or reformat the article itself; that step remains with the editor.
- Format briefs are specific to the source/target pair. If your CMS uses a custom markup dialect (Arc XP, Brightspot), the standard Markdown instructions may need adjustment — mention your CMS when requesting the brief.
- Complex Word documents with tracked changes, comments, or revision marks should have those resolved before conversion; this skill assumes a clean final draft.
Related Skills
1---2name: format-converter-brief3description: Produces a clear, step-by-step brief explaining exactly how to convert a finished article or document from one format (Word, plain text, InDesign export) into a specified target format (Markdown, HTML, or structured plain text), preserving all editorial elements correctly.4---5# Format Converter Brief67## What This Skill Does8Produces a clear, step-by-step brief explaining exactly how to convert a finished article or document from one format (Word, plain text, InDesign export) into a specified target format (Markdown, HTML, or structured plain text), preserving all editorial elements correctly.910## When To Use This Skill11- You need to move a finished article from a Word document into a CMS that uses Markdown or HTML12- A web editor has sent you a piece that needs to be posted to a platform with specific markup requirements13- You are handing off formatted copy to a developer or digital producer and need to give them precise conversion instructions14- You are preparing archival versions of published articles in multiple formats1516## What You Need To Provide17**Required:** The source format (e.g., Word .docx, InDesign exported .txt, plain email text) and the target format (Markdown, HTML, or structured plain text). A description or paste of the article's structural elements — headings, subheadings, pull quotes, captions, byline, bullet lists, embedded links, footnotes.1819**Optional:** The name or type of CMS the output will be pasted into (WordPress, Arc, Contentful, Ghost). Any house style rules that affect markup — for example, whether `<h2>` or `##` is used for section heads, or whether links open in new tabs.2021## How the Assistant Approaches This221. Identifies every structural element in the source document — body paragraphs, headlines, subheadings, captions, bylines, pull quotes, bullet lists, links, footnotes — and maps each to its correct equivalent in the target format.232. Flags any elements that have no clean equivalent in the target format (for example, multi-column layouts or decorated drop caps in Word have no Markdown equivalent) and recommends a practical workaround.243. Produces a brief structured as a numbered conversion checklist: one instruction per element type, written in plain language so that any editor — not just a developer — can follow it without ambiguity.2526## Output Format27A numbered conversion checklist, typically 8–15 items. Each item names the source element, states the target markup or convention, and includes a short example showing before and after. Ends with a short "Watch out for" section listing two or three common conversion errors specific to this format pair. Plain, professional language — no technical jargon beyond the markup itself.2829## Quality Criteria30- [ ] Every structural element mentioned in the source description has a corresponding instruction31- [ ] Each instruction includes a concrete before/after example, not just a rule statement32- [ ] The "Watch out for" section is specific to the source/target pair, not generic advice33- [ ] No instruction requires the editor to know how to code — only to copy and paste markup34- [ ] Any element that cannot convert cleanly is flagged with a practical workaround3536## Example3738### Input39Source format: Word document (.docx)40Target format: Markdown (for Ghost CMS)4142Article structure:43- Headline in Title style44- Byline below headline (Author Name, Date)45- Three section subheadings in Heading 2 style46- Body paragraphs in Normal style47- One pull quote (italicised, indented in Word)48- One bulleted list (Word auto-bullets)49- Three hyperlinks embedded in body text50- Two image captions below photos (Caption style in Word)51- One author bio paragraph at the end (italicised Normal)5253No footnotes. No footnotes. CMS is Ghost 5. Links should open in the same tab.5455### Output5657## Format Conversion Brief: Word → Markdown (Ghost 5)5859**Source:** Word .docx60**Target:** Markdown for Ghost 5 CMS61**Prepared for:** Editorial handoff6263---6465### Conversion Checklist66671. **Headline (Title style → `#` heading)**68 Word: `Urban Heat: How Cities Are Rewriting the Climate Rulebook`69 Markdown: `# Urban Heat: How Cities Are Rewriting the Climate Rulebook`70 Paste this as the first line of your Markdown file. Ghost will use it as the article title.71722. **Byline (below headline → plain text block)**73 Word has no standard Markdown equivalent for bylines. In Ghost, enter the author in the post settings panel — do not include it in the body text. The date is set in the post settings as well. Delete the byline line from the Markdown body entirely.74753. **Section subheadings (Heading 2 → `##`)**76 Word: subheading in Heading 2 style77 Markdown: `## Your Subheading Here`78 Apply this to all three subheadings. Use `##` only — do not use `###` unless you have a third level of heading in the original.79804. **Body paragraphs (Normal style → plain paragraphs)**81 No markup needed. Paste body text as-is, with a blank line between each paragraph. Remove any double spaces after full stops — use single spaces throughout.82835. **Pull quote (italicised indent → blockquote)**84 Word: indented italicised paragraph85 Markdown: `> "No city has solved this alone — the answers are regional or they are nothing."`86 Place the `>` symbol at the start of the line. Do not use quotation marks unless they appear in the original text.87886. **Bulleted list (Word auto-bullets → Markdown list)**89 Word: auto-formatted bullet points90 Markdown:91 ```92 - First item93 - Second item94 - Third item95 ```96 Use a hyphen and a space before each item. Remove any tab indentation Word may have added.97987. **Hyperlinks (embedded links → inline Markdown links)**99 Word: underlined blue text with a URL attached100 Markdown: `[link text](https://example.com)`101 Example: `[a 2023 IPCC report](https://ipcc.ch/report/ar6)` — links open in the same tab by default in Ghost Markdown, which matches your requirement. Do not add `{:target="_blank"}`.1021038. **Image captions (Caption style → italic text below image card)**104 In Ghost, captions are entered directly in the image card after uploading the photo — not in the Markdown body. Remove caption text from the Markdown file. Keep the captions in a separate notes document to paste into Ghost after upload.105 Markdown caption format (if your Ghost theme uses it): `*A caption describing the image.*`1061079. **Author bio (italicised paragraph → italic Markdown)**108 Word: italicised Normal paragraph at article end109 Markdown: `*Firstname Lastname is a journalist covering urban planning and climate adaptation. They are based in [City].*`110 Wrap the entire paragraph in single asterisks. Place it after a horizontal rule: `---` on its own line, then the bio.111112---113114### Watch Out For115116- **Smart quotes.** Word uses curly quotation marks (`"` `"`). Some Markdown parsers handle these fine; others display them as garbled characters. If you see strange symbols in Ghost preview, do a find-and-replace: swap `"` for `"` and `'` for `'` throughout.117- **Hidden line breaks.** Word sometimes inserts a soft return (Shift+Enter) inside paragraphs. These paste as `<br>` tags in some editors, breaking your paragraph spacing. Check that each paragraph is separated by a full blank line, not a single line break.118- **Table formatting.** If the article contains any tables not mentioned above, contact the digital producer before converting — Word tables require manual Markdown table markup and are not covered by this brief.119120## Known Limitations121- This skill produces a conversion brief — instructions for a human to follow — not an automated conversion. It will not paste or reformat the article itself; that step remains with the editor.122- Format briefs are specific to the source/target pair. If your CMS uses a custom markup dialect (Arc XP, Brightspot), the standard Markdown instructions may need adjustment — mention your CMS when requesting the brief.123- Complex Word documents with tracked changes, comments, or revision marks should have those resolved before conversion; this skill assumes a clean final draft.124125## Related Skills126- [print-web-reformatter](../print-web-reformatter/SKILL.md)127- [layout-placement-advisor](../layout-placement-advisor/SKILL.md)