[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JM2ESA67A7F4MB56XFKKWH":3,"skill-same:01M6JM2ESA67A7F4MB56XFKKWH":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":13,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6JM2ESA67A7F4MB56XFKKWH","subagent-driven-development",null,"Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent for each task with code review between tasks.","superhealth\u002Fskills-hub","superhealth","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6292112?v=4","01M6JA6E7F21BYK5W3E4P270TT","01M6JA6EC0W8MPHKDJVBZDSEZ0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fdoyajin174\u002Fsubagent-driven-development\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"development","driven","subagent driven development","subagent","edit","for","with","fresh","plans","task","superpowers","use","session","code review","write","read","Bash","code","tasks","review","2026-11-10 10:12:30",false,"---\nname: subagent-driven-development\ndescription: Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent for each task with code review between tasks.\nallowed-tools: Read, Glob, Grep, Bash, Edit, Write, Task\nlicense: MIT\nmetadata:\n  author: obra\u002Fsuperpowers\n  version: \"1.0\"\n---\n\n# Subagent-Driven Development\n\n구현 계획을 서브에이전트를 통해 실행하는 오케스트레이션 스킬입니다.\n\n## When to Use\n\n다음 조건을 모두 만족할 때:\n\n```\n✅ 완성된 구현 계획이 있음\n✅ 대부분 독립적인 태스크들\n✅ 현재 세션에서 진행해야 함\n```\n\n그렇지 않으면:\n- 수동 실행\n- 또는 parallel-session \"executing-plans\" 사용\n\n## Execution Loop\n\n각 태스크에 대해:\n\n```\n1. Implementer 서브에이전트 디스패치\n   - 전체 태스크 텍스트와 컨텍스트 제공\n\n2. 명확화 질문 답변\n   - 구현 시작 전 모든 질문에 답변\n\n3. Implementer 실행\n   - 테스팅, 커밋, 셀프 리뷰\n\n4. Spec Compliance Review\n   - 원래 요구사항 대비 검증\n\n5. Code Quality Review\n   - 구현 표준 승인\n\n6. 문제 발견 시 수정 루프\n   - 같은 implementer가 수정하고 재제출\n\n7. 완료 마킹 → 다음 태스크\n```\n\n## Review Flow\n\n```\n                    ┌─────────────────┐\n                    │  Implementer    │\n                    │  (서브에이전트) │\n                    └────────┬────────┘\n                             │\n                             ▼\n                    ┌─────────────────┐\n                    │ Spec Compliance │◄──┐\n                    │     Review      │   │ 실패 시\n                    └────────┬────────┘   │ 수정 요청\n                             │            │\n                    통과     ▼            │\n                    ┌─────────────────┐   │\n                    │  Code Quality   │───┘\n                    │     Review      │\n                    └────────┬────────┘\n                             │\n                    통과     ▼\n                    ┌─────────────────┐\n                    │    Complete     │\n                    └─────────────────┘\n```\n\n## Red Flags\n\n```\n❌ 리뷰 단계 건너뛰기\n❌ 미수정 이슈가 있는데 진행\n❌ Spec 리뷰 전에 Code Quality 리뷰 시작\n❌ 서브에이전트 질문에 불완전한 답변\n```\n\n## Task Dispatch Template\n\n```markdown\n## Task\n[태스크 설명]\n\n## Context\n- 관련 파일: [파일 목록]\n- 의존성: [선행 태스크]\n- 제약: [제약 조건]\n\n## Acceptance Criteria\n- [ ] [기준 1]\n- [ ] [기준 2]\n\n## Test Requirements\n- 필요한 테스트 케이스\n```\n\n## Review Templates\n\n### Spec Compliance Review\n\n```markdown\n## Requirement Checklist\n- [ ] 기능 요구사항 충족\n- [ ] 엣지 케이스 처리\n- [ ] 에러 핸들링\n- [ ] 성능 요구사항\n\n## Verdict\n✅ PASS \u002F ❌ NEEDS_REVISION\n\n## Issues (있을 경우)\n- [이슈 설명]\n```\n\n### Code Quality Review\n\n```markdown\n## Quality Checklist\n- [ ] 코드 스타일 준수\n- [ ] 테스트 커버리지\n- [ ] 명명 규칙\n- [ ] 문서화\n\n## Verdict\n✅ PASS \u002F ❌ NEEDS_REVISION\n\n## Suggestions\n- [개선 제안]\n```\n\n## Final Review\n\n모든 태스크 완료 후:\n\n```\n1. 전체 변경사항 리뷰\n2. 통합 테스트 실행\n3. 문서 업데이트 확인\n4. 머지 준비 완료 확인\n```\n","# Subagent-Driven Development\n\n구현 계획을 서브에이전트를 통해 실행하는 오케스트레이션 스킬입니다.\n\n## When to Use\n\n다음 조건을 모두 만족할 때:\n\n```\n✅ 완성된 구현 계획이 있음\n✅ 대부분 독립적인 태스크들\n✅ 현재 세션에서 진행해야 함\n```\n\n그렇지 않으면:\n- 수동 실행\n- 또는 parallel-session \"executing-plans\" 사용\n\n## Execution Loop\n\n각 태스크에 대해:\n\n```\n1. Implementer 서브에이전트 디스패치\n   - 전체 태스크 텍스트와 컨텍스트 제공\n\n2. 명확화 질문 답변\n   - 구현 시작 전 모든 질문에 답변\n\n3. Implementer 실행\n   - 테스팅, 커밋, 셀프 리뷰\n\n4. Spec Compliance Review\n   - 원래 요구사항 대비 검증\n\n5. Code Quality Review\n   - 구현 표준 승인\n\n6. 문제 발견 시 수정 루프\n   - 같은 implementer가 수정하고 재제출\n\n7. 완료 마킹 → 다음 태스크\n```\n\n## Review Flow\n\n```\n                    ┌─────────────────┐\n                    │  Implementer    │\n                    │  (서브에이전트) │\n                    └────────┬────────┘\n                             │\n                             ▼\n                    ┌─────────────────┐\n                    │ Spec Compliance │◄──┐\n                    │     Review      │   │ 실패 시\n                    └────────┬────────┘   │ 수정 요청\n                             │            │\n                    통과     ▼            │\n                    ┌─────────────────┐   │\n                    │  Code Quality   │───┘\n                    │     Review      │\n                    └────────┬────────┘\n                             │\n                    통과     ▼\n                    ┌─────────────────┐\n                    │    Complete     │\n                    └─────────────────┘\n```\n\n## Red Flags\n\n```\n❌ 리뷰 단계 건너뛰기\n❌ 미수정 이슈가 있는데 진행\n❌ Spec 리뷰 전에 Code Quality 리뷰 시작\n❌ 서브에이전트 질문에 불완전한 답변\n```\n\n## Task Dispatch Template\n\n```markdown\n## Task\n[태스크 설명]\n\n## Context\n- 관련 파일: [파일 목록]\n- 의존성: [선행 태스크]\n- 제약: [제약 조건]\n\n## Acceptance Criteria\n- [ ] [기준 1]\n- [ ] [기준 2]\n\n## Test Requirements\n- 필요한 테스트 케이스\n```\n\n## Review Templates\n\n### Spec Compliance Review\n\n```markdown\n## Requirement Checklist\n- [ ] 기능 요구사항 충족\n- [ ] 엣지 케이스 처리\n- [ ] 에러 핸들링\n- [ ] 성능 요구사항\n\n## Verdict\n✅ PASS \u002F ❌ NEEDS_REVISION\n\n## Issues (있을 경우)\n- [이슈 설명]\n```\n\n### Code Quality Review\n\n```markdown\n## Quality Checklist\n- [ ] 코드 스타일 준수\n- [ ] 테스트 커버리지\n- [ ] 명명 규칙\n- [ ] 문서화\n\n## Verdict\n✅ PASS \u002F ❌ NEEDS_REVISION\n\n## Suggestions\n- [개선 제안]\n```\n\n## Final Review\n\n모든 태스크 완료 후:\n\n```\n1. 전체 변경사항 리뷰\n2. 통합 테스트 실행\n3. 문서 업데이트 확인\n4. 머지 준비 완료 확인\n```\n",{"name":5,"license":14,"metadata":48,"description":7,"allowed-tools":51},{"author":49,"version":50},"obra\u002Fsuperpowers","1.0","Read, Glob, Grep, Bash, Edit, Write, Task","master","08cc2532077058aa50e6e18f54695bc256c88152","skills\u002Fdoyajin174\u002Fsubagent-driven-development","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub","https:\u002F\u002Fgithub.com\u002Fsuperhealth","java engineer","2026-04-06 22:07:23",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add superhealth\u002Fskills-hub --skill subagent-driven-development",{"tool":65,"command":66},"bunx","bunx skills add superhealth\u002Fskills-hub --skill subagent-driven-development",{"tool":68,"command":69},"pnpm","pnpm dlx skills add superhealth\u002Fskills-hub --skill subagent-driven-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fdoyajin174\u002Fsubagent-driven-development\u002FSKILL.md",true,[73],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"skill-report.json","REFERENCE","参考文档",10338,"https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fdoyajin174\u002Fsubagent-driven-development\u002Fskill-report.json",[80,108,134,147,162,186],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":89,"publishedAt":43},"01M6MC9F3WHV8S8FZ2W4TRB0FE","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fzhanlincui\u002Fvercel-react-best-practices\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[90,91,92,93,94,95,40,96,97,98,99,100,101,102,41,103,104,105,106,107],"react","vercel react best practices","best practices","vercel","react best practices","data fetching","triggers","pages","next","patterns","refactoring","data","Optimization","guidelines","react components","components","performance","writing",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":118,"publishedAt":43},"01M6MB8KWE1Q5A5KERR7RFTQWP","vue-testing-best-practices","Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-testing-best-practices\u002FSKILL.md",[114,117],{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},[119,120,121,92,122,123,124,125,126,34,127,99,128,129,28,130,131,132,133],"vue testing best practices","testing best practices","vue","testing","testing patterns","js","e2e","vitest","component","test","mocking","utils","e2e testing","github","playwright",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":43},"01M6MB8GK06M6GA4KVYNDV1BZP","vue-router-best-practices","Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-router-best-practices\u002FSKILL.md",[140],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},[92,121,142,143,144,99,145,146,127,132],"router","vue router best practices","route","navigation","lifecycle",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":43},"01M6MB8DQF21TZMQ9XC3745ERW","vue-pinia-best-practices","Pinia stores, state management patterns, store setup, and reactivity with stores.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-pinia-best-practices\u002FSKILL.md",[153],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},[155,156,121,92,29,157,99,158,159,160,161,132],"vue pinia best practices","pinia","store","management","state","state management","setup",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":177,"publishedAt":43},"01M6MB8A7MC08747J9TV4GWQ9A","vue-options-api-best-practices","Vue 3 Options API style (data(), methods, this context). Each reference shows Options API solution only.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-options-api-best-practices\u002FSKILL.md",[168,169,172],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":173,"categoryName":174,"taxonomyType":175,"taxonomyTypeDesc":176},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[121,178,179,180,92,181,182,183,184,101,132,185],"options","vue options api best practices","api","methods","reference","only","context","style",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":43},"01M6MB85ZTQC24Q04X49MM4YXN","vue-development-guides","A collection of best practices and tips for developing applications using Vue.js. This skill MUST be apply when developing, refactoring or reviewing Vue.js or Nuxt projects.","https:\u002F\u002Fgithub.com\u002Fsuperhealth\u002Fskills-hub\u002Fblob\u002Fmaster\u002Fskills\u002Fvuejs-ai\u002Fvue-development-guides\u002FSKILL.md",[192],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},[23,121,194,195,132,196,197,28,198,199,200,124,100,201,202,92],"guides","vue development guides","tips","apply","project","nuxt","projects","collection","applications"]