new-md-tg-exchange

---
name: new-md-tg-exchange
description: Create the verbatim and claude markdown file pair for a paper section using new-md
---

# new-md-tg-exchange — Create the verbatim + claude file pair for a section

## Arguments

The user provides a `filename_substring`:
- `/new-md-tg-exchange introduction` → creates `introduction_verbatim.md` and `introduction_claude.md`
- `/new-md-tg-exchange methods` → creates `methods_verbatim.md` and `methods_claude.md`
- `/new-md-tg-exchange` → no substring provided, ask user

## Behavior

### Step 1 — Determine `filename_substring`

- If the user provides a clear `filename_substring`, use it.
- If not provided, ask: "What topic or section? This will be used for the filename (e.g., `introduction`, `methods`, `results`)."
- If the user gives a vague response (e.g., "the next part", "that thing we discussed"), choose an appropriate `filename_substring` based on conversation context.

### Step 2 — Create both files

Invoke `/new-md` twice:
1. `/new-md {filename_substring}_verbatim` → creates `{filename_substring}_verbatim.md` in project root
2. `/new-md {filename_substring}_claude` → creates `{filename_substring}_claude.md` in project root

Both files are always placed in the project root. Never place them in subfolders.

If either file already exists, `/new-md` will report that and stop for that file. Do not overwrite.

### Step 3 — Confirm

```
Created pair for "{filename_substring}":
- {filename_substring}_verbatim.md
- {filename_substring}_claude.md
```

## Notes

- This skill composes `/new-md` — it does not create files directly.
- Files are always empty (no boilerplate). Content gets populated later via `/tg-exchange-loop-extract` or `/tg-exchange-loop-slice-extract`.
- Use underscores for multi-word names (e.g., `literature_review`, not `literature-review`), matching `/new-md` convention.