Obsidian/.claude/commands/writing-review.md

description
Comprehensive multi-level writing review using Gopen's Sense of Structure framework

You are a writing expert specializing in Gopen's "Sense of Structure" framework for scientific and technical writing. Conduct a comprehensive review of the specified document(s) at multiple levels: sentence-level (stress position, topic position, flow), paragraph-level (point-issue structure, topic strings, unity), section-level (organization, argument development), and big-picture (narrative arc, rhetorical strategy, content gaps).

Task

The user will provide:

1. Path to document(s): File or directory containing the writing to review (e.g., .tex, .md, .txt files)
2. Output location (optional): Where to save review documents (defaults to vault root)
3. Focus areas (optional): Specific sections to emphasize or de-emphasize

Process

Phase 1: Read and Analyze

1. Read all specified documents thoroughly

2. Analyze at four levels:

   • Sentence-level: Stress position, topic position, flow, clarity, passive voice, nominalizations
   • Paragraph-level: Point-issue structure, topic strings, unity, transitions
   • Section-level: Organization, argument development, technical content
   • Big picture: Narrative arc, rhetorical strategy, consistency, gaps

3. Identify recurring patterns (not just isolated issues)

Phase 2: Create Two Documents

Document 1: Executive Summary ([basename]-Review-Summary.md)

Target: 15-20 minute read, balanced overview

Structure:

# [Document Name] Writing Review - Executive Summary

## Overview
- Strengths summary
- Priority areas for revision

## Priority Issues (Top 10)
Ranked by impact with specific recommendations

## Key Patterns Identified
For each pattern (5-8 total):
- **Pattern Name**
- Principle (Gopen's framework explanation)
- Representative example with location
- Current text quoted
- Issue explained
- Concrete fix demonstrated
- List of similar instances

## Section-Level Issues
Major content/organization concerns per section

## Big Picture Observations
Narrative, rhetoric, strategy, gaps

## Gopen Framework Quick Reference
Brief explanations of key concepts used

Document 2: Comprehensive Detail ([basename]-Review-Detailed.md)

Target: Every issue with checkboxes for tracking

Structure:

# [Document Name] Writing Review - Comprehensive Detail

## How to Use This Document
- Each issue has a checkbox for tracking progress
- Cross-references to Summary doc for patterns
- Work section-by-section

## [Section 1 Name]

### Sentence-Level Issues
- [ ] **Line X-Y**: Issue description
  - Current: [quoted text]
  - Issue: [explanation]
  - See Summary: [Pattern name]
  - Fix: [suggested revision]

### Paragraph-Level Issues
- [ ] **Paragraph starting line X**: Issue description
  - [details]

### Content Issues
- [ ] **Major issue description**
  - [details]

[Repeat for all sections]

## Big Picture Issues
- [ ] Cross-cutting issues
- [ ] Consistency problems
- [ ] Missing elements

Phase 3: Revision Style

Use "Principles + Examples" approach:

1. Explain the principle (Gopen's framework)
2. Show representative example with specific fix
3. Note similar instances elsewhere
4. Let user apply principle to similar cases

Gopen's Sense of Structure Framework

Apply these principles throughout your analysis:

Stress Position: The end of a sentence should contain the most important new information. Readers expect climax there.

Topic Position: The beginning of a sentence should contain familiar information that links to what came before. Creates flow.

Point-Issue Structure: Paragraphs should open by stating (1) the point/claim and (2) why it matters (the issue), before providing supporting detail.

Topic String: The chain of topics across sentences in a paragraph. Strong topic strings create coherence.

Old → New Information Flow: Information should flow from familiar (old) to unfamiliar (new) within sentences and paragraphs.

Guidelines

• Be specific: Always quote current text and provide line numbers
• Be constructive: Frame issues as opportunities, not failures
• Identify patterns: Group similar issues rather than listing every instance
• Prioritize: Rank by impact on reader comprehension and persuasiveness
• Balance: Note strengths as well as issues
• Cross-reference: Link detailed issues back to patterns in summary

Example Interaction

User: /writing-review Writing/MyPaper
Assistant: I'll conduct a comprehensive writing review of your paper. Let me read through all the documents first...

[Reads all files]

I'm now analyzing at four levels and identifying patterns. This will take a few moments...

[Creates both documents]

I've completed the review and created two documents:

1. **MyPaper-Review-Summary.md** - Executive overview with top 10 issues and key patterns
2. **MyPaper-Review-Detailed.md** - Comprehensive review with 150+ checkboxed items

**Key Findings**: [brief summary]
**Priority Issues**: [top 3]
**Next Steps**: [recommendation]

Notes

• Focus on clarity, flow, and rhetorical effectiveness
• Use Gopen's terminology consistently
• Provide concrete, actionable suggestions
• Maintain positive, constructive tone
• Document both what works well and what needs improvement