[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EN85XS71YA5YP37R8BK9VP":3,"skill-same:01M6EN85XS71YA5YP37R8BK9VP":121},{"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":31,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6EN85XS71YA5YP37R8BK9VP","project-planning",null,"Generate initial project planning documents (PVS, ADR, Tech Spec, Roadmap) from a project concept description. Use when starting a new project, when docs\u002Fplanning\u002F contains placeholder files, or when user requests project planning document generation.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"project","planning","project planning","user","document generation","tech","generation","document","files","roadmap","use","spec","tech spec","adr","new project","generate","documents","placeholder","docs","2026-11-10 10:12:30",false,"---\nname: project-planning\ndescription: >\n  Generate initial project planning documents (PVS, ADR, Tech Spec, Roadmap) from a project\n  concept description. Use when starting a new project, when docs\u002Fplanning\u002F contains placeholder\n  files, or when user requests project planning document generation.\nversion: 1.0.0\n---\n\n# Project Planning Skill\n\nGenerate four essential planning documents to guide AI-assisted development. These documents\nmaintain context coherence across coding sessions and prevent architectural drift.\n\n## When to Use This Skill\n\n- User describes a project concept and asks for planning documents\n- Files in `docs\u002Fplanning\u002F` show \"Awaiting Generation\" status\n- User invokes `\u002Fplan` command with project description\n- Starting development on a new feature requiring architectural decisions\n\n## Output Documents\n\n| Document | Location | Purpose |\n|----------|----------|---------|\n| Project Vision & Scope | `docs\u002Fplanning\u002Fproject-vision.md` | What & Why - problem, solution, scope |\n| Technical Spec | `docs\u002Fplanning\u002Ftech-spec.md` | How - architecture, data model, APIs |\n| Development Roadmap | `docs\u002Fplanning\u002Froadmap.md` | When - phased implementation plan |\n| Architecture Decision Record | `docs\u002Fplanning\u002Fadr\u002Fadr-001-*.md` | Key technical decisions with rationale |\n\n## Generation Process\n\n### Step 1: Gather Project Context\n\nBefore generating, collect:\n1. **Project description** from user input\n2. **Technical constraints** from `pyproject.toml` and existing code\n3. **Cookiecutter choices** reflected in project structure\n\n### Step 2: Generate Documents in Order\n\nGenerate documents sequentially, as later documents reference earlier ones:\n\n1. **Project Vision & Scope** - Establishes what we're building and why\n2. **Architecture Decision Record** - Key technical choices based on PVS\n3. **Technical Implementation Spec** - Detailed how-to based on ADRs\n4. **Development Roadmap** - Implementation plan based on all above\n\n### Step 3: Expert Review via Consensus\n\nAfter generating each document, use the zen-mcp-server consensus tool to get expert review:\n\n```\nUse mcp__zen__consensus with gemini-3-pro-preview to review:\n\n\"Review this [document type] for sufficiency to begin development.\n\nEvaluate:\n1. SPECIFICITY: Are requirements concrete enough to implement?\n2. COMPLETENESS: Are all critical sections filled with project-specific content?\n3. FEASIBILITY: Are timelines and technical choices realistic?\n4. CLARITY: Can a developer understand what to build from this?\n5. GAPS: What critical information is missing?\n\nRespond with:\n- READY: Document is sufficient to begin work\n- NEEDS REVISION: [List specific improvements required]\n\nDocument content:\n[paste document content]\"\n```\n\n**Review each document in order**:\n1. PVS → Must be READY before generating ADR\n2. ADR → Must be READY before generating Tech Spec\n3. Tech Spec → Must be READY before generating Roadmap\n4. Roadmap → Must be READY before completing\n\nIf any document NEEDS REVISION, incorporate feedback and re-review before proceeding.\n\n### Step 4: Validate and Cross-Reference\n\nAfter all documents pass review:\n- Ensure documents reference each other correctly\n- Verify technical choices are consistent across documents\n- Flag any assumptions needing user validation\n- Run validation script if available\n\n## Document Generation Guidelines\n\n### All Documents\n\n- **Be specific**: Use concrete technologies, versions, and measurable criteria\n- **No boilerplate**: Every section must contain project-specific information\n- **Under 1000 words**: Dense information, minimal prose\n- **Markdown format**: Use headers, bullets, tables for structure\n- **Include TL;DR**: 2-3 sentence summary at top of each document\n\n### Project Vision & Scope (PVS)\n\nUse template: `templates\u002Fpvs-template.md`\n\nFocus on:\n- Problem being solved and user impact\n- Core capabilities (3-5 max for MVP)\n- Explicit scope boundaries (in vs out)\n- Measurable success metrics\n\n### Architecture Decision Record (ADR)\n\nUse template: `templates\u002Fadr-template.md`\n\nCreate ADR for:\n- Database\u002Fstorage choice\n- Authentication strategy\n- API design approach\n- Key framework decisions\n- Any choice expensive to reverse\n\nFormat: `adr-001-{decision-slug}.md`\n\n### Technical Implementation Spec\n\nUse template: `templates\u002Ftech-spec-template.md`\n\nInclude:\n- Complete tech stack with versions\n- Component architecture diagram (ASCII)\n- Data model with schemas\n- API endpoints specification\n- Security requirements\n- Error handling approach\n\n### Development Roadmap\n\nUse template: `templates\u002Froadmap-template.md`\n\nStructure as:\n- Phase 0: Foundation (environment, CI\u002FCD)\n- Phase 1: MVP Core (essential features)\n- Phase 2: Enhancement (additional features)\n- Phase 3: Polish (testing, documentation)\n\nEach phase needs:\n- Clear deliverables\n- Success criteria (testable)\n- Estimated duration\n- Dependencies\n\n## Pre-Filling from Project Context\n\nWhen generating, incorporate known information:\n\n```python\n# From pyproject.toml \u002F cookiecutter context\npython_version = \"3.12\"\nproject_name = \"Fragrance Rater\"\nproject_slug = \"fragrance_rater\"\ncli_framework = \"Click\"\ncontainerization = \"Docker\"\n```\n\n## Quality Checklist\n\nBefore completing generation:\n\n- [ ] All four documents created in `docs\u002Fplanning\u002F`\n- [ ] Each document has TL;DR section\n- [ ] No \"[TODO]\" or \"[TBD]\" placeholders remain\n- [ ] Documents cross-reference each other\n- [ ] Technical choices are consistent\n- [ ] Success criteria are measurable\n- [ ] Scope boundaries are explicit\n- [ ] At least one ADR created\n\n## Templates Reference\n\nTemplates are in `templates\u002F` directory:\n- `pvs-template.md` - Project Vision & Scope structure\n- `adr-template.md` - Architecture Decision Record structure\n- `tech-spec-template.md` - Technical Spec structure\n- `roadmap-template.md` - Development Roadmap structure\n\n## Detailed Guidance\n\nFor comprehensive documentation on each document type, see `reference\u002F` directory:\n- `reference\u002Fdocument-guide.md` - Full guidance for all document types\n- `reference\u002Fprompting-patterns.md` - How to use documents during development\n\n## After Generation\n\nInstruct user to:\n1. Review each document for accuracy\n2. Validate assumptions marked with `[ ]`\n3. Adjust timelines in roadmap if needed\n4. Commit documents to version control\n5. Reference documents in future development sessions\n\n## Example Usage\n\nWhen user says: \"I want to build a CLI tool for managing personal finances...\"\n\n### Generation Flow with Consensus Review\n\n1. **Generate PVS**\n   - Read `templates\u002Fpvs-template.md`\n   - Generate `docs\u002Fplanning\u002Fproject-vision.md` with finance CLI specifics\n   - **Review**: `mcp__zen__consensus` with gemini-3-pro-preview → READY or revise\n\n2. **Generate ADR**\n   - Read `templates\u002Fadr-template.md`\n   - Generate `docs\u002Fplanning\u002Fadr\u002Fadr-001-database-choice.md` for SQLite decision\n   - **Review**: `mcp__zen__consensus` with gemini-3-pro-preview → READY or revise\n\n3. **Generate Tech Spec**\n   - Read `templates\u002Ftech-spec-template.md`\n   - Generate `docs\u002Fplanning\u002Ftech-spec.md` with Python\u002FClick\u002FSQLite stack\n   - **Review**: `mcp__zen__consensus` with gemini-3-pro-preview → READY or revise\n\n4. **Generate Roadmap**\n   - Read `templates\u002Froadmap-template.md`\n   - Generate `docs\u002Fplanning\u002Froadmap.md` with phased implementation\n   - **Review**: `mcp__zen__consensus` with gemini-3-pro-preview → READY or revise\n\n5. **Final Validation**\n   - Run `scripts\u002Fvalidate-planning-docs.py`\n   - Summarize what was created and review outcomes\n   - List next steps for beginning development\n\n### Consensus Review Prompt Template\n\n```\nmcp__zen__consensus with gemini-3-pro-preview:\n\nReview this Project Vision & Scope document for Fragrance Rater.\n\nEVALUATION CRITERIA:\n1. SPECIFICITY - Can a developer implement from these requirements?\n2. COMPLETENESS - All sections filled with project-specific content?\n3. FEASIBILITY - Realistic scope for the described constraints?\n4. CLARITY - Unambiguous success criteria and scope boundaries?\n5. GAPS - Any critical missing information?\n\nRESPOND:\n- READY: Sufficient to proceed to next document\n- NEEDS REVISION: [Specific improvements with examples]\n\nDOCUMENT:\n[Full document content here]\n```\n\n### MCP Server Requirement\n\nThis skill requires the zen-mcp-server for consensus review.\nIf not available, skip Step 3 and proceed with manual review.\n\nConfiguration: Ensure `mcp__zen__consensus` tool is accessible.\n","# Project Planning Skill\n\nGenerate four essential planning documents to guide AI-assisted development. These documents\nmaintain context coherence across coding sessions and prevent architectural drift.\n\n## When to Use This Skill\n\n- User describes a project concept and asks for planning documents\n- Files in `docs\u002Fplanning\u002F` show \"Awaiting Generation\" status\n- User invokes `\u002Fplan` command with project description\n- Starting development on a new feature requiring architectural decisions\n\n## Output Documents\n\n| Document | Location | Purpose |\n|----------|----------|---------|\n| Project Vision & Scope | `docs\u002Fplanning\u002Fproject-vision.md` | What & Why - problem, solution, scope |\n| Technical Spec | `docs\u002Fplanning\u002Ftech-spec.md` | How - architecture, data model, APIs |\n| Development Roadmap | `docs\u002Fplanning\u002Froadmap.md` | When - phased implementation plan |\n| Architecture Decision Record | `docs\u002Fplanning\u002Fadr\u002Fadr-001-*.md` | Key technical decisions with rationale |\n\n## Generation Process\n\n### Step 1: Gather Project Context\n\nBefore generating, collect:\n1. **Project description** from user input\n2. **Technical constraints** from `pyproject.toml` and existing code\n3. **Cookiecutter choices** reflected in project structure\n\n### Step 2: Generate Documents in Order\n\nGenerate documents sequentially, as later documents reference earlier ones:\n\n1. **Project Vision & Scope** - Establishes what we're building and why\n2. **Architecture Decision Record** - Key technical choices based on PVS\n3. **Technical Implementation Spec** - Detailed how-to based on ADRs\n4. **Development Roadmap** - Implementation plan based on all above\n\n### Step 3: Expert Review via Consensus\n\nAfter generating each document, use the zen-mcp-server consensus tool to get expert review:\n\n```\nUse mcp__zen__consensus with gemini-3-pro-preview to review:\n\n\"Review this [document type] for sufficiency to begin development.\n\nEvaluate:\n1. SPECIFICITY: Are requirements concrete enough to implement?\n2. COMPLETENESS: Are all critical sections filled with project-specific content?\n3. FEASIBILITY: Are timelines and technical choices realistic?\n4. CLARITY: Can a developer understand what to build from this?\n5. GAPS: What critical information is missing?\n\nRespond with:\n- READY: Document is sufficient to begin work\n- NEEDS REVISION: [List specific improvements required]\n\nDocument content:\n[paste document content]\"\n```\n\n**Review each document in order**:\n1. PVS → Must be READY before generating ADR\n2. ADR → Must be READY before generating Tech Spec\n3. Tech Spec → Must be READY before generating Roadmap\n4. Roadmap → Must be READY before completing\n\nIf any document NEEDS REVISION, incorporate feedback and re-review before proceeding.\n\n### Step 4: Validate and Cross-Reference\n\nAfter all documents pass review:\n- Ensure documents reference each other correctly\n- Verify technical choices are consistent across documents\n- Flag any assumptions needing user validation\n- Run validation script if available\n\n## Document Generation Guidelines\n\n### All Documents\n\n- **Be specific**: Use concrete technologies, versions, and measurable criteria\n- **No boilerplate**: Every section must contain project-specific information\n- **Under 1000 words**: Dense information, minimal prose\n- **Markdown format**: Use headers, bullets, tables for structure\n- **Include TL;DR**: 2-3 sentence summary at top of each document\n\n### Project Vision & Scope (PVS)\n\nUse template: `templates\u002Fpvs-template.md`\n\nFocus on:\n- Problem being solved and user impact\n- Core capabilities (3-5 max for MVP)\n- Explicit scope boundaries (in vs out)\n- Measurable success metrics\n\n### Architecture Decision Record (ADR)\n\nUse template: `templates\u002Fadr-template.md`\n\nCreate ADR for:\n- Database\u002Fstorage choice\n- Authentication strategy\n- API design approach\n- Key framework decisions\n- Any choice expensive to reverse\n\nFormat: `adr-001-{decision-slug}.md`\n\n### Technical Implementation Spec\n\nUse template: `templates\u002Ftech-spec-template.md`\n\nInclude:\n- Complete tech stack with versions\n- Component architecture diagram (ASCII)\n- Data model with schemas\n- API endpoints specification\n- Security requirements\n- Error handling approach\n\n### Development Roadmap\n\nUse template: `templates\u002Froadmap-template.md`\n\nStructure as:\n- Phase 0: Foundation (environment, CI\u002FCD)\n- Phase 1: MVP Core (essential features)\n- Phase 2: Enhancement (additional features)\n- Phase 3: Polish (testing, documentation)\n\nEach phase needs:\n- Clear deliverables\n- Success criteria (testable)\n- Estimated duration\n- Dependencies\n\n## Pre-Filling from Project Context\n\nWhen generating, incorporate known information:\n\n```python\n# From pyproject.toml \u002F cookiecutter context\npython_version = \"3.12\"\nproject_name = \"Fragrance Rater\"\nproject_slug = \"fragrance_rater\"\ncli_framework = \"Click\"\ncontainerization = \"Docker\"\n```\n\n## Quality Checklist\n\nBefore completing generation:\n\n- [ ] All four documents created in `docs\u002Fplanning\u002F`\n- [ ] Each document has TL;DR section\n- [ ] No \"[TODO]\" or \"[TBD]\" placeholders remain\n- [ ] Documents cross-reference each other\n- [ ] Technical choices are consistent\n- [ ] Success criteria are measurable\n- [ ] Scope boundaries are explicit\n- [ ] At least one ADR created\n\n## Templates Reference\n\nTemplates are in `templates\u002F` directory:\n- `pvs-template.md` - Project Vision & Scope structure\n- `adr-template.md` - Architecture Decision Record structure\n- `tech-spec-template.md` - Technical Spec structure\n- `roadmap-template.md` - Development Roadmap structure\n\n## Detailed Guidance\n\nFor comprehensive documentation on each document type, see `reference\u002F` directory:\n- `reference\u002Fdocument-guide.md` - Full guidance for all document types\n- `reference\u002Fprompting-patterns.md` - How to use documents during development\n\n## After Generation\n\nInstruct user to:\n1. Review each document for accuracy\n2. Validate assumptions marked with `[ ]`\n3. Adjust timelines in roadmap if needed\n4. Commit documents to version control\n5. Reference documents in future development sessions\n\n## Example Usage\n\nWhen user says: \"I want to build a CLI tool for managing personal finances...\"\n\n### Generation Flow with Consensus Review\n\n1. **Generate PVS**\n   - Read `templates\u002Fpvs-template.md`\n   - Generate `docs\u002Fplanning\u002Fproject-vision.md` with finance CLI specifics\n   - **Review**: `mcp__zen__consensus` with gemini-3-pro-preview → READY or revise\n\n2. **Generate ADR**\n   - Read `templates\u002Fadr-template.md`\n   - Generate `docs\u002Fplanning\u002Fadr\u002Fadr-001-database-choice.md` for SQLite decision\n   - **Review**: `mcp__zen__consensus` with gemini-3-pro-preview → READY or revise\n\n3. **Generate Tech Spec**\n   - Read `templates\u002Ftech-spec-template.md`\n   - Generate `docs\u002Fplanning\u002Ftech-spec.md` with Python\u002FClick\u002FSQLite stack\n   - **Review**: `mcp__zen__consensus` with gemini-3-pro-preview → READY or revise\n\n4. **Generate Roadmap**\n   - Read `templates\u002Froadmap-template.md`\n   - Generate `docs\u002Fplanning\u002Froadmap.md` with phased implementation\n   - **Review**: `mcp__zen__consensus` with gemini-3-pro-preview → READY or revise\n\n5. **Final Validation**\n   - Run `scripts\u002Fvalidate-planning-docs.py`\n   - Summarize what was created and review outcomes\n   - List next steps for beginning development\n\n### Consensus Review Prompt Template\n\n```\nmcp__zen__consensus with gemini-3-pro-preview:\n\nReview this Project Vision & Scope document for Fragrance Rater.\n\nEVALUATION CRITERIA:\n1. SPECIFICITY - Can a developer implement from these requirements?\n2. COMPLETENESS - All sections filled with project-specific content?\n3. FEASIBILITY - Realistic scope for the described constraints?\n4. CLARITY - Unambiguous success criteria and scope boundaries?\n5. GAPS - Any critical missing information?\n\nRESPOND:\n- READY: Sufficient to proceed to next document\n- NEEDS REVISION: [Specific improvements with examples]\n\nDOCUMENT:\n[Full document content here]\n```\n\n### MCP Server Requirement\n\nThis skill requires the zen-mcp-server for consensus review.\nIf not available, skip Step 3 and proceed with manual review.\n\nConfiguration: Ensure `mcp__zen__consensus` tool is accessible.\n",{"name":5,"version":56,"description":57},"1.0.0","Generate initial project planning documents (PVS, ADR, Tech Spec, Roadmap) from a project concept description. Use when starting a new project, when docs\u002Fplanning\u002F contains placeholder files, or when user requests project planning document generation.\n","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill project-planning",{"tool":73,"command":74},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill project-planning",{"tool":76,"command":77},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill project-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002FSKILL.md",true,[81,87,91,97,101,105,109,113,117],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"reference\u002Fdocument-guide.md","REFERENCE","参考文档",6771,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Freference\u002Fdocument-guide.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"reference\u002Fprompting-patterns.md",5259,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Freference\u002Fprompting-patterns.md",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fvalidate-planning-docs.py","SCRIPT","脚本",7880,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Fscripts\u002Fvalidate-planning-docs.py",{"path":98,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":99,"sourceHtmlUrl":100},"skill-report.json",34073,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Fskill-report.json",{"path":102,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":103,"sourceHtmlUrl":104},"templates\u002Fadr-template.md",2108,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Ftemplates\u002Fadr-template.md",{"path":106,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":107,"sourceHtmlUrl":108},"templates\u002Fpvs-template.md",1630,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Ftemplates\u002Fpvs-template.md",{"path":110,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":111,"sourceHtmlUrl":112},"templates\u002Froadmap-template.md",4097,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Ftemplates\u002Froadmap-template.md",{"path":114,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":115,"sourceHtmlUrl":116},"templates\u002Ftech-spec-template.md",4160,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Ftemplates\u002Ftech-spec-template.md",{"path":118,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":119,"sourceHtmlUrl":120},"workflows\u002Fsynthesize.md",6932,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fbyronwilliamscpa\u002Fproject-planning\u002Fworkflows\u002Fsynthesize.md",[122,132,142,151,157,164],{"skillNo":123,"name":124,"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":125,"categories":126,"keywords":128,"publishedAt":51},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[127],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[129,130,131],"model","model hierarchy","model hierarchy skill",{"skillNo":133,"name":134,"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":135,"categories":136,"keywords":138,"publishedAt":51},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[137],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[139,140,141],"MCP","zoom","zoom mcp",{"skillNo":143,"name":144,"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":145,"categories":146,"keywords":147,"publishedAt":51},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[148,149,150,140],"sdk","zoom apps sdk","apps",{"skillNo":152,"name":153,"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":154,"categories":155,"keywords":156,"publishedAt":51},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[153],{"skillNo":158,"name":159,"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":160,"categories":161,"keywords":163,"publishedAt":51},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[162],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[159],{"skillNo":165,"name":166,"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":167,"categories":168,"keywords":169,"publishedAt":51},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[166]]