[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71B9Q3JWE457FQFK5VG4MN8":3,"skill-same:01M71B9Q3JWE457FQFK5VG4MN8":71},{"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":28,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71B9Q3JWE457FQFK5VG4MN8","technical-research",null,"Research a technology, library, API, or approach to inform an architecture or implementation decision. Use when the user says 'research this technology', 'evaluate this library', or 'investigate this approach'.","superMLdev\u002Fsmart-sdlc","superMLdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214327565?v=4","01M71B92B8VKCZZ0YCSNAJ9CB1","superML.dev","01M71B92BVCWP4F23ANQ0ZKF6S",8,"MIT","https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002F1-analysis\u002Ftechnical-research\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42],"technical research","technical","research","decision","technology","use","when","architecture","api","investigate","evaluate","implementation","library","user","2026-11-10 10:12:30",false,"---\nname: technical-research\ndescription: \"Research a technology, library, API, or approach to inform an architecture or implementation decision. Use when the user says 'research this technology', 'evaluate this library', or 'investigate this approach'.\"\n---\n\n# Technical Research Workflow\n\n## Goal\n\nProduce a structured technical evaluation that gives the team enough information to make a confident build \u002F buy \u002F adopt \u002F reject decision.\n\n---\n\n## Step 1: Define the Research Question\n\nAsk:\n1. What technology, library, or approach are we evaluating?\n2. What problem is it solving?\n3. What are the alternatives we should compare against?\n4. Who will use the decision — architect, developer, or product?\n\n---\n\n## Step 2: Evaluation Dimensions\n\nAssess the technology across:\n\n### Maturity & Ecosystem\n- Version, release cadence, age of project\n- GitHub stars, downloads\u002Fweek, last commit\n- Community size (Stack Overflow, Discord, forums)\n- Commercial backing vs. community-only\n\n### Fit Assessment\n- Does it solve the stated problem? Fully \u002F partially \u002F needs workaround?\n- Known integrations with our current stack\n- License compatibility\n\n### Performance & Scale\n- Benchmark data (if available) or credible community reports\n- Known limits: throughput, latency, memory footprint\n- Scale stories: who uses it at production scale?\n\n### Security\n- CVE history — any critical vulnerabilities in last 2 years?\n- Active security patch cadence\n- Compliance considerations (GDPR, SOC 2, HIPAA, etc.)\n\n### Developer Experience\n- Time to first working example\n- Quality of documentation\n- Local dev setup complexity\n\n### Cost\n- Licence cost (open source, commercial, seat-based, usage-based)\n- Hosting \u002F infrastructure cost implications\n\n---\n\n## Step 3: Comparison Table\n\n| Dimension           | Option A | Option B | Option C |\n|---------------------|----------|----------|----------|\n| Maturity            |          |          |          |\n| Fit                 |          |          |          |\n| Performance         |          |          |          |\n| Security            |          |          |          |\n| Developer XP        |          |          |          |\n| Cost                |          |          |          |\n| **Overall**         |          |          |          |\n\n---\n\n## Step 4: Recommendation\n\nState clearly:\n- **Recommended option** and why\n- **Conditions \u002F caveats** that could change the recommendation\n- **Risks** to monitor if adopted\n- **Suggested next step** (spike, POC, ADR, direct adoption)\n\n---\n\n## Step 5: Output\n\nSave to `{docsPath}\u002Fanalysis\u002Ftechnical-research-{slug}.md`.\n","# Technical Research Workflow\n\n## Goal\n\nProduce a structured technical evaluation that gives the team enough information to make a confident build \u002F buy \u002F adopt \u002F reject decision.\n\n---\n\n## Step 1: Define the Research Question\n\nAsk:\n1. What technology, library, or approach are we evaluating?\n2. What problem is it solving?\n3. What are the alternatives we should compare against?\n4. Who will use the decision — architect, developer, or product?\n\n---\n\n## Step 2: Evaluation Dimensions\n\nAssess the technology across:\n\n### Maturity & Ecosystem\n- Version, release cadence, age of project\n- GitHub stars, downloads\u002Fweek, last commit\n- Community size (Stack Overflow, Discord, forums)\n- Commercial backing vs. community-only\n\n### Fit Assessment\n- Does it solve the stated problem? Fully \u002F partially \u002F needs workaround?\n- Known integrations with our current stack\n- License compatibility\n\n### Performance & Scale\n- Benchmark data (if available) or credible community reports\n- Known limits: throughput, latency, memory footprint\n- Scale stories: who uses it at production scale?\n\n### Security\n- CVE history — any critical vulnerabilities in last 2 years?\n- Active security patch cadence\n- Compliance considerations (GDPR, SOC 2, HIPAA, etc.)\n\n### Developer Experience\n- Time to first working example\n- Quality of documentation\n- Local dev setup complexity\n\n### Cost\n- Licence cost (open source, commercial, seat-based, usage-based)\n- Hosting \u002F infrastructure cost implications\n\n---\n\n## Step 3: Comparison Table\n\n| Dimension           | Option A | Option B | Option C |\n|---------------------|----------|----------|----------|\n| Maturity            |          |          |          |\n| Fit                 |          |          |          |\n| Performance         |          |          |          |\n| Security            |          |          |          |\n| Developer XP        |          |          |          |\n| Cost                |          |          |          |\n| **Overall**         |          |          |          |\n\n---\n\n## Step 4: Recommendation\n\nState clearly:\n- **Recommended option** and why\n- **Conditions \u002F caveats** that could change the recommendation\n- **Risks** to monitor if adopted\n- **Suggested next step** (spike, POC, ADR, direct adoption)\n\n---\n\n## Step 5: Output\n\nSave to `{docsPath}\u002Fanalysis\u002Ftechnical-research-{slug}.md`.\n",{"name":5,"description":7},"master","86f9b15bf32a913d78f2dce364b9fe56e53ddf12","skills\u002F1-analysis\u002Ftechnical-research",1,"https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc","https:\u002F\u002Fsupermldev.github.io\u002Fsmart-sdlc\u002F","https:\u002F\u002Fgithub.com\u002FsuperMLdev","https:\u002F\u002Fsuperml.dev","2026-05-12 11:55:28",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add superMLdev\u002Fsmart-sdlc --skill technical-research",{"tool":63,"command":64},"bunx","bunx skills add superMLdev\u002Fsmart-sdlc --skill technical-research",{"tool":66,"command":67},"pnpm","pnpm dlx skills add superMLdev\u002Fsmart-sdlc --skill technical-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002F1-analysis\u002Ftechnical-research\u002FSKILL.md",true,[],[72,89,102,114,132,144],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":43},"01M71BD2HCRX8SP34Y37NZGVX2","jira-sync","Bulk sync all epics and stories from the local backlog to JIRA. Use when the user says 'sync to JIRA', 'push everything to JIRA', or 'create all JIRA tickets'.","https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fintegrations\u002Fjira\u002Fsync\u002FSKILL.md",[],[79,80,81,42,82,83,84,85,34,35,86,87,88],"jira sync","jira","sync","bulk","push","backlog","local","stories","create","tickets",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":43},"01M71BD0C5A3A3J7WF4YCGJJPY","jira-create-story","Create a single story ticket in JIRA from a local story file. Use when the user says 'create this story in JIRA' or 'push story to JIRA'.","https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fintegrations\u002Fjira\u002Fcreate-story\u002FSKILL.md",[],[96,80,87,97,98,83,99,85,100,34,35,101,42],"Story","create story","jira create story","ticket","single","file",{"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":108,"publishedAt":43},"01M71BCYVDM32DNS0XJAKTHRZ1","jira-create-epic","Create an epic in JIRA from a planning artifact. Use when the user says 'create this epic in JIRA' or 'push epic to JIRA'.","https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fintegrations\u002Fjira\u002Fcreate-epic\u002FSKILL.md",[],[87,109,80,110,111,42,35,34,112,83,113],"create epic","EPIC","jira create epic","planning","artifact",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":123,"publishedAt":43},"01M71BCWGYW8T1TD07JJ1G12G9","jira-connect","Set up and verify JIRA integration. Use when the user says 'connect to JIRA', 'set up JIRA', or 'configure JIRA'.","https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fintegrations\u002Fjira\u002Fconnect\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[124,80,125,126,127,34,35,128,129,130,131,42],"jira connect","connect","SET","up","configure","verify","jira integration","integration",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":43},"01M71BCTZ1EW31JHP6AMBHEM9G","jira-conflict-detect","Check if a story is already being worked on by another team member. Use before starting any story implementation.","https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fintegrations\u002Fjira\u002Fconflict-detect\u002FSKILL.md",[],[139,80,140,141,142,34,143,40,96],"jira conflict detect","detect","conflict","check","team",{"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":43},"01M71BCRX4ZHQ60DXGRAEECHB9","gitlab-create-mr","Create a GitLab Merge Request for the current story branch. Use when the user says 'create an MR', 'open a merge request', or 'ready for review' in a GitLab project.","https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fintegrations\u002Fgitlab\u002Fcreate-mr\u002FSKILL.md",[],[87,151,152,153,154,155,156,157,158,159,34,35,160,161,162,96,42],"mr","gitlab create mr","create mr","gitlab","ready","branch","for","project","open","review","merge","request"]