[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CXKJWVD48QD2QJ6WQTCPBA":3,"skill-same:01M6CXKJWVD48QD2QJ6WQTCPBA":101},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6CXKJWVD48QD2QJ6WQTCPBA","feature-forge",null,"Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.","eric861129\u002FSKILLS_All-in-one","eric861129","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F74950944?v=4","01M6CXHDYEYRPFGGV4EFXCSYCF","ChiYu-Huang","01M6CXHE2J5CN1EBTY0FKV3ZKW",52,"MIT","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FCollaboration & Project Management\u002Ffeature-forge\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"forge","feature forge","format","writing","matrices","requirements","acceptance criteria","specification","document","master","use","spec","design","https","produce","acceptance","planning","test","workflow","github","2026-11-10 10:12:30",false,"---\nname: feature-forge\ndescription: Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists. Use when defining new features, gathering requirements, or writing specifications. Invoke for feature definition, requirements gathering, user stories, EARS format specs, PRDs, acceptance criteria, or requirement matrices.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: workflow\n  triggers: requirements, specification, feature definition, user stories, EARS, planning\n  role: specialist\n  scope: design\n  output-format: document\n  related-skills: fullstack-guardian, spec-miner, test-master\n---\n\n# Feature Forge\n\nRequirements specialist conducting structured workshops to define comprehensive feature specifications.\n\n## Role Definition\n\nOperate with two perspectives:\n- **PM Hat**: Focused on user value, business goals, success metrics\n- **Dev Hat**: Focused on technical feasibility, security, performance, edge cases\n\n## When to Use This Skill\n\n- Defining new features from scratch\n- Gathering comprehensive requirements\n- Writing specifications in EARS format\n- Creating acceptance criteria\n- Planning implementation TODO lists\n\n## Core Workflow\n\n1. **Discover** - Use `AskUserQuestions` to understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level).\n2. **Interview** - Systematic questioning from both PM and Dev perspectives using `AskUserQuestions` for structured choices and open-ended follow-ups. Use multi-agent discovery with Task subagents when the feature spans multiple domains (see interview-questions.md for guidance).\n3. **Document** - Write EARS-format requirements\n4. **Validate** - Use `AskUserQuestions` to review acceptance criteria with stakeholder, presenting key trade-offs as structured choices\n5. **Plan** - Create implementation checklist\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| EARS Syntax | `references\u002Fears-syntax.md` | Writing functional requirements |\n| Interview Questions | `references\u002Finterview-questions.md` | Gathering requirements |\n| Specification Template | `references\u002Fspecification-template.md` | Writing final spec document |\n| Acceptance Criteria | `references\u002Facceptance-criteria.md` | Given\u002FWhen\u002FThen format |\n| Pre-Discovery Subagents | `references\u002Fpre-discovery-subagents.md` | Multi-domain features needing front-loaded context |\n\n## Constraints\n\n### MUST DO\n- Use `AskUserQuestions` tool for structured elicitation (priority, scope, format choices)\n- Use open-ended questions only when choices cannot be predetermined\n- Conduct thorough interview before writing spec\n- Use EARS format for all functional requirements\n- Include non-functional requirements (performance, security)\n- Provide testable acceptance criteria\n- Include implementation TODO checklist\n- Ask for clarification on ambiguous requirements\n\n### MUST NOT DO\n- Output interview questions as plain text when `AskUserQuestions` can provide structured options\n- Generate spec without conducting interview\n- Accept vague requirements (\"make it fast\")\n- Skip security considerations\n- Forget error handling requirements\n- Write untestable acceptance criteria\n\n## Output Templates\n\nThe final specification must include:\n1. Overview and user value\n2. Functional requirements (EARS format)\n3. Non-functional requirements\n4. Acceptance criteria (Given\u002FWhen\u002FThen)\n5. Error handling table\n6. Implementation TODO checklist\n\n**Inline EARS format examples** (load `references\u002Fears-syntax.md` for full syntax):\n```\nWhen \u003Ctrigger>, the \u003Csystem> shall \u003Cresponse>.\nWhere \u003Cfeature> is active, the \u003Csystem> shall \u003Cbehaviour>.\nThe \u003Csystem> shall \u003Caction> within \u003Cmeasure>.\n```\n\n**Inline acceptance criteria example** (load `references\u002Facceptance-criteria.md` for full format):\n```\nGiven a registered user is on the login page,\nWhen they submit valid credentials,\nThen they are redirected to the dashboard within 2 seconds.\n```\n\nSave as: `specs\u002F{feature_name}.spec.md`\n","# Feature Forge\n\nRequirements specialist conducting structured workshops to define comprehensive feature specifications.\n\n## Role Definition\n\nOperate with two perspectives:\n- **PM Hat**: Focused on user value, business goals, success metrics\n- **Dev Hat**: Focused on technical feasibility, security, performance, edge cases\n\n## When to Use This Skill\n\n- Defining new features from scratch\n- Gathering comprehensive requirements\n- Writing specifications in EARS format\n- Creating acceptance criteria\n- Planning implementation TODO lists\n\n## Core Workflow\n\n1. **Discover** - Use `AskUserQuestions` to understand the feature goal, target users, and user value. Present structured choices where possible (e.g., user types, priority level).\n2. **Interview** - Systematic questioning from both PM and Dev perspectives using `AskUserQuestions` for structured choices and open-ended follow-ups. Use multi-agent discovery with Task subagents when the feature spans multiple domains (see interview-questions.md for guidance).\n3. **Document** - Write EARS-format requirements\n4. **Validate** - Use `AskUserQuestions` to review acceptance criteria with stakeholder, presenting key trade-offs as structured choices\n5. **Plan** - Create implementation checklist\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| EARS Syntax | `references\u002Fears-syntax.md` | Writing functional requirements |\n| Interview Questions | `references\u002Finterview-questions.md` | Gathering requirements |\n| Specification Template | `references\u002Fspecification-template.md` | Writing final spec document |\n| Acceptance Criteria | `references\u002Facceptance-criteria.md` | Given\u002FWhen\u002FThen format |\n| Pre-Discovery Subagents | `references\u002Fpre-discovery-subagents.md` | Multi-domain features needing front-loaded context |\n\n## Constraints\n\n### MUST DO\n- Use `AskUserQuestions` tool for structured elicitation (priority, scope, format choices)\n- Use open-ended questions only when choices cannot be predetermined\n- Conduct thorough interview before writing spec\n- Use EARS format for all functional requirements\n- Include non-functional requirements (performance, security)\n- Provide testable acceptance criteria\n- Include implementation TODO checklist\n- Ask for clarification on ambiguous requirements\n\n### MUST NOT DO\n- Output interview questions as plain text when `AskUserQuestions` can provide structured options\n- Generate spec without conducting interview\n- Accept vague requirements (\"make it fast\")\n- Skip security considerations\n- Forget error handling requirements\n- Write untestable acceptance criteria\n\n## Output Templates\n\nThe final specification must include:\n1. Overview and user value\n2. Functional requirements (EARS format)\n3. Non-functional requirements\n4. Acceptance criteria (Given\u002FWhen\u002FThen)\n5. Error handling table\n6. Implementation TODO checklist\n\n**Inline EARS format examples** (load `references\u002Fears-syntax.md` for full syntax):\n```\nWhen \u003Ctrigger>, the \u003Csystem> shall \u003Cresponse>.\nWhere \u003Cfeature> is active, the \u003Csystem> shall \u003Cbehaviour>.\nThe \u003Csystem> shall \u003Caction> within \u003Cmeasure>.\n```\n\n**Inline acceptance criteria example** (load `references\u002Facceptance-criteria.md` for full format):\n```\nGiven a registered user is on the login page,\nWhen they submit valid credentials,\nThen they are redirected to the dashboard within 2 seconds.\n```\n\nSave as: `specs\u002F{feature_name}.spec.md`\n",{"name":5,"license":15,"metadata":49,"description":7},{"role":50,"scope":36,"author":51,"domain":42,"version":52,"triggers":53,"output-format":32,"related-skills":54},"specialist","https:\u002F\u002Fgithub.com\u002FJeffallan","1.1.0","requirements, specification, feature definition, user stories, EARS, planning","fullstack-guardian, spec-miner, test-master","main","cbdd44aae21131521c09e42762e36178c790eacf","public\u002FSKILLS\u002FCollaboration & Project Management\u002Ffeature-forge",13,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one","http:\u002F\u002Fhuangchiyu.com\u002FSKILLS_All-in-one\u002F","https:\u002F\u002Fgithub.com\u002Feric861129","https:\u002F\u002Fhuangchiyu.com\u002FChiYu-Blog\u002F","開發工程師，專注於 C#／.NET 系統現代化、AI-assisted engineering、開源工具與技術寫作。","2026-04-16 14:28:14",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add eric861129\u002FSKILLS_All-in-one --skill feature-forge",{"tool":71,"command":72},"bunx","bunx skills add eric861129\u002FSKILLS_All-in-one --skill feature-forge",{"tool":74,"command":75},"pnpm","pnpm dlx skills add eric861129\u002FSKILLS_All-in-one --skill feature-forge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FCollaboration & Project Management\u002Ffeature-forge\u002FSKILL.md",true,[79,85,89,93,97],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Facceptance-criteria.md","REFERENCE","参考文档",2984,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FCollaboration & Project Management\u002Ffeature-forge\u002Freferences\u002Facceptance-criteria.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fears-syntax.md",2699,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FCollaboration & Project Management\u002Ffeature-forge\u002Freferences\u002Fears-syntax.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Finterview-questions.md",5492,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FCollaboration & Project Management\u002Ffeature-forge\u002Freferences\u002Finterview-questions.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fpre-discovery-subagents.md",2084,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FCollaboration & Project Management\u002Ffeature-forge\u002Freferences\u002Fpre-discovery-subagents.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fspecification-template.md",2592,"https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FCollaboration & Project Management\u002Ffeature-forge\u002Freferences\u002Fspecification-template.md",[102,129,161,187,210,230],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":109,"publishedAt":44},"01M6CZ1WR3KNVTKSWH4GNWT646","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fwhat-if-oracle\u002FSKILL.md",[108],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[110,111,112,113,40,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128],"oracle","what if oracle","go","run","ux","futures","risk","analysis","explore","decision","branch","question","read","write","idea","exploration","options","stress-test","strategies",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":147,"publishedAt":44},"01M6CZ1QHGJE91A95MSN5EK5Q9","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fvenue-templates\u002FSKILL.md",[135,138,141,142],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[148,149,150,151,152,153,154,155,156,157,122,123,158,159,160,29],"templates","venue templates","research","guidelines","NeurIPS","ICML","LaTeX","science","Bash","access","edit","proposals","Academic",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":171,"publishedAt":44},"01M6CZ1KBQD2E5RTFB3BGVX7CD","the-fool","Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fthe-fool\u002FSKILL.md",[167,168],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":169,"categoryName":170,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000030","开发工程师",[172,173,112,42,174,113,175,176,24,177,178,179,180,181,159,182,183,184,185,186],"the fool","review","architecture","code","audit","devil","team","designer","reviewer","challenge","stress test","evidence","expert","poke","ideas",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":196,"publishedAt":44},"01M6CZ1ES826S7P1X3333E40TA","scientific-writing","Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA\u002FAMA\u002FVancouver), figures\u002Ftables, reporting guidelines (CONSORT\u002FSTROBE\u002FPRISMA), for research papers and journal submissions.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fscientific-writing\u002FSKILL.md",[193,194,195],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},[27,197,151,198,199,200,201,202,156,203,122,123,158,34,204,205,206,207,208,209],"scientific writing","core","reporting","deep research","Citations","Outlines","tool","never","structure","deep","full","stage","prisma",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":44},"01M6CZ1B2JGJTB9FRD0TW4RXXE","scientific-brainstorming","Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fscientific-brainstorming\u002FSKILL.md",[216],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[218,219,150,220,40,221,222,223,34,224,225,226,125,227,228,208,229],"brainstorming","scientific brainstorming","sessions","data","hypothesis","open","ideation","creative","do","connections","research ideation","generation",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":242,"publishedAt":44},"01M6CZ16JG8N7A2ZX04BGE8J2Y","research-lookup","Look up current research information using the Parallel Chat API (primary) or Perplexity sonar-pro-search (academic paper searches). Automatically routes queries to the best backend. Use for finding papers, gathering research data, and verifying scientific information.","https:\u002F\u002Fgithub.com\u002Feric861129\u002FSKILLS_All-in-one\u002Fblob\u002Fmain\u002Fpublic\u002FSKILLS\u002FWriting & Research\u002Fresearch-lookup\u002FSKILL.md",[236,239,240,241],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":169,"categoryName":170,"taxonomyType":145,"taxonomyTypeDesc":146},[150,243,244,245,221,246,247,156,248,249,122,123,158,34,250,251,252,253,254,160],"lookup","research lookup","search","perplexity","api","parallel","openrouter","backend","up","look","queries","chat"]