[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A09031PZ4ZYAP3QTF3KAER":3,"skill-same:01M7A09031PZ4ZYAP3QTF3KAER":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7A09031PZ4ZYAP3QTF3KAER","create-prd",null,"Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-skills\u002Fpm-execution\u002Fskills\u002Fcreate-prd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-prd\ndescription: \"Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.\"\n---\n\n# Create a Product Requirements Document\n\n## Purpose\n\nYou are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.\n\n## Context\n\nA well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.\n\n## Instructions\n\n1. **Gather Information**: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.\n\n2. **Think Step by Step**: Before writing, analyze:\n   - What problem are we solving?\n   - Who are we solving it for?\n   - How will we measure success?\n   - What are our constraints and assumptions?\n\n3. **Apply the PRD Template**: Create a document with these 8 sections:\n\n   **1. Summary** (2-3 sentences)\n   - What is this document about?\n\n   **2. Contacts**\n   - Name, role, and comment for key stakeholders\n\n   **3. Background**\n   - Context: What is this initiative about?\n   - Why now? Has something changed?\n   - Is this something that just recently became possible?\n\n   **4. Objective**\n   - What's the objective? Why does it matter?\n   - How will it benefit the company and customers?\n   - How does it align with vision and strategy?\n   - Key Results: How will you measure success? (Use SMART OKR format)\n\n   **5. Market Segment(s)**\n   - For whom are we building this?\n   - What constraints exist?\n   - Note: Markets are defined by people's problems\u002Fjobs, not demographics\n\n   **6. Value Proposition(s)**\n   - What customer jobs\u002Fneeds are we addressing?\n   - What will customers gain?\n   - Which pains will they avoid?\n   - Which problems do we solve better than competitors?\n   - Consider the Value Curve framework\n\n   **7. Solution**\n   - 7.1 UX\u002FPrototypes (wireframes, user flows)\n   - 7.2 Key Features (detailed feature descriptions)\n   - 7.3 Technology (optional, only if relevant)\n   - 7.4 Assumptions (what we believe but haven't proven)\n\n   **8. Release**\n   - How long could it take?\n   - What goes in the first version vs. future versions?\n   - Avoid exact dates; use relative timeframes\n\n4. **Use Accessible Language**: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.\n\n5. **Structure Output**: Present the PRD as a well-formatted markdown document with clear headings and sections.\n\n6. **Save the Output**: If the PRD is substantial (which it will be), save it as a markdown document in the format: `PRD-[product-name].md`\n\n## Notes\n\n- Be specific and data-driven where possible\n- Link each section back to the overall strategy\n- Flag assumptions clearly so the team can validate them\n- Keep the document concise but complete\n\n---\n\n### Further Reading\n\n- [How to Write a Product Requirements Document? The Best PRD Template.](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fprd-template)\n- [A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fai-prd-template)\n","# Create a Product Requirements Document\n\n## Purpose\n\nYou are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.\n\n## Context\n\nA well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.\n\n## Instructions\n\n1. **Gather Information**: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.\n\n2. **Think Step by Step**: Before writing, analyze:\n   - What problem are we solving?\n   - Who are we solving it for?\n   - How will we measure success?\n   - What are our constraints and assumptions?\n\n3. **Apply the PRD Template**: Create a document with these 8 sections:\n\n   **1. Summary** (2-3 sentences)\n   - What is this document about?\n\n   **2. Contacts**\n   - Name, role, and comment for key stakeholders\n\n   **3. Background**\n   - Context: What is this initiative about?\n   - Why now? Has something changed?\n   - Is this something that just recently became possible?\n\n   **4. Objective**\n   - What's the objective? Why does it matter?\n   - How will it benefit the company and customers?\n   - How does it align with vision and strategy?\n   - Key Results: How will you measure success? (Use SMART OKR format)\n\n   **5. Market Segment(s)**\n   - For whom are we building this?\n   - What constraints exist?\n   - Note: Markets are defined by people's problems\u002Fjobs, not demographics\n\n   **6. Value Proposition(s)**\n   - What customer jobs\u002Fneeds are we addressing?\n   - What will customers gain?\n   - Which pains will they avoid?\n   - Which problems do we solve better than competitors?\n   - Consider the Value Curve framework\n\n   **7. Solution**\n   - 7.1 UX\u002FPrototypes (wireframes, user flows)\n   - 7.2 Key Features (detailed feature descriptions)\n   - 7.3 Technology (optional, only if relevant)\n   - 7.4 Assumptions (what we believe but haven't proven)\n\n   **8. Release**\n   - How long could it take?\n   - What goes in the first version vs. future versions?\n   - Avoid exact dates; use relative timeframes\n\n4. **Use Accessible Language**: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.\n\n5. **Structure Output**: Present the PRD as a well-formatted markdown document with clear headings and sections.\n\n6. **Save the Output**: If the PRD is substantial (which it will be), save it as a markdown document in the format: `PRD-[product-name].md`\n\n## Notes\n\n- Be specific and data-driven where possible\n- Link each section back to the overall strategy\n- Flag assumptions clearly so the team can validate them\n- Keep the document concise but complete\n\n---\n\n### Further Reading\n\n- [How to Write a Product Requirements Document? The Best PRD Template.](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fprd-template)\n- [A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fai-prd-template)\n",{"name":5,"description":7},"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fpm-skills\u002Fpm-execution\u002Fskills\u002Fcreate-prd","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi","https:\u002F\u002Fgithub.com\u002Fkongnakornna","http:\u002F\u002Fcmoniot.trueddns.com:52160","Technical Skills and Expertise\r\nLanguages and Frameworks\r\nFrontend: HTML, JavaScript, TypeScript, React, Vue, Angular, Next.js\r\nBackend: Node.js,Python,Golang","2026-10-06 23:01:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kongnakornna\u002Fgolangapi --skill create-prd",{"tool":38,"command":39},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill create-prd",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill create-prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-skills\u002Fpm-execution\u002Fskills\u002Fcreate-prd\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7A0M4JKY4DEDRP1CBHT00WV","tb-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7A0KZ5HRAQAAT2KXR6146Q7","tb-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-test-driven-development\u002FSKILL.md",[],[],{"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":74,"publishedAt":19},"01M7A0KW92W3F18E2MRP8H62P2","tb-subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-subagent-driven-development\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7A0KKYQCHYYRHA5J5BAP24M","tb-scrutinize","Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler\u002Fmore elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on \u002Ftb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-scrutinize\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7A0KFDR1V3RW7SW1XNHP82P","tb-requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-requesting-code-review\u002FSKILL.md",[],[]]