[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71H2EF211ZTJS2GERHEFWQK":3,"skill-same:01M71H2EF211ZTJS2GERHEFWQK":63},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M71H2EF211ZTJS2GERHEFWQK","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",290,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.cline\u002Fskills\u002Fchange-request\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"change","request","change request","directories","new","when","prioritization","plan","release","sonnet","add","modes","use","EPIC","WSJF","yaml","2026-11-10 10:12:30",false,"---\nname: change-request\nmodel: sonnet\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\n---\n\n# WSJF Scoring Reference\n\nWeighted Shortest Job First: **WSJF = (Business Value + Time Criticality + Risk Reduction) \u002F Job Size**\n\nAll dimensions scored 1–10 using a Fibonacci-like scale: 1, 2, 3, 5, 8, 10.\n\n## Business Value\n\n| Score | Meaning |\n|-------|---------|\n| 10 | Core revenue path, legal requirement, blocking launch |\n| 8  | Significant user value, major pain point removed |\n| 5  | Notable improvement, medium user segment affected |\n| 3  | Nice-to-have, minor convenience |\n| 1  | Cosmetic or speculative |\n\n## Time Criticality\n\n| Score | Meaning |\n|-------|---------|\n| 10 | Hard deadline (regulatory, contract, launch date) |\n| 8  | Competitive window closing, partner dependency |\n| 5  | Would delay next milestone if deferred |\n| 3  | Flexible, can slip one sprint |\n| 1  | No urgency |\n\n## Risk Reduction (or Opportunity Enablement)\n\n| Score | Meaning |\n|-------|---------|\n| 10 | Eliminates critical architectural risk or enables a new capability |\n| 8  | Reduces a known failure mode or unblocks high-value work |\n| 5  | Moderate risk mitigation or enablement |\n| 3  | Low risk reduction |\n| 1  | No risk relevance |\n\n## Job Size (effort denominator — larger = lower WSJF)\n\n| Score | Meaning |\n|-------|---------|\n| 1  | Hours |\n| 2  | 1 day |\n| 3  | 2–3 days |\n| 5  | 1 week |\n| 8  | 2 weeks |\n| 10 | 1 month+ |\n\n## Cut threshold\n\nStories with WSJF \u003C 1.5 are cut candidates: high effort, low combined value.\n\n## Example\n\nStory: \"Add OAuth login\"\n- Business Value: 8 (removes major sign-up friction)\n- Time Criticality: 5 (Q3 launch nice, not hard)\n- Risk Reduction: 3 (minor security improvement)\n- Job Size: 5 (one week)\n\nWSJF = (8 + 5 + 3) \u002F 5 = **3.2** — healthy, implement early.\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\n---\n\n# WSJF Scoring Reference\n\nWeighted Shortest Job First: **WSJF = (Business Value + Time Criticality + Risk Reduction) \u002F Job Size**\n\nAll dimensions scored 1–10 using a Fibonacci-like scale: 1, 2, 3, 5, 8, 10.\n\n## Business Value\n\n| Score | Meaning |\n|-------|---------|\n| 10 | Core revenue path, legal requirement, blocking launch |\n| 8  | Significant user value, major pain point removed |\n| 5  | Notable improvement, medium user segment affected |\n| 3  | Nice-to-have, minor convenience |\n| 1  | Cosmetic or speculative |\n\n## Time Criticality\n\n| Score | Meaning |\n|-------|---------|\n| 10 | Hard deadline (regulatory, contract, launch date) |\n| 8  | Competitive window closing, partner dependency |\n| 5  | Would delay next milestone if deferred |\n| 3  | Flexible, can slip one sprint |\n| 1  | No urgency |\n\n## Risk Reduction (or Opportunity Enablement)\n\n| Score | Meaning |\n|-------|---------|\n| 10 | Eliminates critical architectural risk or enables a new capability |\n| 8  | Reduces a known failure mode or unblocks high-value work |\n| 5  | Moderate risk mitigation or enablement |\n| 3  | Low risk reduction |\n| 1  | No risk relevance |\n\n## Job Size (effort denominator — larger = lower WSJF)\n\n| Score | Meaning |\n|-------|---------|\n| 1  | Hours |\n| 2  | 1 day |\n| 3  | 2–3 days |\n| 5  | 1 week |\n| 8  | 2 weeks |\n| 10 | 1 month+ |\n\n## Cut threshold\n\nStories with WSJF \u003C 1.5 are cut candidates: high effort, low combined value.\n\n## Example\n\nStory: \"Add OAuth login\"\n- Business Value: 8 (removes major sign-up friction)\n- Time Criticality: 5 (Q3 launch nice, not hard)\n- Risk Reduction: 3 (minor security improvement)\n- Job Size: 5 (one week)\n\nWSJF = (8 + 5 + 3) \u002F 5 = **3.2** — healthy, implement early.\n",{"name":5,"model":28,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".cline\u002Fskills\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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add danielvm-git\u002Fbigpowers --skill change-request",{"tool":55,"command":56},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill change-request",{"tool":58,"command":59},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill change-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.cline\u002Fskills\u002Fchange-request\u002FSKILL.md",true,[],[64,85,92,119,141,162],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":75,"publishedAt":35},"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",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[76,77,78,79,80,81,82,83,84],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":86,"name":87,"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":88,"categories":89,"keywords":90,"publishedAt":35},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[91,81],"negative path",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":101,"publishedAt":35},"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",[98],{"categoryNo":99,"categoryName":100,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000002","文档处理",[102,103,104,105,106,107,108,109,110,111,31,24,112,113,28,114,115,116,117,118],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":35},"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",[],[126,127,128,111,129,31,130,131,132,29,28,133,134,135,136,137,138,24,139,140],"observability","wire observability","readiness","commands","development","as","logging","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":35},"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",[],[148,149,150,151,152,153,154,155,156,157,158,111,159,83,126,28,160,161],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":179,"publishedAt":35},"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",[168,171,176],{"categoryNo":169,"categoryName":170,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":172,"categoryName":173,"taxonomyType":174,"taxonomyTypeDesc":175},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":177,"categoryName":178,"taxonomyType":174,"taxonomyTypeDesc":175},"01JBSEEDCAT000000000000033","数据分析师",[180,181,182,183,184,185,186,187,188,28,189,27,190,26,191,192,193,139,194,195],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","opencode","browser","api","architecture","project status","http api"]