[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K4WM70GXFQH6JS1CHS083":3,"skill-same:01M71K4WM70GXFQH6JS1CHS083":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":18,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M71K4WM70GXFQH6JS1CHS083","change-request",null,"Add a new requirement or reorder epics by WSJF against specs\u002Frelease-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.","danielvm-git\u002Fbigpowers","danielvm-git","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1020864?v=4","01M71H1N1CTQ529S0KN7KETVG6","Daniel V M","01M71H1N218Y3S8WHCJ58NPRSW",289,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fchange-request\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"request","change request","change","add","sonnet","yaml","release","WSJF","plan","prioritization","standard","EPIC","when","use","new","modes","directories","2026-11-10 10:12:30",false,"---\nname: change-request\nmodel: sonnet\neffort: standard\ndescription: Add a new requirement or reorder epics by WSJF against specs\u002Frelease-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.\n---\n\n\u003C!-- story: e45s29 -->\n\u003C!-- story: e20s01 -->\n\n# Change Request\n\n> **HARD GATE** — `specs\u002Frelease-plan.yaml` must exist before running either mode. If it doesn't, run `plan-release` first.\n>\n> → verify: `test -f specs\u002Frelease-plan.yaml`\n\nTwo modes. State which one you want or the skill will ask.\n\n## Mode A — Add\n\nIntake a new requirement mid-flight without disrupting work in progress.\n\n1. **Capture**: What is the change? What problem does it solve?\n2. **Locate**: Which existing stories in `specs\u002Fepics\u002F` does it affect or replace?\n3. **Draft**: Add story + `tasks[]` with Gherkin-style AC in epic YAML (each task has `verify`). Tag requirement deltas: `ADDED` \u002F `MODIFIED` \u002F `REMOVED` \u002F `RENAMED` with before\u002Fafter for non-`ADDED` changes (e45s29).\n4. **Place**: Append story under existing epic capsule, or create `specs\u002Fepics\u002FeNN-slug.yaml` and register in `release-plan.yaml` `epics[]`.\n5. **Score**: Compute WSJF; note if it outranks in-progress work.\n\n→ verify: `grep -c 'stories:' specs\u002Fepics\u002F*\u002Fepic.yaml`\n\n## Mode B — Reorder\n\nValue-engineering pass over the full release using WSJF.\n\nSee [REFERENCE.md](REFERENCE.md) for the full WSJF scoring rubric.\n\n1. **Score** each epic\u002Fstory: BV + TC + RR \u002F Job Size.\n2. **Re-sort** `release-plan.yaml` `epics[]` and per-epic `wsjf` fields.\n3. **Flag cut candidates**: WSJF \u003C 1.5.\n4. **Update** `specs\u002Frelease-plan.yaml` and epic `wsjf` keys with rationale.\n5. **Report** the delta.\n\n→ verify: `grep -c 'wsjf' specs\u002Frelease-plan.yaml specs\u002Fepics\u002F*\u002Fepic.yaml`\n\n## Conversational Mode\n\nIf the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.\n\n### 5-Step Flow\n\n1. **Capture**: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.\n2. **Locate**: Identify which epic or capability in `specs\u002Fepics\u002F` the request affects or replaces.\n3. **Draft**: Present a structured draft of the proposed story and tasks for user confirmation.\n4. **Score**: Estimate the WSJF score and explain the calculation so the user understands the priority.\n5. **Place**: Confirm the final epic placement with the user before writing files.\n\n## After either mode\n\nRun `bash scripts\u002Fsync-status-from-epics.sh`. Suggest `plan-work` or `build-epic` for the top-ranked unstarted story.\n","\u003C!-- story: e45s29 -->\n\u003C!-- story: e20s01 -->\n\n# Change Request\n\n> **HARD GATE** — `specs\u002Frelease-plan.yaml` must exist before running either mode. If it doesn't, run `plan-release` first.\n>\n> → verify: `test -f specs\u002Frelease-plan.yaml`\n\nTwo modes. State which one you want or the skill will ask.\n\n## Mode A — Add\n\nIntake a new requirement mid-flight without disrupting work in progress.\n\n1. **Capture**: What is the change? What problem does it solve?\n2. **Locate**: Which existing stories in `specs\u002Fepics\u002F` does it affect or replace?\n3. **Draft**: Add story + `tasks[]` with Gherkin-style AC in epic YAML (each task has `verify`). Tag requirement deltas: `ADDED` \u002F `MODIFIED` \u002F `REMOVED` \u002F `RENAMED` with before\u002Fafter for non-`ADDED` changes (e45s29).\n4. **Place**: Append story under existing epic capsule, or create `specs\u002Fepics\u002FeNN-slug.yaml` and register in `release-plan.yaml` `epics[]`.\n5. **Score**: Compute WSJF; note if it outranks in-progress work.\n\n→ verify: `grep -c 'stories:' specs\u002Fepics\u002F*\u002Fepic.yaml`\n\n## Mode B — Reorder\n\nValue-engineering pass over the full release using WSJF.\n\nSee [REFERENCE.md](REFERENCE.md) for the full WSJF scoring rubric.\n\n1. **Score** each epic\u002Fstory: BV + TC + RR \u002F Job Size.\n2. **Re-sort** `release-plan.yaml` `epics[]` and per-epic `wsjf` fields.\n3. **Flag cut candidates**: WSJF \u003C 1.5.\n4. **Update** `specs\u002Frelease-plan.yaml` and epic `wsjf` keys with rationale.\n5. **Report** the delta.\n\n→ verify: `grep -c 'wsjf' specs\u002Frelease-plan.yaml specs\u002Fepics\u002F*\u002Fepic.yaml`\n\n## Conversational Mode\n\nIf the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.\n\n### 5-Step Flow\n\n1. **Capture**: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.\n2. **Locate**: Identify which epic or capability in `specs\u002Fepics\u002F` the request affects or replaces.\n3. **Draft**: Present a structured draft of the proposed story and tasks for user confirmation.\n4. **Score**: Estimate the WSJF score and explain the calculation so the user understands the priority.\n5. **Place**: Confirm the final epic placement with the user before writing files.\n\n## After either mode\n\nRun `bash scripts\u002Fsync-status-from-epics.sh`. Suggest `plan-work` or `build-epic` for the top-ranked unstarted story.\n",{"name":5,"model":23,"effort":29,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa","skills\u002Fchange-request",24,"https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers","https:\u002F\u002Fdanielvm-git.github.io\u002Fbigpowers\u002F","https:\u002F\u002Fgithub.com\u002Fdanielvm-git","danielvm.net","2026-11-10 01:18:54",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add danielvm-git\u002Fbigpowers --skill change-request",{"tool":56,"command":57},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill change-request",{"tool":59,"command":60},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill change-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fchange-request\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"REFERENCE.md","REFERENCE","参考文档",1714,"https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fchange-request\u002FREFERENCE.md",[71,92,99,125,147,168],{"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":36},"01M71KBG9F8X644MJB16H4V8M7","skill-verify-fail-open-fixture","Negative-path fixture for run-skill-verify.sh — must never PASS.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fskill-verify-fail-open\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[83,84,85,86,87,88,89,90,91],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":93,"name":94,"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":95,"categories":96,"keywords":97,"publishedAt":36},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[98,88],"negative path",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":108,"publishedAt":36},"01M71KBBGF7Y4EB4AMHBZ8CJFC","write-document","Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs\u002F directory.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-document\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000002","文档处理",[109,110,111,112,113,114,115,116,117,29,32,31,118,119,23,120,121,122,123,124],"write","write document","document","documents","actionable","technical","methodology","high","bmad","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":36},"01M71KB8TM089JJD5AY5KAFSDM","wire-observability","Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-observability\u002FSKILL.md",[],[132,133,134,29,135,32,136,137,138,22,23,139,140,141,142,143,144,31,145,146],"observability","wire observability","readiness","commands","development","as","logging","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":36},"01M71KB6CNRANP449DQA3NJZ96","wire-ci","CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fwire-ci\u002FSKILL.md",[],[154,155,156,157,158,159,160,161,162,163,164,29,165,90,132,23,166,167],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":185,"publishedAt":36},"01M71KB2ZV98P03X88QR8MT9F1","visual-dashboard","Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers\u002Fdashboard\u002F. Reads specs\u002Fstate.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-dashboard\u002FSKILL.md",[174,177,182],{"categoryNo":175,"categoryName":176,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":178,"categoryName":179,"taxonomyType":180,"taxonomyTypeDesc":181},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":183,"categoryName":184,"taxonomyType":180,"taxonomyTypeDesc":181},"01JBSEEDCAT000000000000033","数据分析师",[186,187,188,189,190,191,192,193,194,23,195,25,196,27,197,198,199,145,200,201],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","opencode","browser","api","architecture","project status","http api"]