@hanna84/mcp-writing 3.2.1 → 3.3.1

package/CHANGELOG.md

@@ -4,11 +4,31 @@ All notable changes to this project will be documented in this file. Dates are d
 
 Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
 
+#### [v3.3.1](https://github.com/hannasdev/mcp-writing.git
+/compare/v3.3.0...v3.3.1)
+
+- fix(review-comments): enforce command-specific flags and add failure-path tests [`#174`](https://github.com/hannasdev/mcp-writing.git
+/pull/174)
+
+#### [v3.3.0](https://github.com/hannasdev/mcp-writing.git
+/compare/v3.2.1...v3.3.0)
+
+> 3 May 2026
+
+- feat(styleguide): formalize review mode output contract [`#173`](https://github.com/hannasdev/mcp-writing.git
+/pull/173)
+- Release 3.3.0 [`233f471`](https://github.com/hannasdev/mcp-writing.git
+/commit/233f471979802dda5d226a94bb03ff01a08dc819)
+
 #### [v3.2.1](https://github.com/hannasdev/mcp-writing.git
 /compare/v3.2.0...v3.2.1)
 
+> 3 May 2026
+
 - docs(skills): add review comment resolution workflow [`#172`](https://github.com/hannasdev/mcp-writing.git
 /pull/172)
+- Release 3.2.1 [`a05a429`](https://github.com/hannasdev/mcp-writing.git
+/commit/a05a4291aaebdb243999904600ea82a0fff154b6)
 
 #### [v3.2.0](https://github.com/hannasdev/mcp-writing.git
 /compare/v3.1.4...v3.2.0)

package/README.md

@@ -22,8 +22,9 @@ Instead of feeding an entire manuscript to an AI and hoping it fits in the conte
 
 **Current status:**
 - **Core platform complete:** Metadata-first analysis, sidecar-backed metadata maintenance, AI-assisted prose editing with confirmation + git history, review bundles, and Scrivener Direct extraction are all implemented.
-- **Active development:** OpenClaw integration and guideline generation are the current focus areas.
-- **Deferred backlog:** embeddings search and the reference document system are intentionally deferred for later exploration.
+- **Recently delivered:** Guideline generation is now delivered and tracked in done PRDs.
+- **Active development:** OpenClaw integration is the current focus area.
+- **Deferred backlog:** embeddings search is intentionally deferred for later exploration.
 
 ## Who it is for
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanna84/mcp-writing",
-  "version": "3.2.1",
+  "version": "3.3.1",
   "description": "MCP service for AI-assisted reasoning and editing on long-form fiction projects",
   "homepage": "https://hannasdev.github.io/mcp-writing/",
   "type": "module",

package/src/styleguide/prose-styleguide-skill.js

@@ -115,6 +115,36 @@ export function buildProseStyleguideSkill({ resolvedConfig, sources = [], projec
     "## Voice Notes",
     voiceNotes,
     "",
+    "## Review Mode Output Contract",
+    "",
+    "When providing critique, structure feedback as follows:",
+    "",
+    "### Structural Issues",
+    "- **Scene Purpose**: [Is it clear? Plot, character, theme, or tone.] If unclear, suggest clarification.",
+    "- **Transformation**: [What changes for the POV character or narrative?] If absent, note the stasis.",
+    "- **Non-Functional Sections**: [Does every paragraph advance purpose?] Flag bridging or exposition without tension.",
+    "",
+    "### Convention Drift",
+    "- **Tense**: [Is the tense consistent with config? Flag deviations as questions unless config allows intentional breaks.]",
+    "- **POV**: [Is POV maintained or intentionally shifted? Ask if shifts are deliberate.]",
+    "- **Quotation Style**: [Are dialogue markers consistent with config?]",
+    "- **Spelling/Abbreviations**: [Do these match configured rules?]",
+    "",
+    "### Prose Issues",
+    "- **Clarity**: [Is the sentence structure clear? Suggest specific revisions if muddy.]",
+    "- **Cadence**: [Do sentence rhythms support tone and pacing? Note if breaking is intentional vs. accidental.]",
+    "- **Specificity**: [Are abstractions replaced with concrete action? Flag generic beats.]",
+    "- **Dialogue**: [Does dialogue reflect character voice and cognition, or is it exposition?]",
+    "",
+    "### Sample Feedback Structure",
+    "```",
+    "**Structural Issues:** Scene purpose is [X shows Y to Z]; transformation is [character learns/fails/shifts]. ✓",
+    "",
+    "**Convention Drift:** Paragraph 2 shifts to a secondary character's perspective. Intentional multi-POV or head-hop?",
+    "",
+    "**Prose Issues:** [emotion stated directly] → Suggest concrete action (e.g., [physical reaction or movement]). Specificity: Use verbs and sensory detail to show emotion through action, not explanation. (✓ Shows a visible reaction.)",
+    "```",
+    "",
   ].join("\n");
 
   return {