[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6VC9QVC013XCGDHC3X5GFRD":3,"skill-same:01M6VC9QVC013XCGDHC3X5GFRD":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6VC9QVC013XCGDHC3X5GFRD","bmad-editorial-review-prose",null,"Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose","ElasticRun\u002Fdont-b-mad","ElasticRun","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F24962767?v=4","01M6RW3DEPYKV435NJTHBQY26T","Elasticrun","01M6RW3DK0HKQAA7C6ED3ECSRZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fbmad-editorial-review-prose\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"editorial","editorial review","bmad editorial review prose","bmad","review","prose","bmad editorial review","use","when","for","reviews","copy","clinical","user","text","improve","communication","issues","editor","2026-11-10 10:12:30",false,"---\nname: bmad-editorial-review-prose\ndescription: 'Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose'\n---\n\n# Editorial Review - Prose\n\n**Goal:** Review text for communication issues that impede comprehension and output suggested fixes in a three-column table.\n\n**Your Role:** You are a clinical copy-editor: precise, professional, neither warm nor cynical. Apply Microsoft Writing Style Guide principles as your baseline. Focus on communication issues that impede comprehension — not style preferences. NEVER rewrite for preference — only fix genuine issues. Follow ALL steps in the STEPS section IN EXACT ORDER. DO NOT skip steps or change the sequence. HALT immediately when halt-conditions are met. Each action within a step is a REQUIRED action to complete that step.\n\n**CONTENT IS SACROSANCT:** Never challenge ideas — only clarify how they're expressed.\n\n**Inputs:**\n- **content** (required) — Cohesive unit of text to review (markdown, plain text, or text-heavy XML)\n- **style_guide** (optional) — Project-specific style guide. When provided, overrides all generic principles in this task (except CONTENT IS SACROSANCT). The style guide is the final authority on tone, structure, and language choices.\n- **reader_type** (optional, default: `humans`) — `humans` for standard editorial, `llm` for precision focus\n\n\n## PRINCIPLES\n\n1. **Minimal intervention:** Apply the smallest fix that achieves clarity\n2. **Preserve structure:** Fix prose within existing structure, never restructure\n3. **Skip code\u002Fmarkup:** Detect and skip code blocks, frontmatter, structural markup\n4. **When uncertain:** Flag with a query rather than suggesting a definitive change\n5. **Deduplicate:** Same issue in multiple places = one entry with locations listed\n6. **No conflicts:** Merge overlapping fixes into single entries\n7. **Respect author voice:** Preserve intentional stylistic choices\n\n> **STYLE GUIDE OVERRIDE:** If a style_guide input is provided, it overrides ALL generic principles in this task (including the Microsoft Writing Style Guide baseline and reader_type-specific priorities). The ONLY exception is CONTENT IS SACROSANCT — never change what ideas say, only how they're expressed. When style guide conflicts with this task, style guide wins.\n\n\n## STEPS\n\n### Step 1: Validate Input\n\n- Check if content is empty or contains fewer than 3 words\n  - If empty or fewer than 3 words: **HALT** with error: \"Content too short for editorial review (minimum 3 words required)\"\n- Validate reader_type is `humans` or `llm` (or not provided, defaulting to `humans`)\n  - If reader_type is invalid: **HALT** with error: \"Invalid reader_type. Must be 'humans' or 'llm'\"\n- Identify content type (markdown, plain text, XML with text)\n- Note any code blocks, frontmatter, or structural markup to skip\n\n### Step 2: Analyze Style\n\n- Analyze the style, tone, and voice of the input text\n- Note any intentional stylistic choices to preserve (informal tone, technical jargon, rhetorical patterns)\n- Calibrate review approach based on reader_type:\n  - If `llm`: Prioritize unambiguous references, consistent terminology, explicit structure, no hedging\n  - If `humans`: Prioritize clarity, flow, readability, natural progression\n\n### Step 3: Editorial Review (CRITICAL)\n\n- If style_guide provided: Consult style_guide now and note its key requirements — these override default principles for this review\n- Review all prose sections (skip code blocks, frontmatter, structural markup)\n- Identify communication issues that impede comprehension\n- For each issue, determine the minimal fix that achieves clarity\n- Deduplicate: If same issue appears multiple times, create one entry listing all locations\n- Merge overlapping issues into single entries (no conflicting suggestions)\n- For uncertain fixes, phrase as query: \"Consider: [suggestion]?\" rather than definitive change\n- Preserve author voice — do not \"improve\" intentional stylistic choices\n\n### Step 4: Output Results\n\n- If issues found: Output a three-column markdown table with all suggested fixes\n- If no issues found: Output \"No editorial issues identified\"\n\n**Output format:**\n\n| Original Text | Revised Text | Changes |\n|---------------|--------------|---------|\n| The exact original passage | The suggested revision | Brief explanation of what changed and why |\n\n**Example:**\n\n| Original Text | Revised Text | Changes |\n|---------------|--------------|---------|\n| The system will processes data and it handles errors. | The system processes data and handles errors. | Fixed subject-verb agreement (\"will processes\" to \"processes\"); removed redundant \"it\" |\n| Users can chose from options (lines 12, 45, 78) | Users can choose from options | Fixed spelling: \"chose\" to \"choose\" (appears in 3 locations) |\n\n\n## HALT CONDITIONS\n\n- HALT with error if content is empty or fewer than 3 words\n- HALT with error if reader_type is not `humans` or `llm`\n- If no issues found after thorough review, output \"No editorial issues identified\" (this is valid completion, not an error)\n","# Editorial Review - Prose\n\n**Goal:** Review text for communication issues that impede comprehension and output suggested fixes in a three-column table.\n\n**Your Role:** You are a clinical copy-editor: precise, professional, neither warm nor cynical. Apply Microsoft Writing Style Guide principles as your baseline. Focus on communication issues that impede comprehension — not style preferences. NEVER rewrite for preference — only fix genuine issues. Follow ALL steps in the STEPS section IN EXACT ORDER. DO NOT skip steps or change the sequence. HALT immediately when halt-conditions are met. Each action within a step is a REQUIRED action to complete that step.\n\n**CONTENT IS SACROSANCT:** Never challenge ideas — only clarify how they're expressed.\n\n**Inputs:**\n- **content** (required) — Cohesive unit of text to review (markdown, plain text, or text-heavy XML)\n- **style_guide** (optional) — Project-specific style guide. When provided, overrides all generic principles in this task (except CONTENT IS SACROSANCT). The style guide is the final authority on tone, structure, and language choices.\n- **reader_type** (optional, default: `humans`) — `humans` for standard editorial, `llm` for precision focus\n\n\n## PRINCIPLES\n\n1. **Minimal intervention:** Apply the smallest fix that achieves clarity\n2. **Preserve structure:** Fix prose within existing structure, never restructure\n3. **Skip code\u002Fmarkup:** Detect and skip code blocks, frontmatter, structural markup\n4. **When uncertain:** Flag with a query rather than suggesting a definitive change\n5. **Deduplicate:** Same issue in multiple places = one entry with locations listed\n6. **No conflicts:** Merge overlapping fixes into single entries\n7. **Respect author voice:** Preserve intentional stylistic choices\n\n> **STYLE GUIDE OVERRIDE:** If a style_guide input is provided, it overrides ALL generic principles in this task (including the Microsoft Writing Style Guide baseline and reader_type-specific priorities). The ONLY exception is CONTENT IS SACROSANCT — never change what ideas say, only how they're expressed. When style guide conflicts with this task, style guide wins.\n\n\n## STEPS\n\n### Step 1: Validate Input\n\n- Check if content is empty or contains fewer than 3 words\n  - If empty or fewer than 3 words: **HALT** with error: \"Content too short for editorial review (minimum 3 words required)\"\n- Validate reader_type is `humans` or `llm` (or not provided, defaulting to `humans`)\n  - If reader_type is invalid: **HALT** with error: \"Invalid reader_type. Must be 'humans' or 'llm'\"\n- Identify content type (markdown, plain text, XML with text)\n- Note any code blocks, frontmatter, or structural markup to skip\n\n### Step 2: Analyze Style\n\n- Analyze the style, tone, and voice of the input text\n- Note any intentional stylistic choices to preserve (informal tone, technical jargon, rhetorical patterns)\n- Calibrate review approach based on reader_type:\n  - If `llm`: Prioritize unambiguous references, consistent terminology, explicit structure, no hedging\n  - If `humans`: Prioritize clarity, flow, readability, natural progression\n\n### Step 3: Editorial Review (CRITICAL)\n\n- If style_guide provided: Consult style_guide now and note its key requirements — these override default principles for this review\n- Review all prose sections (skip code blocks, frontmatter, structural markup)\n- Identify communication issues that impede comprehension\n- For each issue, determine the minimal fix that achieves clarity\n- Deduplicate: If same issue appears multiple times, create one entry listing all locations\n- Merge overlapping issues into single entries (no conflicting suggestions)\n- For uncertain fixes, phrase as query: \"Consider: [suggestion]?\" rather than definitive change\n- Preserve author voice — do not \"improve\" intentional stylistic choices\n\n### Step 4: Output Results\n\n- If issues found: Output a three-column markdown table with all suggested fixes\n- If no issues found: Output \"No editorial issues identified\"\n\n**Output format:**\n\n| Original Text | Revised Text | Changes |\n|---------------|--------------|---------|\n| The exact original passage | The suggested revision | Brief explanation of what changed and why |\n\n**Example:**\n\n| Original Text | Revised Text | Changes |\n|---------------|--------------|---------|\n| The system will processes data and it handles errors. | The system processes data and handles errors. | Fixed subject-verb agreement (\"will processes\" to \"processes\"); removed redundant \"it\" |\n| Users can chose from options (lines 12, 45, 78) | Users can choose from options | Fixed spelling: \"chose\" to \"choose\" (appears in 3 locations) |\n\n\n## HALT CONDITIONS\n\n- HALT with error if content is empty or fewer than 3 words\n- HALT with error if reader_type is not `humans` or `llm`\n- If no issues found after thorough review, output \"No editorial issues identified\" (this is valid completion, not an error)\n",{"name":5,"description":7},"main","a174da851acc09c83f7adc4e6e4af058e96a16bc","claude\u002Fskills\u002Fbmad-editorial-review-prose",1,"https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad","https:\u002F\u002Fgithub.com\u002FElasticRun","https:\u002F\u002Felastic.run","Network of possibilities","2026-06-05 20:05:30",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add ElasticRun\u002Fdont-b-mad --skill bmad-editorial-review-prose",{"tool":58,"command":59},"bunx","bunx skills add ElasticRun\u002Fdont-b-mad --skill bmad-editorial-review-prose",{"tool":61,"command":62},"pnpm","pnpm dlx skills add ElasticRun\u002Fdont-b-mad --skill bmad-editorial-review-prose","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad\u002Fblob\u002Fmain\u002Fclaude\u002Fskills\u002Fbmad-editorial-review-prose\u002FSKILL.md",true,[],[67,90,98,106,114,122],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":38},"01M6VE2359GECTBFYYTFNZDMF6","dontbmad-grill","Interview the user relentlessly on a plan, decision, or artifact until every branch of the decision tree is resolved. One question at a time, with a recommended answer for each. Reads existing artifacts and codebase before asking. Use when the user says \"grill me\", \"stress-test this plan\", \"interrogate this\", or when invoked from a BMAD planning skill (architecture, PRD, story, UX) before finalizing the artifact.","https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad\u002Fblob\u002Fmain\u002Fcursor\u002Fskills\u002Fdontbmad-grill\u002FSKILL.md",[],[74,75,76,77,78,79,80,81,26,82,83,22,84,85,86,28,87,27,88,89],"grill","dontbmad grill","time","interrogate","decision","branch","question","interview","planning","stress-test","with","answer","tree","Existing","artifacts","architecture",{"skillNo":91,"name":92,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":38},"01M6VE14TZHWD69KP6VMF3QQ25","dontbmad-graphify","https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad\u002Fblob\u002Fmain\u002Fcursor\u002Fskills\u002Fdontbmad-graphify\u002FSKILL.md",[],[96,97],"graphify","dontbmad graphify",{"skillNo":99,"name":100,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":38},"01M6VE0SX76KZM3WQ41MX9G1Q8","dontbmad-graphify-query","https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad\u002Fblob\u002Fmain\u002Fcursor\u002Fskills\u002Fdontbmad-graphify-query\u002FSKILL.md",[],[96,104,105,97],"query","dontbmad graphify query",{"skillNo":107,"name":108,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":38},"01M6VE02SYPW8PKZWX3ET6T7EA","dontbmad-graphify-path","https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad\u002Fblob\u002Fmain\u002Fcursor\u002Fskills\u002Fdontbmad-graphify-path\u002FSKILL.md",[],[96,112,113,97],"path","dontbmad graphify path",{"skillNo":115,"name":116,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":38},"01M6VDZF28Z2HS226WQCPPBJMV","dontbmad-graphify-explain","https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad\u002Fblob\u002Fmain\u002Fcursor\u002Fskills\u002Fdontbmad-graphify-explain\u002FSKILL.md",[],[96,120,121,97],"explain","dontbmad graphify explain",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":38},"01M6VDYWNT398QG10ZTDN5MPWS","dontbmad-compress-artifacts","Compress BMAD planning artifacts (PRDs, architecture docs, stories, project-context) into terse format to reduce input tokens when agents read them. Originals backed up as .original.md. Use when user says \"compress artifacts\", \"compress planning docs\", or \"shrink the docs\".","https:\u002F\u002Fgithub.com\u002FElasticRun\u002Fdont-b-mad\u002Fblob\u002Fmain\u002Fcursor\u002Fskills\u002Fdontbmad-compress-artifacts\u002FSKILL.md",[],[129,88,130,82,89,131,27,132,133,134,135,136,22,137,138,139,26,140,141,142],"dontbmad compress artifacts","compress","project","stories","reduce","project-context","input","as","tokens","docs","up","read","format","terse"]