[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K6QFJDCPB6SPKVVNKYBV4":3,"skill-same:01M71K6QFJDCPB6SPKVVNKYBV4":68},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M71K6QFJDCPB6SPKVVNKYBV4","gate-trace",null,"Deterministic traceability quality gate — reads coverage matrix + blind-spot data, applies decision rules with oracle confidence downgrade, emits PASS\u002FCONCERNS\u002FFAIL\u002FWAIVED verdict. Use before release-branch to gate merges on traceability.","danielvm-git\u002Fbigpowers","danielvm-git","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1020864?v=4","01M71H1N1CTQ529S0KN7KETVG6","Daniel V M","01M71H1N218Y3S8WHCJ58NPRSW",292,"MIT","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fgate-trace\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"gate","trace","gate trace","quality","spot","verdict","with","Rules","use","traceability","quality gate","deterministic","data","matrix","release","haiku","oracle","decision","branch","coverage","2026-11-10 10:12:30",false,"---\n# story: e80s01\n# story: e45s05\nname: gate-trace\ndescription: \"Deterministic traceability quality gate — reads coverage matrix + blind-spot data, applies decision rules with oracle confidence downgrade, emits PASS\u002FCONCERNS\u002FFAIL\u002FWAIVED verdict. Use before release-branch to gate merges on traceability.\"\n# story: e38s06\n# story: e45s32\nmodel: haiku\neffort: light\n---\n\n# Gate Trace\n\nDeterministic quality gate that combines traceability coverage and blind-spot data into a single PASS\u002FFAIL\u002FCONCERNS\u002FWAIVED decision before release.\n\n## Decision Rules\n\n| Rule | Condition | Verdict |\n|------|-----------|---------|\n| R1 | Any undone story with 0 code tags | FAIL |\n| R2 | Any story done but no verify evidence | CONCERNS |\n| R3 | P0 story (top WSJF quartile) with 0% coverage | FAIL |\n| R4 | Overall coverage \u003C 60% | CONCERNS |\n| R6 | P0 story + eNN-TEST_PLAN_LATEST.md exists + zero SC-eNNsYY-P0-* in test files | CONCERNS |\n| R5 | Overall ≥ 80% + no critical gaps + all verify → PASS | PASS |\n\n## Oracle Confidence Downgrade\n\nTEA-inspired: if trace links rely on heuristics rather than explicit tags, confidence drops.\n\n| Heuristic Ratio | Downgrade |\n|-----------------|-----------|\n| > 50% links from heuristics (file-name or task-reference) | One level (PASS→CONCERNS, CONCERNS→FAIL) |\n| > 80% links from heuristics | Two levels (PASS→FAIL, CONCERNS→FAIL) |\n\n## Process\n\n1. **Pre-flight:** Ensure `scripts\u002Ftrace-stories.sh --json` has been run (produces `specs\u002Ftraceability-matrix.json`). If not present, run it.\n2. Ensure `scripts\u002Fcheck-blind-spots.sh` has been run (produces `specs\u002Fblind-spots.json`). If not present, run it.\n3. Read `specs\u002Ftraceability-matrix.json` and `specs\u002Fblind-spots.json`.\n4. Apply decision rules R1–R5 in order (first match wins).\n5. Apply oracle confidence downgrade based on the heuristic link ratio from the matrix's `oracle_stats`.\n6. **Drift check (e39s03):** If `specs\u002Fdrift-report.json` exists and has suspect links, mark verdict as CONCERNS with note: \"Drift detected — some implementing files are newer than their specs. Run scripts\u002Fcheck-spec-drift.sh for details.\"\n7. Output verdict + rationale to stdout.\n8. **Adversarial refute check (e45s32):** Before emitting PASS, attempt to **refute** the verdict — list at least one concrete traceability gap that would block merge if it were real. If the gap is real, downgrade the verdict. Rubber-stamping is prohibited; every PASS must survive one refutation attempt.\n9. **Completeness critic (e45s05)** — Run adversarial gap-finding:\n\n```bash\nbash scripts\u002Flib\u002Fcompleteness-critic.sh\n```\n\nClassify output as **BLOCKER \u002F WARNING \u002F FILLED**. **BLOCKER overrides any PASS verdict → FAIL.** Append critic summary to rationale.\n10. Update `specs\u002Fexecution-status.yaml` with gate-trace result.\n\n## Verdict Semantics\n\n| Verdict | Meaning | Action |\n|---------|---------|--------|\n| PASS | All gates satisfied | Proceed with merge |\n| CONCERNS | Non-critical issues found | Requires explicit human override in `state.yaml` |\n| FAIL | Critical traceability gap | Block merge — fix gap first |\n| WAIVED | Cannot evaluate (missing inputs) | Skip gate — data not available |\n\n## Output Format\n\n```yaml\ngate_trace:\n  verdict: PASS|CONCERNS|FAIL|WAIVED\n  generated_at: \"\u003CISO 8601>\"\n  rationale: \"\u003Chuman-readable explanation>\"\n  heuristic_ratio: \u003C0.0–1.0>\n  downgrade_applied: \u003Ctrue|false>\n```\n\n## Integration Points\n\n- **release-branch SKILL.md** — pre-PR gate (FAIL blocks merge).\n- **test-build-release.yml** — its `sync` job runs `trace-stories.sh --strict` as the \"Traceability gate\" step (FAIL\n  blocks the release job), which shares this skill's coverage data (`traceability-matrix.json`) but\n  does not invoke a gate-trace PASS\u002FCONCERNS\u002FFAIL\u002FWAIVED verdict directly.\n- **verify-work SKILL.md** — runs blind-spot checks; gate-trace consumes the result.\n\n## References\n\n- BMAD TEA traceability approach (market survey 2026-07-02).\n- scripts\u002Ftrace-stories.sh (e38s01) — produces traceability-matrix.json.\n- scripts\u002Fcheck-blind-spots.sh (e38s04) — produces blind-spots.json.\n- specs\u002Fexecution-status.yaml — output target for gate result.\n\n## Handoff\n\nGate: READY → next: release-branch (final step before merge)\nWrites: state.yaml handoff.next_skill = release-branch\n\n## Verify\n\n→ verify: `test -x scripts\u002Frun-gate-trace-verify.sh && bash scripts\u002Frun-gate-trace-verify.sh --self-test && echo OK`\n","# Gate Trace\n\nDeterministic quality gate that combines traceability coverage and blind-spot data into a single PASS\u002FFAIL\u002FCONCERNS\u002FWAIVED decision before release.\n\n## Decision Rules\n\n| Rule | Condition | Verdict |\n|------|-----------|---------|\n| R1 | Any undone story with 0 code tags | FAIL |\n| R2 | Any story done but no verify evidence | CONCERNS |\n| R3 | P0 story (top WSJF quartile) with 0% coverage | FAIL |\n| R4 | Overall coverage \u003C 60% | CONCERNS |\n| R6 | P0 story + eNN-TEST_PLAN_LATEST.md exists + zero SC-eNNsYY-P0-* in test files | CONCERNS |\n| R5 | Overall ≥ 80% + no critical gaps + all verify → PASS | PASS |\n\n## Oracle Confidence Downgrade\n\nTEA-inspired: if trace links rely on heuristics rather than explicit tags, confidence drops.\n\n| Heuristic Ratio | Downgrade |\n|-----------------|-----------|\n| > 50% links from heuristics (file-name or task-reference) | One level (PASS→CONCERNS, CONCERNS→FAIL) |\n| > 80% links from heuristics | Two levels (PASS→FAIL, CONCERNS→FAIL) |\n\n## Process\n\n1. **Pre-flight:** Ensure `scripts\u002Ftrace-stories.sh --json` has been run (produces `specs\u002Ftraceability-matrix.json`). If not present, run it.\n2. Ensure `scripts\u002Fcheck-blind-spots.sh` has been run (produces `specs\u002Fblind-spots.json`). If not present, run it.\n3. Read `specs\u002Ftraceability-matrix.json` and `specs\u002Fblind-spots.json`.\n4. Apply decision rules R1–R5 in order (first match wins).\n5. Apply oracle confidence downgrade based on the heuristic link ratio from the matrix's `oracle_stats`.\n6. **Drift check (e39s03):** If `specs\u002Fdrift-report.json` exists and has suspect links, mark verdict as CONCERNS with note: \"Drift detected — some implementing files are newer than their specs. Run scripts\u002Fcheck-spec-drift.sh for details.\"\n7. Output verdict + rationale to stdout.\n8. **Adversarial refute check (e45s32):** Before emitting PASS, attempt to **refute** the verdict — list at least one concrete traceability gap that would block merge if it were real. If the gap is real, downgrade the verdict. Rubber-stamping is prohibited; every PASS must survive one refutation attempt.\n9. **Completeness critic (e45s05)** — Run adversarial gap-finding:\n\n```bash\nbash scripts\u002Flib\u002Fcompleteness-critic.sh\n```\n\nClassify output as **BLOCKER \u002F WARNING \u002F FILLED**. **BLOCKER overrides any PASS verdict → FAIL.** Append critic summary to rationale.\n10. Update `specs\u002Fexecution-status.yaml` with gate-trace result.\n\n## Verdict Semantics\n\n| Verdict | Meaning | Action |\n|---------|---------|--------|\n| PASS | All gates satisfied | Proceed with merge |\n| CONCERNS | Non-critical issues found | Requires explicit human override in `state.yaml` |\n| FAIL | Critical traceability gap | Block merge — fix gap first |\n| WAIVED | Cannot evaluate (missing inputs) | Skip gate — data not available |\n\n## Output Format\n\n```yaml\ngate_trace:\n  verdict: PASS|CONCERNS|FAIL|WAIVED\n  generated_at: \"\u003CISO 8601>\"\n  rationale: \"\u003Chuman-readable explanation>\"\n  heuristic_ratio: \u003C0.0–1.0>\n  downgrade_applied: \u003Ctrue|false>\n```\n\n## Integration Points\n\n- **release-branch SKILL.md** — pre-PR gate (FAIL blocks merge).\n- **test-build-release.yml** — its `sync` job runs `trace-stories.sh --strict` as the \"Traceability gate\" step (FAIL\n  blocks the release job), which shares this skill's coverage data (`traceability-matrix.json`) but\n  does not invoke a gate-trace PASS\u002FCONCERNS\u002FFAIL\u002FWAIVED verdict directly.\n- **verify-work SKILL.md** — runs blind-spot checks; gate-trace consumes the result.\n\n## References\n\n- BMAD TEA traceability approach (market survey 2026-07-02).\n- scripts\u002Ftrace-stories.sh (e38s01) — produces traceability-matrix.json.\n- scripts\u002Fcheck-blind-spots.sh (e38s04) — produces blind-spots.json.\n- specs\u002Fexecution-status.yaml — output target for gate result.\n\n## Handoff\n\nGate: READY → next: release-branch (final step before merge)\nWrites: state.yaml handoff.next_skill = release-branch\n\n## Verify\n\n→ verify: `test -x scripts\u002Frun-gate-trace-verify.sh && bash scripts\u002Frun-gate-trace-verify.sh --self-test && echo OK`\n",{"name":5,"model":34,"effort":44,"description":7},"light","main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa","skills\u002Fgate-trace",23,"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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add danielvm-git\u002Fbigpowers --skill gate-trace",{"tool":60,"command":61},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill gate-trace",{"tool":63,"command":64},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill gate-trace","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fskills\u002Fgate-trace\u002FSKILL.md",true,[],[69,90,97,126,149,169],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":80,"publishedAt":39},"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",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[81,82,83,84,85,86,87,88,89],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":91,"name":92,"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":93,"categories":94,"keywords":95,"publishedAt":39},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[96,86],"negative path",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"publishedAt":39},"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",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000002","文档处理",[107,108,109,110,111,112,113,114,115,116,27,117,118,119,120,121,122,123,124,125],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","when","minimal","bold","sonnet","integrity","organize","sync","directory","guides",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":39},"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",[],[133,134,135,116,136,27,137,138,139,140,120,141,142,143,144,145,146,117,147,148],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":39},"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",[],[156,157,158,159,160,161,162,163,164,165,25,116,166,88,133,120,167,168],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","ci pipeline setup","git","workflows",{"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":186,"publishedAt":39},"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",[175,178,183],{"categoryNo":176,"categoryName":177,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":179,"categoryName":180,"taxonomyType":181,"taxonomyTypeDesc":182},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":184,"categoryName":185,"taxonomyType":181,"taxonomyTypeDesc":182},"01JBSEEDCAT000000000000033","数据分析师",[187,188,189,190,191,192,193,194,195,120,196,33,197,198,199,200,201,147,202,203],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","opencode","plan","browser","api","architecture","project status","http api"]