[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HGYBGWXHT6ZVRVF0V4EG7":3,"skill-same:01M71HGYBGWXHT6ZVRVF0V4EG7":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},"01M71HGYBGWXHT6ZVRVF0V4EG7","audit-plan",null,"Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY\u002FNOT READY verdict before engagement begins. Use when a new project arrives, when adapting a foreign plan, or before running seed-conventions on an unfamiliar codebase.","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\u002F.codex\u002Fskills\u002Faudit-plan\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"plan","audit","audit plan","codebase","principles","evaluate","verdict","engagement","gaps","use","produce","running","new project","sonnet","seed","project plan","when","new","project","ready","2026-11-10 10:12:30",false,"---\nname: audit-plan\nmodel: sonnet\ndescription: \"Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY\u002FNOT READY verdict before engagement begins. Use when a new project arrives, when adapting a foreign plan, or before running seed-conventions on an unfamiliar codebase.\"\n---\n\n# Audit Plan\n\n> **HARD GATE** — Do NOT start build skills (kickoff-branch, develop-tdd) until audit-plan returns a READY verdict. A plan missing test commands, scope boundaries, or success criteria will produce drift and rework downstream.\n\nAssess an incoming project plan for alignment with bigpowers principles, identify what's missing, and produce a structured readiness report before any skill execution begins.\n\n## Three lenses\n\n### 1. Principles alignment\n- Are stories vertical slices (not horizontal layers)?\n- Is scope bounded — explicit in_scope + out_of_scope?\n- Are success criteria defined (how do we know we're done)?\n- Are HARD GATE candidates identifiable (critical decision points)?\n- Is there a domain language \u002F ubiquitous terminology?\n\n### 2. Conventions completeness\n- Does `CLAUDE.md` or `AGENTS.md` exist?\n- Does `CONVENTIONS.md` exist?\n- Is the `specs\u002F` directory layout in place?\n- Are commit conventions documented (Conventional Commits)?\n- Is the git workflow mode identified (`solo-git` | `team-pr`)?\n\n### 3. Bigpowers pre-flight (must all be answered before build)\n| Question | Why |\n|----------|-----|\n| What is the **test command**? | `develop-tdd` verify steps require it |\n| What is the **build command**? | `verify-work` mechanical gate |\n| What is the **lint command**? | `audit-code` lint gate |\n| What is the **typecheck command**? | `verify-work` typecheck gate |\n| What **CI platform** is in use? | `wire-ci` configuration |\n| **Solo or team**? | `release-branch` integration mode |\n| Primary **language + framework**? | model routing + conventions |\n| **Greenfield or existing** codebase? | determines whether to run `seed-conventions` or `migrate-spec` first |\n\n## Process\n\n1. **Ingest the plan** — accept a file path, pasted PRD text, or existing `specs\u002F` artifacts. Read `CLAUDE.md` and `CONVENTIONS.md` if present.\n\n2. **Score each lens** — for every item above, mark:\n   - ✅ Present and adequate\n   - ⚠️ Present but incomplete — note what's missing\n   - ❌ Absent\n\n3. **Close gaps conversationally** — for each ❌ or ⚠️, ask one question at a time. Record each answer before moving to the next.\n\n4. **Write `specs\u002FPLAN-AUDIT_LATEST.md`**:\n\n```markdown\n# Plan Audit — \u003Cproject>\n**Date:** YYYY-MM-DD · **Verdict:** READY | NOT READY\n\n## Principles Alignment\n| Check | Status | Note |\n| Vertical slices | ✅ | 4 stories, each shippable |\n| Scope bounded | ⚠️ | in_scope present; out_of_scope missing |\n\n## Conventions Completeness\n| Check | Status | Note |\n\n## Pre-flight Answers\n| Command | Value |\n| test | `npm test` |\n| build | `npm run build` |\n\n## Open Gaps\n- [ ] Add out_of_scope to scope definition (run scope-work)\n- [ ] Create CLAUDE.md (run seed-conventions)\n\n## Verdict\nREADY — proceed with survey-context\nNOT READY — N gaps remain; close before proceeding\n```\n\n5. **Recommend next skill**:\n   - READY → `survey-context`\n   - Needs bootstrapping → `seed-conventions`\n   - Needs spec elaboration → `elaborate-spec`\n   - Has foreign spec format → `migrate-spec`\n   - Plan assumptions need challenging → `grill-me`\n\n## Verify\n\n→ verify: `test -f specs\u002FPLAN-AUDIT_LATEST.md && grep -q Verdict specs\u002FPLAN-AUDIT_LATEST.md`\n","# Audit Plan\n\n> **HARD GATE** — Do NOT start build skills (kickoff-branch, develop-tdd) until audit-plan returns a READY verdict. A plan missing test commands, scope boundaries, or success criteria will produce drift and rework downstream.\n\nAssess an incoming project plan for alignment with bigpowers principles, identify what's missing, and produce a structured readiness report before any skill execution begins.\n\n## Three lenses\n\n### 1. Principles alignment\n- Are stories vertical slices (not horizontal layers)?\n- Is scope bounded — explicit in_scope + out_of_scope?\n- Are success criteria defined (how do we know we're done)?\n- Are HARD GATE candidates identifiable (critical decision points)?\n- Is there a domain language \u002F ubiquitous terminology?\n\n### 2. Conventions completeness\n- Does `CLAUDE.md` or `AGENTS.md` exist?\n- Does `CONVENTIONS.md` exist?\n- Is the `specs\u002F` directory layout in place?\n- Are commit conventions documented (Conventional Commits)?\n- Is the git workflow mode identified (`solo-git` | `team-pr`)?\n\n### 3. Bigpowers pre-flight (must all be answered before build)\n| Question | Why |\n|----------|-----|\n| What is the **test command**? | `develop-tdd` verify steps require it |\n| What is the **build command**? | `verify-work` mechanical gate |\n| What is the **lint command**? | `audit-code` lint gate |\n| What is the **typecheck command**? | `verify-work` typecheck gate |\n| What **CI platform** is in use? | `wire-ci` configuration |\n| **Solo or team**? | `release-branch` integration mode |\n| Primary **language + framework**? | model routing + conventions |\n| **Greenfield or existing** codebase? | determines whether to run `seed-conventions` or `migrate-spec` first |\n\n## Process\n\n1. **Ingest the plan** — accept a file path, pasted PRD text, or existing `specs\u002F` artifacts. Read `CLAUDE.md` and `CONVENTIONS.md` if present.\n\n2. **Score each lens** — for every item above, mark:\n   - ✅ Present and adequate\n   - ⚠️ Present but incomplete — note what's missing\n   - ❌ Absent\n\n3. **Close gaps conversationally** — for each ❌ or ⚠️, ask one question at a time. Record each answer before moving to the next.\n\n4. **Write `specs\u002FPLAN-AUDIT_LATEST.md`**:\n\n```markdown\n# Plan Audit — \u003Cproject>\n**Date:** YYYY-MM-DD · **Verdict:** READY | NOT READY\n\n## Principles Alignment\n| Check | Status | Note |\n| Vertical slices | ✅ | 4 stories, each shippable |\n| Scope bounded | ⚠️ | in_scope present; out_of_scope missing |\n\n## Conventions Completeness\n| Check | Status | Note |\n\n## Pre-flight Answers\n| Command | Value |\n| test | `npm test` |\n| build | `npm run build` |\n\n## Open Gaps\n- [ ] Add out_of_scope to scope definition (run scope-work)\n- [ ] Create CLAUDE.md (run seed-conventions)\n\n## Verdict\nREADY — proceed with survey-context\nNOT READY — N gaps remain; close before proceeding\n```\n\n5. **Recommend next skill**:\n   - READY → `survey-context`\n   - Needs bootstrapping → `seed-conventions`\n   - Needs spec elaboration → `elaborate-spec`\n   - Has foreign spec format → `migrate-spec`\n   - Plan assumptions need challenging → `grill-me`\n\n## Verify\n\n→ verify: `test -f specs\u002FPLAN-AUDIT_LATEST.md && grep -q Verdict specs\u002FPLAN-AUDIT_LATEST.md`\n",{"name":5,"model":32,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".codex\u002Fskills\u002Faudit-plan",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add danielvm-git\u002Fbigpowers --skill audit-plan",{"tool":59,"command":60},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill audit-plan",{"tool":62,"command":63},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill audit-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Faudit-plan\u002FSKILL.md",true,[],[68,89,96,123,145,166],{"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,87,88],"fixture","open","verify","skill verify fail open fixture","skill verify","path","run","for","never",{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":39},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[95,85],"negative path",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":105,"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",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000002","文档处理",[106,107,108,109,110,111,112,113,114,115,28,35,116,117,32,118,119,120,121,122],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","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,115,133,28,134,135,136,137,32,138,139,140,141,142,143,35,37,144],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","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,162,115,163,87,130,32,164,165],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","ci pipeline setup","git","workflows",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":183,"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",[172,175,180],{"categoryNo":173,"categoryName":174,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":176,"categoryName":177,"taxonomyType":178,"taxonomyTypeDesc":179},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":181,"categoryName":182,"taxonomyType":178,"taxonomyTypeDesc":179},"01JBSEEDCAT000000000000033","数据分析师",[184,185,186,187,188,189,190,191,192,32,193,194,195,19,196,197,198,37,199,200],"dashboard","visual","visual dashboard","status","artifacts","http","plans","planning","panel","start","release","opencode","browser","api","architecture","project status","http api"]