[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DDGSE4AMZ4V76NV8KK5WFP":3,"skill-same:01M6DDGSE4AMZ4V76NV8KK5WFP":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":13,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6DDGSE4AMZ4V76NV8KK5WFP","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","Hexalith\u002FHexalith.FrontShell","Hexalith","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80614290?v=4","01M6DBNQRMWTKX8V49BV1XNXV9","01M6DBNQX5SJ5BFK1QKMT2ZAXS",0,"MIT","https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell\u002Fblob\u002Fmain\u002F_bmad\u002Fcore\u002Fbmad-editorial-review-prose\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31],"review","editorial review","bmad editorial review prose","prose","bmad editorial review","bmad","editor","issues","communication","improve","text","user","use","clinical","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","1d461f2105c8d90ad067fbf0a3efa0f875285adf","_bmad\u002Fcore\u002Fbmad-editorial-review-prose","https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell","https:\u002F\u002Fgithub.com\u002FHexalith","https:\u002F\u002Fhexalith.readthedocs.io\u002F","2026-04-05 22:10:05",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add Hexalith\u002FHexalith.FrontShell --skill bmad-editorial-review-prose",{"tool":50,"command":51},"bunx","bunx skills add Hexalith\u002FHexalith.FrontShell --skill bmad-editorial-review-prose",{"tool":53,"command":54},"pnpm","pnpm dlx skills add Hexalith\u002FHexalith.FrontShell --skill bmad-editorial-review-prose","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell\u002Fblob\u002Fmain\u002F_bmad\u002Fcore\u002Fbmad-editorial-review-prose\u002FSKILL.md",true,[],[59,77,101,115,134,148],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":70,"publishedAt":32},"01M6DDN9BYPMZARQPC3JXNER94","wds-8-product-evolution","Brownfield improvements — the full WDS pipeline in miniature for existing products","https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell\u002Fblob\u002Fmain\u002F_bmad\u002Fwds\u002Fworkflows\u002Fwds-8-product-evolution\u002FSKILL.md",[65],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[71,72,73,74,75,76],"product","wds 8 product evolution","evolution","full","pipeline","brownfield",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":91,"publishedAt":32},"01M6DDN5YE3MAG19NE0V5S6S9H","wds-7-design-system","Create, import, browse, and maintain design system components and tokens","https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell\u002Fblob\u002Fmain\u002F_bmad\u002Fwds\u002Fworkflows\u002Fwds-7-design-system\u002FSKILL.md",[83,88],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":89,"categoryName":90,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000032","设计师",[92,93,94,95,96,97,98,99,100],"design","design system","wds 7 design system","system","components","create","browse","maintain","tokens",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":32},"01M6DDMXYC0ZKGDMF4TZYAKT5R","wds-6-asset-generation","Generate visual and text assets from specifications through AI-powered creative production","https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell\u002Fblob\u002Fmain\u002F_bmad\u002Fwds\u002Fworkflows\u002Fwds-6-asset-generation\u002FSKILL.md",[],[108,109,110,111,112,28,113,114],"generation","wds 6 asset generation","assets","visual","creative","generate","Production",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":124,"publishedAt":32},"01M6DDMQQHJX457RM5R3AA340P","wds-5-agentic-development","AI-assisted development, testing, and reverse engineering through structured agent collaboration","https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell\u002Fblob\u002Fmain\u002F_bmad\u002Fwds\u002Fworkflows\u002Fwds-5-agentic-development\u002FSKILL.md",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000008","测试与质量",[125,126,127,128,129,130,131,132,133],"development","agentic","wds 5 agentic development","agentic development","testing","collaboration","agent collaboration","engineering","structured",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":142,"publishedAt":32},"01M6DDMBZ1VC44HATR12NKBYWT","wds-4-ux-design","Transform ideas into detailed visual specifications through scenario-driven design","https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell\u002Fblob\u002Fmain\u002F_bmad\u002Fwds\u002Fworkflows\u002Fwds-4-ux-design\u002FSKILL.md",[140,141],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},{"categoryNo":89,"categoryName":90,"taxonomyType":68,"taxonomyTypeDesc":69},[143,144,92,145,111,146,147],"ux","wds 4 ux design","scenario","ideas","driven",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":32},"01M6DDM8CC0BNAMB6HBKXTXYVT","wds-3-scenarios","Create UX scenario outlines from Trigger Map through structured micro-steps","https:\u002F\u002Fgithub.com\u002FHexalith\u002FHexalith.FrontShell\u002Fblob\u002Fmain\u002F_bmad\u002Fwds\u002Fworkflows\u002Fwds-3-scenarios\u002FSKILL.md",[],[155,97,143,156,157,158,133,145,159],"wds 3 scenarios","micro","Outlines","map","trigger"]