[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KWCMYKZMBE06AY561YDSQ2":3,"skill-same:01M6KWCMYKZMBE06AY561YDSQ2":70},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6KWCMYKZMBE06AY561YDSQ2","product-planning",null,"Product backlog management and release planning skill. Invoked by the product-manager agent to add items, review backlog health, re-prioritize, plan releases, or update item status. Reads and writes docs\u002Fbacklog\u002Fbacklog.md as the persistent source of truth.","rafsanulhasan\u002FHypermediaEngine","rafsanulhasan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2341142?v=4","01M6KW2HWPTZWK051N7B0HTBVG","Rafsanul Hasan","01M6KW2J0N3613382MF5DRN79H",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fproduct-planning\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"product planning","planning","product","prioritize","review backlog","source","manager","re","as","backlog","releases","management","review","plan","health","release","update","backlog management","status","docs","2026-11-10 10:12:30",false,"---\nname: product-planning\ndescription: \"Product backlog management and release planning skill. Invoked by the product-manager agent to add items, review backlog health, re-prioritize, plan releases, or update item status. Reads and writes docs\u002Fbacklog\u002Fbacklog.md as the persistent source of truth.\"\n---\n\n# Product Planning\n\nYou are executing the `product-planning` skill on behalf of the product-manager agent. You manage the backlog file at `docs\u002Fbacklog\u002Fbacklog.md` and apply prioritization rules consistently.\n\n## Input\n\nThe calling agent passes an action verb as `args`:\n\n| Action | Description |\n|---|---|\n| `review-backlog` | Summarize current backlog state and recommend next actions |\n| `add-item \u003Cdescription>` | Add a new work item to the backlog |\n| `prioritize` | Re-rank items based on current context |\n| `plan-release \u003Cversion>` | Prepare a release checklist and hand off to devops-engineer |\n| `update-status \u003CITEM-NNN> \u003Cstatus>` | Change an item's status |\n\n## Process\n\n### Backlog Initialization\n\nIf `docs\u002Fbacklog\u002Fbacklog.md` does not exist:\n\n1. Create the `docs\u002Fbacklog\u002F` directory path.\n2. Write the initial backlog file:\n\n```markdown\n# HypermediaEngine Product Backlog\n\n_Last updated: YYYY-MM-DD_\n\n## Priority Key\n- **P0**: Critical blocker — stops work or releases\n- **P1**: High impact — next to be worked\n- **P2**: Medium — planned, not urgent\n- **P3**: Low — nice-to-have, deferred\n\n## Active Items\n\n_(none yet)_\n\n## Completed Items\n\n_(none yet)_\n```\n\n### Priority Rules (always enforced)\n\n| Type | Default Priority | Override Condition |\n|---|---|---|\n| Security Fix | P0 | Never downgrade |\n| Bug (regression \u002F system blocker) | P0 | — |\n| Bug (other) | P1 | — |\n| Feature | P1 | Cosmetic or low-impact → P2 |\n| TechDebt | P2 | Blocking a P0\u002FP1 item → P1 |\n| Release | — | Blocked by any open P0 for the milestone |\n\n### ID Assignment\n\nRead the backlog, find the highest existing `ITEM-NNN` number, increment by 1. Start at `ITEM-001` if the backlog is empty.\n\n### Item Format\n\n```markdown\n### ITEM-NNN: \u003CTitle>\n- **Type**: Feature | Bug | Security | TechDebt | Release\n- **Priority**: P0 | P1 | P2 | P3\n- **Status**: Backlog | In Progress | Review | Done | Cancelled\n- **Milestone**: \u003Cversion or \"Unplanned\">\n- **Added**: YYYY-MM-DD\n- **Agent Chain**: \u003Ce.g., requirement-analyst → software-architect → software-engineer → sqa-engineer>\n\n**Acceptance Criteria**\n- [ ] \u003Cverifiable condition>\n- [ ] \u003Cverifiable condition>\n```\n\n### Action: review-backlog\n\n1. Count items by type, priority, and status.\n2. Flag any P0 items not \"In Progress\" — these are immediate escalations.\n3. Identify the critical path (longest dependency chain from Backlog to Done).\n4. Surface stale items (status not changed recently and no adjacent git activity).\n5. Recommend the next 3 unblocked items to start.\n\n### Action: add-item\n\n1. Assign next ITEM-NNN.\n2. Apply priority rules.\n3. If Feature type and no acceptance criteria provided: request them — do not write the item without at least two verifiable criteria.\n4. Check for duplicate items before adding (search by title keywords).\n5. Append to \"Active Items\" section.\n6. Write to `docs\u002Fbacklog\u002Fbacklog.md`.\n\n### Action: prioritize\n\n1. List all active items sorted by current priority.\n2. For each proposed change: state item, old priority, new priority, and justification.\n3. Apply changes to `docs\u002Fbacklog\u002Fbacklog.md`.\n4. Return a change summary.\n\n### Action: plan-release\n\n1. Identify all items for the target milestone.\n2. Verify all are \"Done\" or explicitly \"Cancelled\" \u002F deferred to a later milestone.\n3. Check for open P0 items — any P0 blocks the release; surface the blocker and stop.\n4. Draft release notes by type (Features \u002F Bug Fixes \u002F Security Patches \u002F Tech Debt).\n5. Present draft to the calling agent for user approval before handing off to `devops-engineer` for deployment.\n6. After approval: move all included items to \"Completed Items\" section with status \"Done\" and date.\n\n### Action: update-status\n\n1. Find item by ITEM-NNN.\n2. Update the `Status` field.\n3. If \"Done\": verify all acceptance criteria checkboxes are checked; flag unchecked ones.\n4. If update unblocks a dependent item: note it in the return value.\n5. Write to `docs\u002Fbacklog\u002Fbacklog.md`.\n\n## Output\n\nReturn the requested report or confirmation to the product-manager agent. Always write changes to `docs\u002Fbacklog\u002Fbacklog.md` before returning — never hold backlog changes in memory only.\n","# Product Planning\n\nYou are executing the `product-planning` skill on behalf of the product-manager agent. You manage the backlog file at `docs\u002Fbacklog\u002Fbacklog.md` and apply prioritization rules consistently.\n\n## Input\n\nThe calling agent passes an action verb as `args`:\n\n| Action | Description |\n|---|---|\n| `review-backlog` | Summarize current backlog state and recommend next actions |\n| `add-item \u003Cdescription>` | Add a new work item to the backlog |\n| `prioritize` | Re-rank items based on current context |\n| `plan-release \u003Cversion>` | Prepare a release checklist and hand off to devops-engineer |\n| `update-status \u003CITEM-NNN> \u003Cstatus>` | Change an item's status |\n\n## Process\n\n### Backlog Initialization\n\nIf `docs\u002Fbacklog\u002Fbacklog.md` does not exist:\n\n1. Create the `docs\u002Fbacklog\u002F` directory path.\n2. Write the initial backlog file:\n\n```markdown\n# HypermediaEngine Product Backlog\n\n_Last updated: YYYY-MM-DD_\n\n## Priority Key\n- **P0**: Critical blocker — stops work or releases\n- **P1**: High impact — next to be worked\n- **P2**: Medium — planned, not urgent\n- **P3**: Low — nice-to-have, deferred\n\n## Active Items\n\n_(none yet)_\n\n## Completed Items\n\n_(none yet)_\n```\n\n### Priority Rules (always enforced)\n\n| Type | Default Priority | Override Condition |\n|---|---|---|\n| Security Fix | P0 | Never downgrade |\n| Bug (regression \u002F system blocker) | P0 | — |\n| Bug (other) | P1 | — |\n| Feature | P1 | Cosmetic or low-impact → P2 |\n| TechDebt | P2 | Blocking a P0\u002FP1 item → P1 |\n| Release | — | Blocked by any open P0 for the milestone |\n\n### ID Assignment\n\nRead the backlog, find the highest existing `ITEM-NNN` number, increment by 1. Start at `ITEM-001` if the backlog is empty.\n\n### Item Format\n\n```markdown\n### ITEM-NNN: \u003CTitle>\n- **Type**: Feature | Bug | Security | TechDebt | Release\n- **Priority**: P0 | P1 | P2 | P3\n- **Status**: Backlog | In Progress | Review | Done | Cancelled\n- **Milestone**: \u003Cversion or \"Unplanned\">\n- **Added**: YYYY-MM-DD\n- **Agent Chain**: \u003Ce.g., requirement-analyst → software-architect → software-engineer → sqa-engineer>\n\n**Acceptance Criteria**\n- [ ] \u003Cverifiable condition>\n- [ ] \u003Cverifiable condition>\n```\n\n### Action: review-backlog\n\n1. Count items by type, priority, and status.\n2. Flag any P0 items not \"In Progress\" — these are immediate escalations.\n3. Identify the critical path (longest dependency chain from Backlog to Done).\n4. Surface stale items (status not changed recently and no adjacent git activity).\n5. Recommend the next 3 unblocked items to start.\n\n### Action: add-item\n\n1. Assign next ITEM-NNN.\n2. Apply priority rules.\n3. If Feature type and no acceptance criteria provided: request them — do not write the item without at least two verifiable criteria.\n4. Check for duplicate items before adding (search by title keywords).\n5. Append to \"Active Items\" section.\n6. Write to `docs\u002Fbacklog\u002Fbacklog.md`.\n\n### Action: prioritize\n\n1. List all active items sorted by current priority.\n2. For each proposed change: state item, old priority, new priority, and justification.\n3. Apply changes to `docs\u002Fbacklog\u002Fbacklog.md`.\n4. Return a change summary.\n\n### Action: plan-release\n\n1. Identify all items for the target milestone.\n2. Verify all are \"Done\" or explicitly \"Cancelled\" \u002F deferred to a later milestone.\n3. Check for open P0 items — any P0 blocks the release; surface the blocker and stop.\n4. Draft release notes by type (Features \u002F Bug Fixes \u002F Security Patches \u002F Tech Debt).\n5. Present draft to the calling agent for user approval before handing off to `devops-engineer` for deployment.\n6. After approval: move all included items to \"Completed Items\" section with status \"Done\" and date.\n\n### Action: update-status\n\n1. Find item by ITEM-NNN.\n2. Update the `Status` field.\n3. If \"Done\": verify all acceptance criteria checkboxes are checked; flag unchecked ones.\n4. If update unblocks a dependent item: note it in the return value.\n5. Write to `docs\u002Fbacklog\u002Fbacklog.md`.\n\n## Output\n\nReturn the requested report or confirmation to the product-manager agent. Always write changes to `docs\u002Fbacklog\u002Fbacklog.md` before returning — never hold backlog changes in memory only.\n",{"name":5,"description":7},"main","00b2c68281930728ee390bb16cec32b88d2caac7",".github\u002Fskills\u002Fproduct-planning","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine","https:\u002F\u002Fgithub.com\u002Frafsanulhasan","\r\n    MCSD || A-CSD || Software Architect\r\n\r\n","2026-06-06 07:47:06",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add rafsanulhasan\u002FHypermediaEngine --skill product-planning",{"tool":62,"command":63},"bunx","bunx skills add rafsanulhasan\u002FHypermediaEngine --skill product-planning",{"tool":65,"command":66},"pnpm","pnpm dlx skills add rafsanulhasan\u002FHypermediaEngine --skill product-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fproduct-planning\u002FSKILL.md",true,[],[71,102,122,140,167,190],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":44},"01M6KWEJD606FG3DBBRM0W4DKW","write-tests","Test implementation skill for HypermediaEngine. Takes a confirmed test plan from design-test-cases and produces compilable, runnable xUnit tests following project conventions. Validates coverage quality through mutation testing. Invoked by the sqa-engineer agent after the test plan is approved.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-tests\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[83,84,85,86,87,88,89,90,91,37,92,93,94,95,96,97,98,99,100,101],"write tests","write","tests","testing","design","test","project conventions","test plan","Bash","quality","xunit","read","edit","coverage","engineer","mutation testing","project","mutation","for",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":44},"01M6KWEF2XQ00C1Y6QCK7YHZ1H","write-documentation","Structured documentation writing workflow for HypermediaEngine. Writes or updates README.md files at the repo root and in each project directory (src\u002F, tests\u002F, samples\u002F, etc.) based on current implementation, ADRs, and architecture decisions.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-documentation\u002FSKILL.md",[],[109,84,110,111,112,113,114,91,115,116,117,118,94,95,119,99,85,120,121,101],"documentation","write documentation","writing","directory","workflow","architecture","src","repo","decisions","README","files","updates","at",{"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":44},"01M6KWEBDXTXAVPQ3BHS3YYYNT","write-adr","Writes a numbered Architecture Decision Record (ADR) for a significant architectural choice in the HypermediaEngine project. Invoked by the software-architect agent whenever a consequential design decision is made or ratified. Saves the ADR to docs\u002Farchitecture\u002Fdecisions\u002F.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fwrite-adr\u002FSKILL.md",[],[129,84,130,87,43,114,131,132,133,134,117,94,135,136,99,137,138,101,139],"adr","write adr","architect","decision","choice","grep","architecture decision record","record","software","opus","architecture decision",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":150,"publishedAt":44},"01M6KWE76TM3QHGQ08PEB3KY6D","tunit-playwright-ui-testing","Comprehensive guidance for writing coded end-to-end UI tests in C# using TUnit.Playwright. Tests inherit from PageTest — the base class manages all browser lifecycle. Covers NuGet setup, PageTest inheritance, Page Object Model, browser configuration, parallelism limiting, and CI integration. Based on the official TUnit docs at https:\u002F\u002Ftunit.dev\u002Fdocs\u002Fexamples\u002Fplaywright.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftunit-playwright-ui-testing\u002FSKILL.md",[146,147],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[86,151,152,153,154,155,156,111,157,158,159,160,161,162,163,164,85,165,166,101],"playwright","ui","playwright ui testing","ui testing","tunit","tunit playwright ui testing","official","dev","examples","ci","lifecycle","model","page","inheritance","end","object",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":44},"01M6KWE44A738GDK65QS02XJBG","triage","Task classification, decomposition, dependency mapping, and routing skill. Invoked by the triage-agent to break any user request into discrete, independently-routable work items with assigned priorities and agent chains.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage\u002FSKILL.md",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发",[169,177,178,179,180,181,182,183,184,185,186,187,188,189],"routing","classification","work","user","dependency","task","priorities","decomposition","user request","mapping","with","break","request",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":200,"publishedAt":44},"01M6KWDZ3W9ZKPR7FTTTSX8H2K","system-design","Expert system design skill. Use PROACTIVELY to design systems, review architectures, and assist software engineers in learning design principles and implementing them in the code with design patterns.","https:\u002F\u002Fgithub.com\u002Frafsanulhasan\u002FHypermediaEngine\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsystem-design\u002FSKILL.md",[196,199],{"categoryNo":197,"categoryName":198,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},[87,201,202,203,204,205,206,134,94,207,208,209,210,211,212,137,213,214,187,215],"system","system design","web","design systems","learning","haiku","use","design patterns","design principles","expert","patterns","systems","architectures","principles","implementing"]