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