[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71H65RN22XAPTHHJXV86MXZ":3,"skill-same:01M71H65RN22XAPTHHJXV86MXZ":64},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M71H65RN22XAPTHHJXV86MXZ","plan-tests",null,"Design a risk-scaled test architecture for an epic before implementation begins. Produces prioritized scenarios, test level distribution, and fixture plans based on TEA and bigpowers principles.","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.cline\u002Fskills\u002Fplan-tests\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"plan tests","tests","plan","implementation","principles","test","scenarios","tea","EPIC","plans","for","risk","opus","architecture","design","distribution","fixture","2026-11-10 10:12:30",false,"---\nname: plan-tests\nmodel: opus\ndescription: \"Design a risk-scaled test architecture for an epic before implementation begins. Produces prioritized scenarios, test level distribution, and fixture plans based on TEA and bigpowers principles.\"\n---\n\n# Plan Tests\n\n> **Spine position:** Between `slice-tasks` and `plan-work` for epics with `risk: P0|P1`. Optional (can be waived in `state.yaml`) for P2\u002FP3.\n\nBridges the gap between slicing and planning by systematically designing the test suite as a first-class system. Produces `specs\u002Ftech-architecture\u002FeNN-TEST_PLAN_LATEST.md`.\n\n## Pre-flight\n- Read `specs\u002Fepics\u002FeNN-*\u002F` story list.\n\n## Core Workflow\n1. **Analyze Epic**: Read sliced stories in the active epic capsule.\n2. **Risk Assessment**: Map behaviors to P0–P3 risk tiers.\n3. **Level Strategy**: Classify each scenario (Unit, Integration, E2E).\n4. **Fixture Design**: Plan factories, network intercepts, mocks (see REFERENCE.md).\n5. **NFR Plan**: Define verifiable commands for Non-Functional Requirements. Skip if `--lite`.\n6. **Publish**: Generate `specs\u002Ftech-architecture\u002FeNN-TEST_PLAN_LATEST.md`.\n\n## Hard Gates & Guardrails\n- **DO NOT** write test code or production code during this skill.\n- Scenario ID format MUST be: `SC-eNNsYY-P{0|1|2|3}-NN`.\n- `plan-work` MUST reference these scenario IDs in its §17 Gherkin acceptance criteria.\n- Default to pushing tests to the lowest possible level.\n\n## Execution Modes\n- `$bmad plan-tests`: Standard execution.\n- `$bmad plan-tests --lite`: Skips NFRs and complex fixture planning.\n\n## Verify\n\n→ verify: `test -f specs\u002Ftech-architecture\u002Fe32-TEST_PLAN_LATEST.md`\n\n## Handoff\n\nGate: READY -> next: plan-work\nWrites: state.yaml handoff.next_skill = plan-work\n\n---\n\n# Plan Tests — Reference\n\n## Test Plan Template (`specs\u002Ftech-architecture\u002FeNN-TEST_PLAN_LATEST.md`)\n\n```markdown\n# Test Design: [eNN-slug]\n\n## 1. Risk Matrix & Scenarios\n| Scenario ID | Behavior Description | Risk | Test Level | Target File\u002FModule |\n|-------------|----------------------|------|------------|--------------------|  \n| SC-P0-01    | Primary checkout     | P0   | Integration | checkout.spec.ts  |\n\n## 2. Fixture Architecture & Isolation\n- Data Factories: (e.g. UserFactory)\n- Network Intercepts: (e.g. MSW handlers)\n- Database State: (e.g. in-memory SQLite)\n\n## 3. NFR Verification\n| NFR Type | Requirement | Verification Command |\n|----------|-------------|----------------------|\n| Perf     | \u003C 200ms     | `npm run test:perf`  |\n\n## 4. Out of Scope\n- [Explicitly excluded testing areas]\n```\n\n## Fixture Planning Guidance\n\n- **Data Factories**: Prefer factory functions over manual object construction.\n- **Network Intercepts**: For frontend integration tests, use tools like Mock Service Worker (MSW) to intercept and mock HTTP requests.\n- **Database State**: For backend tests, use a clean database state per test or an in-memory database to ensure isolation.\n","# Plan Tests\n\n> **Spine position:** Between `slice-tasks` and `plan-work` for epics with `risk: P0|P1`. Optional (can be waived in `state.yaml`) for P2\u002FP3.\n\nBridges the gap between slicing and planning by systematically designing the test suite as a first-class system. Produces `specs\u002Ftech-architecture\u002FeNN-TEST_PLAN_LATEST.md`.\n\n## Pre-flight\n- Read `specs\u002Fepics\u002FeNN-*\u002F` story list.\n\n## Core Workflow\n1. **Analyze Epic**: Read sliced stories in the active epic capsule.\n2. **Risk Assessment**: Map behaviors to P0–P3 risk tiers.\n3. **Level Strategy**: Classify each scenario (Unit, Integration, E2E).\n4. **Fixture Design**: Plan factories, network intercepts, mocks (see REFERENCE.md).\n5. **NFR Plan**: Define verifiable commands for Non-Functional Requirements. Skip if `--lite`.\n6. **Publish**: Generate `specs\u002Ftech-architecture\u002FeNN-TEST_PLAN_LATEST.md`.\n\n## Hard Gates & Guardrails\n- **DO NOT** write test code or production code during this skill.\n- Scenario ID format MUST be: `SC-eNNsYY-P{0|1|2|3}-NN`.\n- `plan-work` MUST reference these scenario IDs in its §17 Gherkin acceptance criteria.\n- Default to pushing tests to the lowest possible level.\n\n## Execution Modes\n- `$bmad plan-tests`: Standard execution.\n- `$bmad plan-tests --lite`: Skips NFRs and complex fixture planning.\n\n## Verify\n\n→ verify: `test -f specs\u002Ftech-architecture\u002Fe32-TEST_PLAN_LATEST.md`\n\n## Handoff\n\nGate: READY -> next: plan-work\nWrites: state.yaml handoff.next_skill = plan-work\n\n---\n\n# Plan Tests — Reference\n\n## Test Plan Template (`specs\u002Ftech-architecture\u002FeNN-TEST_PLAN_LATEST.md`)\n\n```markdown\n# Test Design: [eNN-slug]\n\n## 1. Risk Matrix & Scenarios\n| Scenario ID | Behavior Description | Risk | Test Level | Target File\u002FModule |\n|-------------|----------------------|------|------------|--------------------|  \n| SC-P0-01    | Primary checkout     | P0   | Integration | checkout.spec.ts  |\n\n## 2. Fixture Architecture & Isolation\n- Data Factories: (e.g. UserFactory)\n- Network Intercepts: (e.g. MSW handlers)\n- Database State: (e.g. in-memory SQLite)\n\n## 3. NFR Verification\n| NFR Type | Requirement | Verification Command |\n|----------|-------------|----------------------|\n| Perf     | \u003C 200ms     | `npm run test:perf`  |\n\n## 4. Out of Scope\n- [Explicitly excluded testing areas]\n```\n\n## Fixture Planning Guidance\n\n- **Data Factories**: Prefer factory functions over manual object construction.\n- **Network Intercepts**: For frontend integration tests, use tools like Mock Service Worker (MSW) to intercept and mock HTTP requests.\n- **Database State**: For backend tests, use a clean database state per test or an in-memory database to ensure isolation.\n",{"name":5,"model":31,"description":7},"main","72f5e4c8b43f60cf86b37078ad8cd7e22daf67aa",".cline\u002Fskills\u002Fplan-tests",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add danielvm-git\u002Fbigpowers --skill plan-tests",{"tool":56,"command":57},"bunx","bunx skills add danielvm-git\u002Fbigpowers --skill plan-tests",{"tool":59,"command":60},"pnpm","pnpm dlx skills add danielvm-git\u002Fbigpowers --skill plan-tests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002F.cline\u002Fskills\u002Fplan-tests\u002FSKILL.md",true,[],[65,84,91,121,144,165],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":36},"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",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[35,77,78,79,80,81,82,29,83],"open","verify","skill verify fail open fixture","skill verify","path","run","never",{"skillNo":85,"name":86,"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":87,"categories":88,"keywords":89,"publishedAt":36},"01M71KBE3BKEMKNE0C5DGVDWZH","negative-path","https:\u002F\u002Fgithub.com\u002Fdanielvm-git\u002Fbigpowers\u002Fblob\u002Fmain\u002Fspecs\u002Fverifications\u002Ffixtures\u002Fnegative-path\u002FSKILL.md",[],[90,81],"negative path",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":100,"publishedAt":36},"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",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000002","文档处理",[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"write","write document","document","documents","actionable","technical","methodology","high","bmad","standard","use","when","minimal","bold","sonnet","integrity","organize","sync","directory","guides",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":36},"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",[],[128,129,130,110,131,111,132,133,134,135,115,136,137,138,139,140,141,112,142,143],"observability","wire observability","readiness","commands","development","as","logging","add","instrumentation","at","structured logging","production-readiness","idempotent","phase","project","scripts",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":36},"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",[],[151,152,153,154,155,156,157,158,159,160,161,110,162,29,128,115,163,164],"wire ci","ci","remote","local","pipeline","forge","validation","setup","templates","REST","with","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":36},"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":74,"taxonomyTypeDesc":75},"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,28,189,190,115,191,192,193,21,194,195,32,142,196,197],"dashboard","visual","visual dashboard","status","artifacts","http","planning","panel","start","release","opencode","browser","api","project status","http api"]