@damper/mcp 0.8.2 → 0.8.3

package/dist/index.js

@@ -269,8 +269,10 @@ server.registerTool('update_task', {
         'Useful for refining task details as you learn more about the work.',
     inputSchema: z.object({
         taskId: z.string().describe('Task ID'),
-        title: z.string().optional().describe('Task title'),
-        description: z.string().optional().describe('Task description (shown on public roadmap)'),
+        title: z.string().optional().describe('Task title (max 60 chars, sentence case, no trailing period). Verb prefix: ' +
+            'bug → "Fix …", feature → "Add …", improvement → "Improve …", task → "Set up …" / "Update …"'),
+        description: z.string().optional().describe('Task description (shown on public roadmap). Write for end users: 1-3 sentences on what changes and why it matters. ' +
+            'No code references, file paths, or jargon.'),
         implementationPlan: z.string().optional().describe('Implementation plan (markdown, internal only - never shown publicly)'),
         priority: z.enum(['high', 'medium', 'low']).nullable().optional().describe('Task priority'),
         effort: z.enum(['xs', 's', 'm', 'l', 'xl']).nullable().optional().describe('Estimated effort'),
@@ -351,9 +353,11 @@ server.registerTool('create_task', {
     title: 'Create Task',
     description: 'Create a new roadmap task. Use for importing from TODO files or creating work items.',
     inputSchema: z.object({
-        title: z.string().describe('Task title. Use verb prefix matching the type: ' +
-            'bug → "Fix …", feature → "Add …", improvement → "Improve …", task → "Set up …" / "Update …"'),
-        description: z.string().optional().describe('Task description (shown on public roadmap)'),
+        title: z.string().describe('Task title (max 60 chars, sentence case, no trailing period). Use verb prefix matching the type: ' +
+            'bug → "Fix …", feature → "Add …", improvement → "Improve …", task → "Set up …" / "Update …". ' +
+            'E.g., "Add dark mode support", "Fix login timeout on slow connections"'),
+        description: z.string().optional().describe('Task description (shown on public roadmap). Write for end users: 1-3 sentences on what changes and why it matters. ' +
+            'No code references, file paths, or jargon.'),
         type: z.enum(['bug', 'feature', 'improvement', 'task']).optional().describe('Task type (default: feature)'),
         status: z.enum(['planned', 'in_progress', 'done']).optional(),
         priority: z.enum(['high', 'medium', 'low']).optional().describe('Task priority'),
@@ -498,7 +502,7 @@ server.registerTool('add_commit', {
     inputSchema: z.object({
         taskId: z.string(),
         hash: z.string().describe('Commit hash (short or full)'),
-        message: z.string().describe('Commit message'),
+        message: z.string().describe('Commit message in conventional commits format: type(scope): description. E.g., "feat(auth): add OAuth login"'),
     }),
     outputSchema: z.object({
         taskId: z.string(),
@@ -524,7 +528,7 @@ server.registerTool('create_subtask', {
     description: 'Add a new subtask to a task. Useful for breaking down work into smaller steps.',
     inputSchema: z.object({
         taskId: z.string().describe('Task ID'),
-        title: z.string().describe('Subtask title'),
+        title: z.string().describe('Subtask title — short imperative phrase, e.g., "Add validation to login form"'),
     }),
     outputSchema: z.object({
         taskId: z.string(),
@@ -610,7 +614,7 @@ server.registerTool('complete_task', {
         'Returns documentation update suggestions.',
     inputSchema: z.object({
         taskId: z.string(),
-        summary: z.string().describe('Brief one-line summary of what was done'),
+        summary: z.string().describe('Brief one-line summary of what was done, written for end users. Focus on the outcome, not the implementation.'),
         commits: z.array(z.object({
             hash: z.string().describe('Commit hash (short or full)'),
             message: z.string().describe('Commit message'),
@@ -789,6 +793,44 @@ This project uses Damper MCP for task tracking. **You MUST follow this workflow.
 - If the project has a **completion checklist** (shown in \`start_task\` response), you MUST pass all items as \`confirmations\` when calling \`complete_task\`
 - If you learned something about the codebase, consider updating project context
 
+### Content Style Guide
+
+All content you generate — titles, descriptions, changelogs, notes — should follow these conventions for consistency.
+
+**Task titles:**
+- Imperative verb prefix matching type: bug → "Fix …", feature → "Add …", improvement → "Improve …", task → "Set up …" / "Update …"
+- Sentence case after verb (lowercase unless proper noun): "Add dark mode support"
+- Max 60 characters, no trailing period
+- Specific enough to understand without reading the description
+
+**Task descriptions** (shown on public roadmap):
+- Write for end users, not developers — no code references, file paths, or jargon
+- 1-3 sentences explaining what changes and why it matters to users
+- Focus on the user benefit, not implementation details
+
+**Subtask titles:**
+- Short imperative phrase: "Add validation to login form"
+- Specific enough to track independently
+
+**Changelog content:**
+- Write for users who want to know what changed and why they should care
+- Group entries by type: Added, Improved, Fixed
+- Each entry: 1-2 sentences focused on the user-visible change, not the technical approach
+- Use plain language — avoid technical jargon
+
+**Changelog summaries** (max 280 chars):
+- Lead with the most impactful change
+- Conversational tone suitable for social media or email subject
+
+**Commit messages:**
+- Conventional commits format: \`type(scope): description\`
+- Types: feat, fix, refactor, test, docs, chore, style, perf
+- Imperative mood: "add feature" not "added feature"
+
+**Notes:**
+- Prefix with category: "Decision: …", "Blocked: …", "Context: …"
+- Only log non-obvious decisions and blockers — skip routine progress
+
 ### Why This Matters
 - **Project context prevents mistakes** - Contains architecture decisions, gotchas, and patterns
 - Locked tasks block other agents from working on them
@@ -1731,10 +1773,12 @@ server.registerTool('create_changelog', {
         'Use this to create additional changelogs if needed.',
     inputSchema: z.object({
         title: z.string().describe('Changelog title (e.g., "v2.1.0" or "January 2025 Release")'),
-        content: z.string().optional().describe('Initial changelog content (markdown)'),
+        content: z.string().optional().describe('Changelog content (markdown). Write for users: group by Added/Improved/Fixed, ' +
+            '1-2 sentences per entry focused on user-visible changes. Avoid technical jargon.'),
         version: z.string().optional().describe('Version number'),
         date: z.string().optional().describe('Custom display date (ISO 8601). When set, used for sorting/display instead of publishedAt.'),
-        summary: z.string().max(280).optional().describe('Short summary for social sharing and email subject (max 280 chars)'),
+        summary: z.string().max(280).optional().describe('Short summary for social sharing and email subject (max 280 chars). ' +
+            'Lead with the most impactful change, conversational tone.'),
         status: z.enum(['draft', 'published']).optional().describe('Status (default: draft)'),
     }),
     outputSchema: z.object({
@@ -1766,10 +1810,12 @@ server.registerTool('update_changelog', {
     inputSchema: z.object({
         changelogId: z.string().describe('Changelog ID'),
         title: z.string().optional().describe('New title'),
-        content: z.string().optional().describe('New content (markdown)'),
+        content: z.string().optional().describe('New content (markdown). Write for users: group by Added/Improved/Fixed, ' +
+            '1-2 sentences per entry focused on user-visible changes. Avoid technical jargon.'),
         version: z.string().optional().describe('Version number'),
         date: z.string().optional().describe('Custom display date (ISO 8601). When set, used for sorting/display instead of publishedAt. Pass empty string to clear.'),
-        summary: z.string().max(280).optional().describe('Short summary for social sharing and email subject (max 280 chars)'),
+        summary: z.string().max(280).optional().describe('Short summary for social sharing and email subject (max 280 chars). ' +
+            'Lead with the most impactful change, conversational tone.'),
         status: z.enum(['draft', 'published']).optional().describe('Status'),
     }),
     outputSchema: z.object({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@damper/mcp",
-  "version": "0.8.2",
+  "version": "0.8.3",
   "description": "MCP server for Damper task management",
   "author": "Damper <hello@usedamper.com>",
   "repository": {