writing

name	writing
description	Writing projects — research one-pagers, technical documents, and reports. All output goes in the `writing/` folder. Triggers on "write a one-pager", "start a writing project", "write a report", or "research and write".

Writing

Routing

Match the user's request to one of these workflows:

• "write a one-pager" / "start a writing project" / "write about..." → One-Pager Workflow
• "research..." / "investigate..." → Research Workflow (findings only, no final doc)
• "generate docx" / "export to docx" → Docx Export Workflow

---

General Rules

• All writing project outputs go in the writing/ folder
• Each project gets its own subfolder (e.g., writing/my-research/)
• You can read any folder but never write outside of writing/
• Never change branches in other repos — other agents may be working in them simultaneously
• Write intermediate summaries of findings in markdown files with cited sources
• Maintain a changelog.md with timestamps summarizing work progress
• If you need to clone repos for reading, place them in the project subfolder
• Don't clone repos that already exist

Project Structure

writing/
  <project-name>/
    changelog.md                # Work log with timestamps
    NN-topic.md                 # Numbered research findings
    <project-name>.md           # Final document (one-pager, report, etc.)

---

One-Pager Workflow

Steps

1. Create project folder at writing/<project-name>/
2. Research — gather information, write numbered findings files (01-topic.md, 02-topic.md, etc.) with cited sources
3. Draft — write the one-pager in writing/<project-name>/<project-name>.md using the template below
4. Log progress — update changelog.md after each major step

One-Pager Template

Use the template in skills/writing/assets/one-pager-template.md as a starting point. The structure is:

• Summary with recommendations (note one-way/two-way door decisions)
• Overview — concise, non-redundant with summary intro
• Body sections as needed
• Appendices for supporting detail (start on new page)
• References in IEEE style
• Revision History table
• Time spent footnote on final page

Style

• Keep the main body to 1-2 pages; move supporting detail to appendices
• Lead with a compelling intro paragraph in the Summary that frames the problem and opportunity concisely
• Recommendations should be on separate lines (not bullet points)
• The "Overview" section should be concise and non-redundant with the summary intro
• Prioritize readability: be convincing and clear, not exhaustive
• Figures referenced as "Figure 1", tables as "Table 1"
• Use ragged right alignment, no full justification

---

Research Workflow

1. Create project folder at writing/<project-name>/
2. Research — write numbered findings files with cited sources
3. Log progress — update changelog.md after each step
4. No final document — research only

---

Docx Export Workflow

Generate a .docx from a writing project's markdown file. This workflow uses the docx skill — invoke /docx or say "export to docx" to trigger it.

See the docx skill for full pipeline details (scripts, reference template setup, and post-processing).

Quick Reference

1. Run convert_refs_to_footnotes.py on the markdown → generates .docx via pandoc
2. Run fix_docx.py on the .docx → fixes formatting (headings, borders, page breaks)
3. Copy the final .docx to docs/ (symlinked to Google Drive)