[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P9CEME6YBHP7BY0KVFN87V":3,"skill-same:01M6P9CEME6YBHP7BY0KVFN87V":65},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6P9CEME6YBHP7BY0KVFN87V","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","combsmith\u002F.github-private","combsmith","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F258516906?v=4","01M6H305A64BBE95VKYNNXDV4Y","CombSmith","01M6P8XQJHQ22WV72XSHE3NSKS",4,"MIT","https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private\u002Fblob\u002Fmain\u002Fframeworks\u002Fbmad-method\u002Fsrc\u002Fcore-skills\u002Fbmad-editorial-review-prose\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"editorial","editorial review","bmad editorial review prose","bmad","review","prose","bmad editorial review","use","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","46520352938752d2973ade5f7a84b01205f7aac6","frameworks\u002Fbmad-method\u002Fsrc\u002Fcore-skills\u002Fbmad-editorial-review-prose",1,"https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private","https:\u002F\u002Fgithub.com\u002Fcombsmith","https:\u002F\u002Fcombsmith.com","Open-source tools and experiments spanning agent orchestration, AI agent interfaces, AI content tooling, beekeeping tech, personal finance, and consumer apps.","2026-11-14 04:20:37",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add combsmith\u002F.github-private --skill bmad-editorial-review-prose",{"tool":57,"command":58},"bunx","bunx skills add combsmith\u002F.github-private --skill bmad-editorial-review-prose",{"tool":60,"command":61},"pnpm","pnpm dlx skills add combsmith\u002F.github-private --skill bmad-editorial-review-prose","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private\u002Fblob\u002Fmain\u002Fframeworks\u002Fbmad-method\u002Fsrc\u002Fcore-skills\u002Fbmad-editorial-review-prose\u002FSKILL.md",true,[],[66,93,107,134,151,169],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":37},"01M6P9K2GYFR9RBTH96ADYZXEW","bmad-testarch-trace","Generate traceability matrix and quality gate decision. Use when the user says \"lets create traceability matrix\" or \"I want to analyze test coverage\"","https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private\u002Fblob\u002Fmain\u002Fframeworks\u002Fbmad-test-architecture\u002Fsrc\u002Fworkflows\u002Ftestarch\u002Fbmad-testarch-trace\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[78,79,22,80,81,82,83,84,85,26,86,31,87,88,89,90,91,92],"trace","bmad testarch trace","bmad testarch","analyze","matrix","traceability","gate","test coverage","coverage","decision","quality","generate","create","quality gate","test",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":100,"publishedAt":37},"01M6P9JB7TD978DGCMEWWJ88GR","bmad-testarch-test-review","Review test quality using best practices validation. Use when user says \"lets review tests\" or \"I want to evaluate test quality\"","https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private\u002Fblob\u002Fmain\u002Fframeworks\u002Fbmad-test-architecture\u002Fsrc\u002Fworkflows\u002Ftestarch\u002Fbmad-testarch-test-review\u002FSKILL.md",[99],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[22,80,101,102,23,92,103,104,105,106,26,31,88],"test review","bmad testarch test review","best practices","tests","validation","evaluate",{"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":122,"publishedAt":37},"01M6P9J2FJH9X93F027N9XKP8G","bmad-testarch-test-design","Create system-level or epic-level test plans. Use when the user says \"lets design test plan\" or \"I want to create test strategy\"","https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private\u002Fblob\u002Fmain\u002Fframeworks\u002Fbmad-test-architecture\u002Fsrc\u002Fworkflows\u002Ftestarch\u002Fbmad-testarch-test-design\u002FSKILL.md",[113,114,117],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":115,"categoryName":116,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[80,22,123,124,92,125,126,127,128,129,26,31,130,131,132,90,133],"bmad testarch test design","design","test design","create test","EPIC","plans","test strategy","strategy","plan","test plan","system",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":37},"01M6P9HNE1J104G3EYV50FET7Q","bmad-testarch-nfr","Audit NFR evidence for performance, security, reliability, and scalability. Use when implementation evidence exists and the user says \"audit NFR evidence\", \"audit NFRs\", or \"evaluate non-functional requirements\"","https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private\u002Fblob\u002Fmain\u002Fframeworks\u002Fbmad-test-architecture\u002Fsrc\u002Fworkflows\u002Ftestarch\u002Fbmad-testarch-nfr\u002FSKILL.md",[],[141,22,80,106,142,27,143,144,145,146,147,26,31,148,149,150],"bmad testarch nfr","reliability","functional","requirements","scalability","implementation","evidence","audit","performance","security",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":37},"01M6P9HD6HCAFVSRQWT2Z62NEM","bmad-testarch-framework","Initialize test framework with Playwright or Cypress. Use when the user says \"lets setup test framework\" or \"I want to initialize testing framework\"","https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private\u002Fblob\u002Fmain\u002Fframeworks\u002Fbmad-test-architecture\u002Fsrc\u002Fworkflows\u002Ftestarch\u002Fbmad-testarch-framework\u002FSKILL.md",[157],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[159,160,22,80,161,162,163,92,164,165,166,167,168,26,31],"bmad testarch framework","framework","testing framework","setup","test framework","playwright","testing","initialize","with","cypress",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":179,"publishedAt":37},"01M6P9GVNB0SW4HPA4VR9VNN2V","bmad-testarch-ci","Scaffold CI\u002FCD quality pipeline with test execution. Use when the user says \"lets setup CI pipeline\" or \"I want to create quality gates\"","https:\u002F\u002Fgithub.com\u002Fcombsmith\u002F.github-private\u002Fblob\u002Fmain\u002Fframeworks\u002Fbmad-test-architecture\u002Fsrc\u002Fworkflows\u002Ftestarch\u002Fbmad-testarch-ci\u002FSKILL.md",[175,176],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":177,"categoryName":178,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000011","运维与部署",[22,80,180,181,182,167,183,184,185,26,31,88,186,187,90,188,162,189,92],"bmad testarch ci","ci","gates","CI\u002FCD","test execution","cd","execution","pipeline","quality gates","scaffold"]