[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HR5P6EKSSDC40D7RG5SCM":3,"skill-same:01M71HR5P6EKSSDC40D7RG5SCM":67},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M71HR5P6EKSSDC40D7RG5SCM","build-epic",null,"Eight-step epic build cycle — reads state.yaml, execution-status.yaml, and one epic capsule; updates status via bp-yaml-set or direct edit. Resume mode runs one step per invocation. Use instead of ad-hoc execute-plan for release work.","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\u002F.copilot\u002Fskills\u002Fbuild-epic\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"EPIC","build","build epic","state","resume","one","use","execution","for","sonnet","direct","status","edit","release","plan","work","updates","mode","cycle","SET","2026-11-10 10:12:30",false,"---\nname: build-epic\nmodel: sonnet\ndescription: \"Eight-step epic build cycle — reads state.yaml, execution-status.yaml, and one epic capsule; updates status via bp-yaml-set or direct edit. Resume mode runs one step per invocation. Use instead of ad-hoc execute-plan for release work.\"\n---\n\n\u003C!-- story: e20s05 -->\n\n# Build Epic\n\nScope: one story. Called by orchestrate-project Phase 4. Not a replacement for orchestrate-project.\n\nOrchestrates the **build** flow for a single epic: survey → plan tasks → kickoff → TDD → verify → audit → commit → release.\n\n> **HARD GATE** — Set `specs\u002Fstate.yaml` `active_flow: build_epic` and `active_epic: eNN` before starting.\n>\n> **HARD GATE** — Not on `main`\u002F`master` before step 3 (kickoff-branch).\n\n## Nine steps (`epic_cycle` in state.yaml)\n\n| Step | Skill \u002F action |\n|------|----------------|\n| 0 | `security-review` — threat-model epic scope → `specs\u002Fsecurity\u002Fepics\u002F\u003Cid>\u002FTHREAT_MODEL.md` |\n| 1 | `survey-context` — confirm epic + story |\n| 2 | `plan-work` — flesh out story `tasks[]` in `specs\u002Fepics\u002FeNN-slug\u002Fepic.yaml` |\n| 3 | `kickoff-branch` — feature branch + clean baseline |\n| 4 | `develop-tdd` — red-green per task |\n| 5 | `verify-work` — UAT + mechanical gates |\n| 6 | `audit-code` — **non-optional gate** (pass\u002Ffail; fail → loop back to step 4) |\n| 7 | `commit-message` — Conventional Commits draft |\n| 8 | `release-branch` — PR or solo land (supports `--squash-state`) | |\n\n## Process\n\n1. Read `specs\u002Fstate.yaml`, `specs\u002Fexecution-status.yaml`, `specs\u002Frelease-plan.yaml`, active `specs\u002Fepics\u002FeNN-slug\u002Fepic.yaml`.\n   - **On story start (step 1):** Write `started_at` ISO 8601 timestamp to `execution-status.yaml` under the story's key in the `stories:` section. The `bp-timing.sh` script already tracks skill-level timings — this is story-level.\n2. **Step 0 — Threat Model:** Run `security-review` against the epic's scope (read from the epic capsule). Output `specs\u002Fsecurity\u002Fepics\u002F\u003Cepic-id>\u002FTHREAT_MODEL.md` with surface area, vulnerability categories, risk level, and mitigation guidance.\n3. **Assess Impact (Step 2):** Before writing tasks, run `assess-impact --lightweight` on the proposed change. If the risk score exceeds 7, gate — require a `grill-me` session. Write the impact report to `specs\u002FIMPACT-\u003Cepic>-\u003Cstory>.md`. For net-new code with no existing dependents, skip.\n4. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`.\n5. **BCP Plus (Step 2, optional):** When the epic capsule carries a `bcp_plus_breakdown` (13-dimension sizing), also carry it into `state.yaml` as `epic_cycle.bcp_plus`. The breakdown maps each of the 13 dimensions to an integer count. NFR dimensions (11–13) that are N\u002FA per the NFR Gate may be set to 0.\n6. If `epic_cycle.step` missing, set to `1`.\n6. Run **only the current step** (resume mode) unless user asked for full auto-run.\n7. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts\u002Fbp-yaml-set.sh` if available).\n8. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts\u002Fsync-status-from-epics.sh`.\n   - **On story complete (step 8):** Write `completed_at` ISO 8601 timestamp to `execution-status.yaml` under the same story key. Format:\n\n     ```yaml\n     stories:\n       e01s01:\n         status: done\n         started_at: \"2026-07-12T16:00:00-03:00\"\n         completed_at: \"2026-07-12T18:45:00-03:00\"\n     ```\n9. **Traceability refresh:** Before step 8 (release-branch), run `bash scripts\u002Ftrace-stories.sh` to regenerate `specs\u002Ftraceability-matrix.json`, `specs\u002FTRACEABILITY_LATEST.md`, and the `specs\u002Fcodebase-wiki\u002F` OKF bundle. Surface dark\u002Forphan\u002Fstale findings for the just-built epic in your verify summary. If `scripts\u002Ftrace-stories.sh` is missing or fails, note \"trace skipped\" and continue — trace failure must be visible, not silent (blocking is gate-trace's job, e38s06).\n\n9b. **OKF wiki refresh (e39s08):** Before step 8, run maintain-wiki INGEST to refresh the OKF wiki bundle:\n   ```bash\n   bash scripts\u002Fdecompose-conventions.sh\n   bash scripts\u002Fgenerate-agent-guide.sh\n   ```\n   If any script is missing or fails, note \"OKF wiki refresh skipped\" and continue.\n   This is non-blocking — stale concepts are caught by LINT in verify-work Phase 3.\n\n### Step 6 — audit-code gate (non-optional)\n\nAfter step 5 (verify-work) completes successfully, step 6 runs `audit-code` automatically in `--gate` mode:\n\n1. **Run audit:** Invoke `audit-code --gate` on the complete diff for this story.\n2. **Pass (exit 0):** All checklist sections pass → run `bash scripts\u002Flib\u002Fassert-epic-gate.sh advance` to mechanically confirm the audit pass, then advance to step 7 (commit-message). Record `epic_cycle.audit_result: pass` in `state.yaml`.\n3. **Fail (exit 1):** One or more checklist sections fail → **reset `epic_cycle.current_step` to `4`** (develop-tdd) and add the failing section IDs to `completed_steps` as `\"1,2,3,4,5,6(fail: ...)\"`. Record `epic_cycle.audit_result: fail` in `state.yaml`. Do NOT advance past step 6 until audit passes.\n4. **Audit artifact:** Full audit report saved to `specs\u002Fverifications\u002FAUDIT-\u003Cepic>-\u003Cstory>.md` regardless of pass\u002Ffail, for reviewer traceability.\n5. **Enforce F.I.R.S.T:** After audit-code passes, run `enforce-first --quick` on new\u002Fmodified tests. Append F.I.R.S.T violations (if any) to the audit report. Failing F.I.R.S.T criteria trigger the same loop-back to step 4.\n\n## --fast mode\n\nCoalesces read-and-report steps to reduce token overhead. Activate with `build-epic --fast`.\n\n| Normal | --fast | Change |\n|--------|--------|--------|\n| Step 1 (survey-context) | 1+2 together | survey + plan in one invocation |\n| Step 2 (plan-work) | (absorbed into 1) | — |\n| Step 3 (kickoff-branch) | Step 2 | unchanged, sequential |\n| Step 4 (develop-tdd) | Step 3 | unchanged, sequential |\n| Step 5 (verify-work) | Step 4 | unchanged, sequential |\n| Step 6 (audit-code) | 5+6 together | audit + commit-message in one invocation |\n| Step 7 (commit-message) | (absorbed into 6) | — |\n| Step 8 (release-branch) | Step 7 | unchanged, sequential |\n\n**Total invocations:** 8 → 6 per story.\n\n**Rules:**\n- Steps 3\u002F4\u002F5\u002F8 (kickoff, develop, verify, release) still run sequentially — they require user interaction or branch state.\n- `--fast` does NOT skip any checklist items; it only coalesces steps that are pure read-and-report.\n- Record `epic_cycle.fast_mode: true` in `state.yaml` when this flag is active.\n\n## Handoff\n\nWrite `handoff.next_skill` and `handoff.context` in `state.yaml` when pausing mid-epic.\n\n## Verify\n\n→ verify: `test -f specs\u002Fstate.yaml && test -f specs\u002Fexecution-status.yaml && test -f specs\u002Frelease-plan.yaml && test -d skills\u002Fassess-impact && test -d skills\u002Faudit-code && test -d skills\u002Fsecurity-review`\n\n\n\u003C!-- story: e38s02 -->\n","\u003C!-- story: e20s05 -->\n\n# Build Epic\n\nScope: one story. Called by orchestrate-project Phase 4. Not a replacement for orchestrate-project.\n\nOrchestrates the **build** flow for a single epic: survey → plan tasks → kickoff → TDD → verify → audit → commit → release.\n\n> **HARD GATE** — Set `specs\u002Fstate.yaml` `active_flow: build_epic` and `active_epic: eNN` before starting.\n>\n> **HARD GATE** — Not on `main`\u002F`master` before step 3 (kickoff-branch).\n\n## Nine steps (`epic_cycle` in state.yaml)\n\n| Step | Skill \u002F action |\n|------|----------------|\n| 0 | `security-review` — threat-model epic scope → `specs\u002Fsecurity\u002Fepics\u002F\u003Cid>\u002FTHREAT_MODEL.md` |\n| 1 | `survey-context` — confirm epic + story |\n| 2 | `plan-work` — flesh out story `tasks[]` in `specs\u002Fepics\u002FeNN-slug\u002Fepic.yaml` |\n| 3 | `kickoff-branch` — feature branch + clean baseline |\n| 4 | `develop-tdd` — red-green per task |\n| 5 | `verify-work` — UAT + mechanical gates |\n| 6 | `audit-code` — **non-optional gate** (pass\u002Ffail; fail → loop back to step 4) |\n| 7 | `commit-message` — Conventional Commits draft |\n| 8 | `release-branch` — PR or solo land (supports `--squash-state`) | |\n\n## Process\n\n1. Read `specs\u002Fstate.yaml`, `specs\u002Fexecution-status.yaml`, `specs\u002Frelease-plan.yaml`, active `specs\u002Fepics\u002FeNN-slug\u002Fepic.yaml`.\n   - **On story start (step 1):** Write `started_at` ISO 8601 timestamp to `execution-status.yaml` under the story's key in the `stories:` section. The `bp-timing.sh` script already tracks skill-level timings — this is story-level.\n2. **Step 0 — Threat Model:** Run `security-review` against the epic's scope (read from the epic capsule). Output `specs\u002Fsecurity\u002Fepics\u002F\u003Cepic-id>\u002FTHREAT_MODEL.md` with surface area, vulnerability categories, risk level, and mitigation guidance.\n3. **Assess Impact (Step 2):** Before writing tasks, run `assess-impact --lightweight` on the proposed change. If the risk score exceeds 7, gate — require a `grill-me` session. Write the impact report to `specs\u002FIMPACT-\u003Cepic>-\u003Cstory>.md`. For net-new code with no existing dependents, skip.\n4. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`.\n5. **BCP Plus (Step 2, optional):** When the epic capsule carries a `bcp_plus_breakdown` (13-dimension sizing), also carry it into `state.yaml` as `epic_cycle.bcp_plus`. The breakdown maps each of the 13 dimensions to an integer count. NFR dimensions (11–13) that are N\u002FA per the NFR Gate may be set to 0.\n6. If `epic_cycle.step` missing, set to `1`.\n6. Run **only the current step** (resume mode) unless user asked for full auto-run.\n7. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts\u002Fbp-yaml-set.sh` if available).\n8. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts\u002Fsync-status-from-epics.sh`.\n   - **On story complete (step 8):** Write `completed_at` ISO 8601 timestamp to `execution-status.yaml` under the same story key. Format:\n\n     ```yaml\n     stories:\n       e01s01:\n         status: done\n         started_at: \"2026-07-12T16:00:00-03:00\"\n         completed_at: \"2026-07-12T18:45:00-03:00\"\n     ```\n9. **Traceability refresh:** Before step 8 (release-branch), run `bash scripts\u002Ftrace-stories.sh` to regenerate `specs\u002Ftraceability-matrix.json`, `specs\u002FTRACEABILITY_LATEST.md`, and the `specs\u002Fcodebase-wiki\u002F` OKF bundle. Surface dark\u002Forphan\u002Fstale findings for the just-built epic in your verify summary. If `scripts\u002Ftrace-stories.sh` is missing or fails, note \"trace skipped\" and continue — trace failure must be visible, not silent (blocking is gate-trace's job, e38s06).\n\n9b. **OKF wiki refresh (e39s08):** Before step 8, run maintain-wiki INGEST to refresh the OKF wiki bundle:\n   ```bash\n   bash scripts\u002Fdecompose-conventions.sh\n   bash scripts\u002Fgenerate-agent-guide.sh\n   ```\n   If any script is missing or fails, note \"OKF wiki refresh skipped\" and continue.\n   This is non-blocking — stale concepts are caught by LINT in verify-work Phase 3.\n\n### Step 6 — audit-code gate (non-optional)\n\nAfter step 5 (verify-work) completes successfully, step 6 runs `audit-code` automatically in `--gate` mode:\n\n1. **Run audit:** Invoke `audit-code --gate` on the complete diff for this story.\n2. **Pass (exit 0):** All checklist sections pass → run `bash scripts\u002Flib\u002Fassert-epic-gate.sh advance` to mechanically confirm the audit pass, then advance to step 7 (commit-message). Record `epic_cycle.audit_result: pass` in `state.yaml`.\n3. **Fail (exit 1):** One or more checklist sections fail → **reset `epic_cycle.current_step` to `4`** (develop-tdd) and add the failing section IDs to `completed_steps` as `\"1,2,3,4,5,6(fail: ...)\"`. Record `epic_cycle.audit_result: fail` in `state.yaml`. Do NOT advance past step 6 until audit passes.\n4. **Audit artifact:** Full audit report saved to `specs\u002Fverifications\u002FAUDIT-\u003Cepic>-\u003Cstory>.md` regardless of pass\u002Ffail, for reviewer traceability.\n5. **Enforce F.I.R.S.T:** After audit-code passes, run `enforce-first --quick` on new\u002Fmodified tests. Append F.I.R.S.T violations (if any) to the audit report. Failing F.I.R.S.T criteria trigger the same loop-back to step 4.\n\n## --fast mode\n\nCoalesces read-and-report steps to reduce token overhead. Activate with `build-epic --fast`.\n\n| Normal | --fast | Change |\n|--------|--------|--------|\n| Step 1 (survey-context) | 1+2 together | survey + plan in one invocation |\n| Step 2 (plan-work) | (absorbed into 1) | — |\n| Step 3 (kickoff-branch) | Step 2 | unchanged, sequential |\n| Step 4 (develop-tdd) | Step 3 | unchanged, sequential |\n| Step 5 (verify-work) | Step 4 | unchanged, sequential |\n| Step 6 (audit-code) | 5+6 together | audit + commit-message in one invocation |\n| Step 7 (commit-message) | (absorbed into 6) | — |\n| Step 8 (release-branch) | Step 7 | unchanged, sequential |\n\n**Total invocations:** 8 → 6 per story.\n\n**Rules:**\n- Steps 3\u002F4\u002F5\u002F8 (kickoff, develop, verify, release) still run sequentially — they require user interaction or branch state.\n- `--fast` does NOT skip any checklist items; it only coalesces steps that are pure read-and-report.\n- Record `epic_cycle.fast_mode: true` in `state.yaml` when this flag is active.\n\n## Handoff\n\nWrite `handoff.next_skill` and `handoff.context` in `state.yaml` when pausing mid-epic.\n\n## Verify\n\n→ verify: `test -f specs\u002Fstate.yaml && test -f specs\u002Fexecution-status.yaml && test -f specs\u002Frelease-plan.yaml && test -d skills\u002Fassess-impact && test -d skills\u002Faudit-code && test -d skills\u002Fsecurity-review`\n\n\n\u003C!-- story: e38s02 -->\n",{"name":5,"model":28,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".copilot\u002Fskills\u002Fbuild-epic",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add danielvm-git\u002Fbigpowers --skill build-epic",{"tool":59,"command":60},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill build-epic",{"tool":62,"command":63},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill build-epic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.copilot\u002Fskills\u002Fbuild-epic\u002FSKILL.md",true,[],[68,88,95,123,146,167],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"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",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,83,84,85,86,27,87],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","never",{"skillNo":89,"name":90,"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":91,"categories":92,"keywords":93,"publishedAt":39},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[94,85],"negative path",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":104,"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",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000002","文档处理",[105,106,107,108,109,110,111,112,113,114,25,115,116,117,28,118,119,120,121,122],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","when","minimal","bold","integrity","organize","sync","directory","guides",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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",[],[130,131,132,114,133,25,134,135,136,137,28,138,139,140,141,142,143,115,144,145],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"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",[],[153,154,155,156,157,158,159,160,161,162,163,114,164,27,130,28,165,166],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"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":184,"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",[173,176,181],{"categoryNo":174,"categoryName":175,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":182,"categoryName":183,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000033","数据分析师",[185,186,187,30,188,189,190,191,192,28,193,32,194,33,195,196,197,144,198,199],"dashboard","visual","visual dashboard","artifacts","http","plans","planning","panel","start","opencode","browser","api","architecture","project status","http api"]