[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JVWN3HQSCF19GZK60DWVB":3,"skill-same:01M71JVWN3HQSCF19GZK60DWVB":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},"01M71JVWN3HQSCF19GZK60DWVB","using-bigpowers",null,"One-time bootstrap that introduces the bigpowers skills system, the PMBOK lifecycle arc, and tells you which skill to call first for your situation. Use when starting with bigpowers for the first time, when user asks \"where do I start?\", or when the skills system needs to be explained.","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.qwen\u002Fskills\u002Fusing-bigpowers\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"using bigpowers","for","user","first","with","bootstrap","one","use","call","lifecycle","system","do","arc","sonnet","start","which skill","you","when","time","which","2026-11-10 10:12:30",false,"---\nname: using-bigpowers\nmodel: sonnet\ndescription: \"One-time bootstrap that introduces the bigpowers skills system, the PMBOK lifecycle arc, and tells you which skill to call first for your situation. Use when starting with bigpowers for the first time, when user asks \\\"where do I start?\\\", or when the skills system needs to be explained.\"\n---\n\n# Using bigpowers\n> **HARD GATE** — **HARD GATE** — This skill is the entry point. Do NOT skip it when onboarding new users or starting a new session. It establishes the bigpowers methodology, lifecycle phases, and conventions.\n\n\nWelcome to **bigpowers** — a lifecycle of agent skills for production-ready, TDD-driven software by solo developers. The live catalog and its count are generated in [`SKILL-INDEX.md`](..\u002F..\u002FSKILL-INDEX.md); never hardcode the number here.\n\n## Install\n\n```bash\nnpx bigpowers setup           # one-shot setup\nnpm install -g bigpowers       # global install\nbigpowers setup                # sync skills + link to your tools\n```\n\nFrom source: `git clone` → `bash scripts\u002Finstall.sh`. Package: [bigpowers on npm](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fbigpowers).\n\n**Reach tools:** **Cline** — native AGENTS.md reader (no extension). **Aider** — opt-in `.aider.conf.yml` with `read: AGENTS.md` ([Aider-AI\u002Faider](https:\u002F\u002Fgithub.com\u002FAider-AI\u002Faider)). **Codex CLI** — optional `.codex\u002Fconfig.toml` via seed-conventions; global `~\u002F.codex\u002FAGENTS.md` from install.sh.\n\n## What bigpowers is\n\nA curated set of skills organized around the PMBOK developer lifecycle. Each skill does one thing. Skills reference each other by name only — low coupling, high cohesion. All written output goes to `specs\u002F` at your project root.\n\n## The lifecycle at a glance\n\nSee orchestrate-project for the canonical 6-phase lifecycle.\n\n```\nBOOTSTRAP   using-bigpowers (this skill, first time only)\n              ↓\nDISCOVER    survey-context → research-first → elaborate-spec\n              ↓\nDESIGN      model-domain \u002F define-language \u002F grill-me \u002F deepen-architecture \u002F design-interface\n              ↓\nPLAN        scope-work → slice-tasks → plan-work \u002F plan-refactor\n              ↓\nINITIATE    kickoff-branch → guard-git \u002F hook-commits \u002F seed-conventions\n              ↓\nSPIKE?      spike-prototype → (feeds back to plan-work)\n              ↓\nEXECUTE     develop-tdd + enforce-first ←→ delegate-task \u002F dispatch-agents \u002F execute-plan\n              ↓\nVERIFY      run-evals → verify-work\n              ↓\nHARDEN      wire-observability (any phase)\n              ↓\nBUG?        investigate-bug → diagnose-root → validate-fix\n              ↓\nREVIEW      audit-code → request-review → respond-review\n              ↓\nINTEGRATE   commit-message → release-branch\n              ↓\nSUSTAIN     inspect-quality \u002F organize-workspace (ongoing)\n\nUTILITY     terse-mode \u002F craft-skill \u002F edit-document (any phase)\n```\n\n## Where to start\n\n| Your situation | First skill to call |\n|---------------|---------------------|\n| Greenfield project, nothing set up | `seed-conventions` |\n| Existing project, new task | `survey-context` |\n| Vague idea that needs shaping | `elaborate-spec` |\n| Plan exists, ready to implement | `kickoff-branch` → `develop-tdd` |\n| Bug to fix | `investigate-bug` |\n| Code ready for review | `audit-code` |\n| Shipping a feature | `commit-message` → `release-branch` |\n| Solo dev, PRs feel heavy | Enable `profiles\u002Fsolo-git.md` → `specs\u002FWORKFLOW-solo-git.md` → land via `scripts\u002Fland-branch.sh` |\n\n## Solo Git profile\n\nIf you work alone and do not want PR ceremony every task:\n\n1. Read [profiles\u002Fsolo-git.md](..\u002F..\u002Fprofiles\u002Fsolo-git.md).\n2. Register with `compose-workflow` → `specs\u002FWORKFLOW-solo-git.md`.\n3. Ship with `release-branch` in **solo-local** mode (`land-branch.sh`), not `gh pr create`.\n\nYou still use worktrees, protected `main`, and verification gates — only the integrate step changes.\n\n## YAML cockpit and dashboard\n\nOperational source of truth:\n\n- `specs\u002Fstate.yaml` — session, active epic\u002Fstory, handoff\n- `specs\u002Frelease-plan.yaml` — release index and epic list\n- `specs\u002Fepics\u002FeNN-*.yaml` — stories and tasks with `verify`\n- `specs\u002Fexecution-status.yaml` — done\u002Fpending per story\n\nStart the HTTP dashboard with `visual-dashboard` → `GET \u002Fapi\u002Fstatus?projectDir=\u003Cabs>` and `GET \u002Fcockpit.html` for a read-only PM view.\n\n## Key conventions\n\n- **specs\u002F is your memory.** All domain docs, plans, and investigation outputs go in `specs\u002F` at your project root.\n- **Integrate:** team default is `gh pr` (team-pr); solo profile uses `land-branch.sh`. Never create GitHub issues from skills — use local Markdown files instead.\n- **One skill, one thing.** If you're unsure which skill to call, call `survey-context` — it reads your current state and recommends the next step.\n- **verify: every step.** Every epic task must have `verify: \u003Crunnable command>`. Evidence over claims.\n- **The full catalog is auto-generated.** See `SKILL-INDEX.md`; find skills with `search-skills`.\n\n## After this\n\nCall `survey-context` to read your project's current state and get a personalized recommendation for where to go next.\n\n\n\n\u003C!-- story: e03s02 -->\n","# Using bigpowers\n> **HARD GATE** — **HARD GATE** — This skill is the entry point. Do NOT skip it when onboarding new users or starting a new session. It establishes the bigpowers methodology, lifecycle phases, and conventions.\n\n\nWelcome to **bigpowers** — a lifecycle of agent skills for production-ready, TDD-driven software by solo developers. The live catalog and its count are generated in [`SKILL-INDEX.md`](..\u002F..\u002FSKILL-INDEX.md); never hardcode the number here.\n\n## Install\n\n```bash\nnpx bigpowers setup           # one-shot setup\nnpm install -g bigpowers       # global install\nbigpowers setup                # sync skills + link to your tools\n```\n\nFrom source: `git clone` → `bash scripts\u002Finstall.sh`. Package: [bigpowers on npm](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fbigpowers).\n\n**Reach tools:** **Cline** — native AGENTS.md reader (no extension). **Aider** — opt-in `.aider.conf.yml` with `read: AGENTS.md` ([Aider-AI\u002Faider](https:\u002F\u002Fgithub.com\u002FAider-AI\u002Faider)). **Codex CLI** — optional `.codex\u002Fconfig.toml` via seed-conventions; global `~\u002F.codex\u002FAGENTS.md` from install.sh.\n\n## What bigpowers is\n\nA curated set of skills organized around the PMBOK developer lifecycle. Each skill does one thing. Skills reference each other by name only — low coupling, high cohesion. All written output goes to `specs\u002F` at your project root.\n\n## The lifecycle at a glance\n\nSee orchestrate-project for the canonical 6-phase lifecycle.\n\n```\nBOOTSTRAP   using-bigpowers (this skill, first time only)\n              ↓\nDISCOVER    survey-context → research-first → elaborate-spec\n              ↓\nDESIGN      model-domain \u002F define-language \u002F grill-me \u002F deepen-architecture \u002F design-interface\n              ↓\nPLAN        scope-work → slice-tasks → plan-work \u002F plan-refactor\n              ↓\nINITIATE    kickoff-branch → guard-git \u002F hook-commits \u002F seed-conventions\n              ↓\nSPIKE?      spike-prototype → (feeds back to plan-work)\n              ↓\nEXECUTE     develop-tdd + enforce-first ←→ delegate-task \u002F dispatch-agents \u002F execute-plan\n              ↓\nVERIFY      run-evals → verify-work\n              ↓\nHARDEN      wire-observability (any phase)\n              ↓\nBUG?        investigate-bug → diagnose-root → validate-fix\n              ↓\nREVIEW      audit-code → request-review → respond-review\n              ↓\nINTEGRATE   commit-message → release-branch\n              ↓\nSUSTAIN     inspect-quality \u002F organize-workspace (ongoing)\n\nUTILITY     terse-mode \u002F craft-skill \u002F edit-document (any phase)\n```\n\n## Where to start\n\n| Your situation | First skill to call |\n|---------------|---------------------|\n| Greenfield project, nothing set up | `seed-conventions` |\n| Existing project, new task | `survey-context` |\n| Vague idea that needs shaping | `elaborate-spec` |\n| Plan exists, ready to implement | `kickoff-branch` → `develop-tdd` |\n| Bug to fix | `investigate-bug` |\n| Code ready for review | `audit-code` |\n| Shipping a feature | `commit-message` → `release-branch` |\n| Solo dev, PRs feel heavy | Enable `profiles\u002Fsolo-git.md` → `specs\u002FWORKFLOW-solo-git.md` → land via `scripts\u002Fland-branch.sh` |\n\n## Solo Git profile\n\nIf you work alone and do not want PR ceremony every task:\n\n1. Read [profiles\u002Fsolo-git.md](..\u002F..\u002Fprofiles\u002Fsolo-git.md).\n2. Register with `compose-workflow` → `specs\u002FWORKFLOW-solo-git.md`.\n3. Ship with `release-branch` in **solo-local** mode (`land-branch.sh`), not `gh pr create`.\n\nYou still use worktrees, protected `main`, and verification gates — only the integrate step changes.\n\n## YAML cockpit and dashboard\n\nOperational source of truth:\n\n- `specs\u002Fstate.yaml` — session, active epic\u002Fstory, handoff\n- `specs\u002Frelease-plan.yaml` — release index and epic list\n- `specs\u002Fepics\u002FeNN-*.yaml` — stories and tasks with `verify`\n- `specs\u002Fexecution-status.yaml` — done\u002Fpending per story\n\nStart the HTTP dashboard with `visual-dashboard` → `GET \u002Fapi\u002Fstatus?projectDir=\u003Cabs>` and `GET \u002Fcockpit.html` for a read-only PM view.\n\n## Key conventions\n\n- **specs\u002F is your memory.** All domain docs, plans, and investigation outputs go in `specs\u002F` at your project root.\n- **Integrate:** team default is `gh pr` (team-pr); solo profile uses `land-branch.sh`. Never create GitHub issues from skills — use local Markdown files instead.\n- **One skill, one thing.** If you're unsure which skill to call, call `survey-context` — it reads your current state and recommends the next step.\n- **verify: every step.** Every epic task must have `verify: \u003Crunnable command>`. Evidence over claims.\n- **The full catalog is auto-generated.** See `SKILL-INDEX.md`; find skills with `search-skills`.\n\n## After this\n\nCall `survey-context` to read your project's current state and get a personalized recommendation for where to go next.\n\n\n\n\u003C!-- story: e03s02 -->\n",{"name":5,"model":32,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".qwen\u002Fskills\u002Fusing-bigpowers",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 using-bigpowers",{"tool":59,"command":60},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill using-bigpowers",{"tool":62,"command":63},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill using-bigpowers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fusing-bigpowers\u002FSKILL.md",true,[],[68,88,95,122,145,165],{"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,20,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,26,36,115,116,32,117,118,119,120,121],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","minimal","bold","integrity","organize","sync","directory","guides",{"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":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",[],[129,130,131,114,132,26,133,134,135,136,32,137,138,139,140,141,142,36,143,144],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"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",[],[152,153,154,155,156,157,158,159,160,161,23,114,162,20,129,32,163,164],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","ci pipeline setup","git","workflows",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":182,"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",[171,174,179],{"categoryNo":172,"categoryName":173,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":175,"categoryName":176,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":180,"categoryName":181,"taxonomyType":177,"taxonomyTypeDesc":178},"01JBSEEDCAT000000000000033","数据分析师",[183,184,185,186,187,188,189,190,191,32,33,192,193,194,195,196,197,143,198,199],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","release","opencode","plan","browser","api","architecture","project status","http api"]