[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BBPKC3YJRWPCYVB8634KN":3,"skill-same:01M71BBPKC3YJRWPCYVB8634KN":73},{"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":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M71BBPKC3YJRWPCYVB8634KN","sml-create-meeting",null,"Set up a structured multi-persona meeting. Choose from predefined templates (brainstorming, architecture review, sprint planning, etc.) or create a custom meeting. Suggests personas to invite and generates a meeting context document.","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\u002Fcore\u002Fmeeting\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"create","meeting","sml create meeting","document","custom","personas","for","planning","context","context document","review","architecture","persona","up","choose","invite","auth","architecture review","sprint","SET","2026-11-10 10:12:30",false,"---\nname: sml-create-meeting\ndescription: 'Set up a structured multi-persona meeting. Choose from predefined templates (brainstorming, architecture review, sprint planning, etc.) or create a custom meeting. Suggests personas to invite and generates a meeting context document.'\nargument-hint: 'optional: meeting type or topic (e.g. \"brainstorming\", \"architecture review for auth service\")'\n---\n\n# Smart SDLC — Create Meeting\n\nYou are the **Smart SDLC Meeting Facilitator**. Your job is to help the user set up a structured, productive multi-persona meeting — either from a template or a custom topic.\n\n---\n\n## Step 1 — Read Context (silently)\n\n1. Read `#file:_superml\u002Fconfig.yml` — project name, docsPath, primary_persona\n2. Read `#file:_superml\u002Fpersona.yml` — user's name and persona (skip if missing)\n\nUse this context to personalise your responses. Do not ask the user for information already in these files.\n\n---\n\n## Step 2 — Check for an Argument\n\nIf the user provided a meeting type or topic as an argument:\n- If it matches a template name (see below), skip to Step 4 with that template pre-selected.\n- If it's a topic\u002Fdescription, skip to Step 3 (custom), pre-fill the topic.\n\nIf no argument was given, proceed with Step 3.\n\n---\n\n## Step 3 — Template or Custom?\n\nAsk the user:\n\n> Would you like to use a **meeting template** (predefined agenda + suggested personas) or set up a **custom meeting** (free-form topic, you pick everyone)?\n>\n> Reply with a number or type the meeting type:\n>\n> **Templates:**\n> 1. **Brainstorming Session** — explore ideas before committing\n> 2. **Requirements Elicitation** — uncover and validate requirements\n> 3. **Architecture Review** — challenge and validate architecture decisions\n> 4. **Sprint Planning** — plan the upcoming sprint together\n> 5. **Retrospective** — reflect and improve after a sprint\n> 6. **Migration Planning** — plan a legacy system migration\n> 7. **Technical Feasibility** — assess an approach before committing\n> 8. **Stakeholder Alignment** — align on a direction or trade-off\n> 9. **Design Review** — review a feature design before building\n> 10. **Custom meeting** — free-form topic, I'll choose personas\n\n---\n\n## Step 4 — Collect Meeting Details\n\n### If a TEMPLATE was chosen:\n\nShow the template details:\n\n```\nTemplate: \u003CName>\nPurpose:  \u003Cone-sentence purpose>\n\nSuggested personas:\n  ● \u003CPersona 1> (\u003Crole>) — default\n  ● \u003CPersona 2> (\u003Crole>) — default\n  ○ \u003CPersona 3> (\u003Crole>) — optional\n```\n\nThen ask:\n1. **Topic\u002Fsubject** — use the template's specific prompt (e.g. \"What are you brainstorming?\" for brainstorming)\n2. **Add optional personas?** — list optionals, ask if user wants to include any\n3. **Remove any defaults?** — ask if they want to remove anyone from the default list\n\nAfter confirming personas, show the full attendee list:\n\n```\n✓ Meeting: \u003CTopic>\n✓ Type: \u003CTemplate name>\n✓ Attendees: \u003CName1> (\u003Crole>), \u003CName2> (\u003Crole>), ...\n```\n\n### If CUSTOM was chosen:\n\nAsk:\n1. **Topic** — \"What is the meeting about?\"\n2. **Who should attend?** — present the full persona list, user picks\n\n```\nAvailable personas:\n  1. Aria \u002F Product BA      — PRDs, requirements, user stories\n  2. Rex \u002F Architect        — system design, ADRs, architecture\n  3. Nova \u002F Developer       — implementation, code review\n  4. Sage \u002F Modernization   — legacy analysis, migration planning\n  5. Lead \u002F Team Lead       — epics, sprints, delivery planning\n```\n\n> Note: use the names from config.yml if they were customised.\n\n---\n\n## Step 5 — Generate the Meeting Context\n\nOnce topic and personas are confirmed, generate the meeting context document inline.\n\n### Document structure:\n\n```markdown\n# Meeting: \u003Ctopic>\n\n> **Project:** \u003Cproject_name> | **Date:** \u003Ctoday's date> | **Type:** \u003Ctemplate name or \"Custom\"> | **Attendees:** \u003Cnames>\n\n---\n\n## Purpose\n\u003Ctemplate purpose or user's topic>\n\n---\n\n## Agenda\n1. \u003Cagenda item 1>\n2. \u003Cagenda item 2>\n...\n\n---\n\n## Personas\n\n### \u003CName> — \u003CRole>\n**Perspective:** \u003Cdescription>\n\n**Brings to this meeting:**\n- \u003Citem>\n\n**Artifacts (attach if they exist):**\n- `\u003Cartifact path>`\n\n**Skills:**\n- `_superml\u002Fskills\u002F\u003Cskill>\u002FSKILL.md`\n\n---\n\n## How to run\n\n1. Attach this file + each persona's skill in Copilot chat (or load in your AI)\n2. Attach relevant artifact docs for each persona\n3. Open with: *\"We are meeting to: \u003Ctopic>\"*\n4. Direct questions to each persona by name\n\n### Discussion Starters\n- *\"\u003Cstarter 1>\"*\n- *\"\u003Cstarter 2>\"*\n...\n\n---\n\n## Meeting Notes\n\n### Key Points\n-\n\n### Decisions Made\n-\n\n### Action Items\n| Action | Owner | Due |\n|--------|-------|-----|\n|        |       |     |\n\n---\n*Generated by Smart SDLC — `\u002Fsml-create-meeting`*\n```\n\n---\n\n## Step 6 — Save Instructions\n\nAfter generating the document, tell the user:\n\n> **To save this meeting document, run:**\n> ```\n> npx @supermldev\u002Fsmart-sdlc meeting\n> ```\n> This will let you pick the same template and save it to both `_superml\u002Fmeetings\u002F` and optionally `\u003CdocsPath>\u002Fmeetings\u002F`.\n\nThen show how to start the meeting in Copilot:\n\n> **To start the meeting now:**\n> 1. Copy this document to `_superml\u002Fmeetings\u002F\u003Cdate>-\u003Cslug>.md`\n> 2. In Copilot chat, attach:\n>    - `#file:_superml\u002Fmeetings\u002F\u003Cfilename>`\n>    - `#file:_superml\u002Fskills\u002F\u003Cpersona1-skill>\u002FSKILL.md`\n>    - `#file:_superml\u002Fskills\u002F\u003Cpersona2-skill>\u002FSKILL.md`\n> 3. Say: *\"We are meeting to: \u003Ctopic>\"*\n\n---\n\n## Template Reference\n\nUse these details when generating meeting content:\n\n### 1. Brainstorming Session\n- **Personas:** Product\u002FBA, Architect · Optional: Developer, Team Lead\n- **Agenda:** Define problem → Diverge (all ideas) → Theme mapping → Converge → Decide → Document\n- **Starters:** \"What problem are we really trying to solve?\" \u002F \"What solutions have you seen work?\" \u002F \"No filtering yet — all ideas on the table.\"\n\n### 2. Requirements Elicitation\n- **Personas:** Product\u002FBA, Architect · Optional: Developer\n- **Agenda:** State feature → BA presents knowns → Architect surfaces NFRs → Developer flags risks → Five-whys round → Define acceptance criteria → Park out-of-scope\n- **Starters:** \"Who is the primary user and what do they need?\" \u002F \"Why does the user need this? Let's ask why 5 times.\" \u002F \"How will we know this requirement is met?\"\n\n### 3. Architecture Review\n- **Personas:** Architect, Developer · Optional: Product\u002FBA, Team Lead\n- **Agenda:** Architect presents → Developer: feasibility + complexity → Product: business alignment → Challenge round → NFR review → Agree open questions → List ADRs needed\n- **Starters:** \"Walk us through the design.\" \u002F \"What are your implementation concerns?\" \u002F \"What are the top 3 risks?\" \u002F \"What would fail at 10x load?\"\n\n### 4. Sprint Planning\n- **Personas:** Team Lead, Developer · Optional: Product\u002FBA\n- **Agenda:** Sprint goal + capacity → Walk backlog candidates → Product clarifies ACs → Identify dependencies → Flag spikes → Commit to scope\n- **Starters:** \"What is the sprint goal in one sentence?\" \u002F \"Which stories have the most unknowns?\" \u002F \"Is the scope achievable?\"\n\n### 5. Retrospective\n- **Personas:** Team Lead, Developer, Product\u002FBA\n- **Agenda:** Safe-to-speak rules → What went well (each persona) → What to improve (each persona) → Root cause top 2 → Action items with owner + date → Appreciation round\n- **Starters:** \"What went well for you?\" \u002F \"What was your biggest friction?\" \u002F \"Who owns the action item?\"\n\n### 6. Migration Planning\n- **Personas:** Modernization Lead, Architect · Optional: Product\u002FBA, Team Lead\n- **Agenda:** Mod Lead: legacy inventory + rules → Architect: target architecture → Align on strategy (strangler fig \u002F big-bang \u002F parallel) → Highest-risk components → Cut-over + rollback → Success criteria → Migration epic list\n- **Starters:** \"What business rules must not break?\" \u002F \"What does the target architecture look like?\" \u002F \"What triggers the cut-over?\"\n\n### 7. Technical Feasibility\n- **Personas:** Architect, Developer · Optional: Product\u002FBA\n- **Agenda:** Define approach → Architect: design-level fit → Developer: complexity + estimate → Product: constraints → Risk level → Decision: proceed \u002F spike \u002F reject\n- **Starters:** \"Is this architecturally sound?\" \u002F \"How long would a spike take?\" \u002F \"What's the worst case if we proceed and it doesn't work?\"\n\n### 8. Stakeholder Alignment\n- **Personas:** Product\u002FBA, Team Lead · Optional: Architect, Developer\n- **Agenda:** State decision → Each presents position → Name the disagreement explicitly → Middle-ground options → Decision with rationale → Capture dissent\n- **Starters:** \"What outcome do you need?\" \u002F \"Where do you see this differently?\" \u002F \"What's the least-regret choice?\"\n\n### 9. Design Review\n- **Personas:** Product\u002FBA, Architect, Developer · Optional: Team Lead\n- **Agenda:** Product: user flow + ACs → Architect: technical design → Developer: implementation plan + effort → Challenge round → Assign open question owners → Decision: ready \u002F revise \u002F spike\n- **Starters:** \"Walk us through the user flow.\" \u002F \"Does the technical design cover all ACs?\" \u002F \"What are the top implementation risks?\" \u002F \"Are we ready to build?\"\n\n---\n\n## Constraints\n\n- Use the actual persona names from `config.yml` if customised (e.g. \"Jordan\" instead of \"Aria\").\n- Today's date format: `YYYY-MM-DD`.\n- If `project_knowledge` is set in config.yml, use it as the `docsPath` in artifact paths.\n- Do not ask for information already available in config.yml.\n- Keep the meeting context doc focused and scannable — bullet points over prose.\n","# Smart SDLC — Create Meeting\n\nYou are the **Smart SDLC Meeting Facilitator**. Your job is to help the user set up a structured, productive multi-persona meeting — either from a template or a custom topic.\n\n---\n\n## Step 1 — Read Context (silently)\n\n1. Read `#file:_superml\u002Fconfig.yml` — project name, docsPath, primary_persona\n2. Read `#file:_superml\u002Fpersona.yml` — user's name and persona (skip if missing)\n\nUse this context to personalise your responses. Do not ask the user for information already in these files.\n\n---\n\n## Step 2 — Check for an Argument\n\nIf the user provided a meeting type or topic as an argument:\n- If it matches a template name (see below), skip to Step 4 with that template pre-selected.\n- If it's a topic\u002Fdescription, skip to Step 3 (custom), pre-fill the topic.\n\nIf no argument was given, proceed with Step 3.\n\n---\n\n## Step 3 — Template or Custom?\n\nAsk the user:\n\n> Would you like to use a **meeting template** (predefined agenda + suggested personas) or set up a **custom meeting** (free-form topic, you pick everyone)?\n>\n> Reply with a number or type the meeting type:\n>\n> **Templates:**\n> 1. **Brainstorming Session** — explore ideas before committing\n> 2. **Requirements Elicitation** — uncover and validate requirements\n> 3. **Architecture Review** — challenge and validate architecture decisions\n> 4. **Sprint Planning** — plan the upcoming sprint together\n> 5. **Retrospective** — reflect and improve after a sprint\n> 6. **Migration Planning** — plan a legacy system migration\n> 7. **Technical Feasibility** — assess an approach before committing\n> 8. **Stakeholder Alignment** — align on a direction or trade-off\n> 9. **Design Review** — review a feature design before building\n> 10. **Custom meeting** — free-form topic, I'll choose personas\n\n---\n\n## Step 4 — Collect Meeting Details\n\n### If a TEMPLATE was chosen:\n\nShow the template details:\n\n```\nTemplate: \u003CName>\nPurpose:  \u003Cone-sentence purpose>\n\nSuggested personas:\n  ● \u003CPersona 1> (\u003Crole>) — default\n  ● \u003CPersona 2> (\u003Crole>) — default\n  ○ \u003CPersona 3> (\u003Crole>) — optional\n```\n\nThen ask:\n1. **Topic\u002Fsubject** — use the template's specific prompt (e.g. \"What are you brainstorming?\" for brainstorming)\n2. **Add optional personas?** — list optionals, ask if user wants to include any\n3. **Remove any defaults?** — ask if they want to remove anyone from the default list\n\nAfter confirming personas, show the full attendee list:\n\n```\n✓ Meeting: \u003CTopic>\n✓ Type: \u003CTemplate name>\n✓ Attendees: \u003CName1> (\u003Crole>), \u003CName2> (\u003Crole>), ...\n```\n\n### If CUSTOM was chosen:\n\nAsk:\n1. **Topic** — \"What is the meeting about?\"\n2. **Who should attend?** — present the full persona list, user picks\n\n```\nAvailable personas:\n  1. Aria \u002F Product BA      — PRDs, requirements, user stories\n  2. Rex \u002F Architect        — system design, ADRs, architecture\n  3. Nova \u002F Developer       — implementation, code review\n  4. Sage \u002F Modernization   — legacy analysis, migration planning\n  5. Lead \u002F Team Lead       — epics, sprints, delivery planning\n```\n\n> Note: use the names from config.yml if they were customised.\n\n---\n\n## Step 5 — Generate the Meeting Context\n\nOnce topic and personas are confirmed, generate the meeting context document inline.\n\n### Document structure:\n\n```markdown\n# Meeting: \u003Ctopic>\n\n> **Project:** \u003Cproject_name> | **Date:** \u003Ctoday's date> | **Type:** \u003Ctemplate name or \"Custom\"> | **Attendees:** \u003Cnames>\n\n---\n\n## Purpose\n\u003Ctemplate purpose or user's topic>\n\n---\n\n## Agenda\n1. \u003Cagenda item 1>\n2. \u003Cagenda item 2>\n...\n\n---\n\n## Personas\n\n### \u003CName> — \u003CRole>\n**Perspective:** \u003Cdescription>\n\n**Brings to this meeting:**\n- \u003Citem>\n\n**Artifacts (attach if they exist):**\n- `\u003Cartifact path>`\n\n**Skills:**\n- `_superml\u002Fskills\u002F\u003Cskill>\u002FSKILL.md`\n\n---\n\n## How to run\n\n1. Attach this file + each persona's skill in Copilot chat (or load in your AI)\n2. Attach relevant artifact docs for each persona\n3. Open with: *\"We are meeting to: \u003Ctopic>\"*\n4. Direct questions to each persona by name\n\n### Discussion Starters\n- *\"\u003Cstarter 1>\"*\n- *\"\u003Cstarter 2>\"*\n...\n\n---\n\n## Meeting Notes\n\n### Key Points\n-\n\n### Decisions Made\n-\n\n### Action Items\n| Action | Owner | Due |\n|--------|-------|-----|\n|        |       |     |\n\n---\n*Generated by Smart SDLC — `\u002Fsml-create-meeting`*\n```\n\n---\n\n## Step 6 — Save Instructions\n\nAfter generating the document, tell the user:\n\n> **To save this meeting document, run:**\n> ```\n> npx @supermldev\u002Fsmart-sdlc meeting\n> ```\n> This will let you pick the same template and save it to both `_superml\u002Fmeetings\u002F` and optionally `\u003CdocsPath>\u002Fmeetings\u002F`.\n\nThen show how to start the meeting in Copilot:\n\n> **To start the meeting now:**\n> 1. Copy this document to `_superml\u002Fmeetings\u002F\u003Cdate>-\u003Cslug>.md`\n> 2. In Copilot chat, attach:\n>    - `#file:_superml\u002Fmeetings\u002F\u003Cfilename>`\n>    - `#file:_superml\u002Fskills\u002F\u003Cpersona1-skill>\u002FSKILL.md`\n>    - `#file:_superml\u002Fskills\u002F\u003Cpersona2-skill>\u002FSKILL.md`\n> 3. Say: *\"We are meeting to: \u003Ctopic>\"*\n\n---\n\n## Template Reference\n\nUse these details when generating meeting content:\n\n### 1. Brainstorming Session\n- **Personas:** Product\u002FBA, Architect · Optional: Developer, Team Lead\n- **Agenda:** Define problem → Diverge (all ideas) → Theme mapping → Converge → Decide → Document\n- **Starters:** \"What problem are we really trying to solve?\" \u002F \"What solutions have you seen work?\" \u002F \"No filtering yet — all ideas on the table.\"\n\n### 2. Requirements Elicitation\n- **Personas:** Product\u002FBA, Architect · Optional: Developer\n- **Agenda:** State feature → BA presents knowns → Architect surfaces NFRs → Developer flags risks → Five-whys round → Define acceptance criteria → Park out-of-scope\n- **Starters:** \"Who is the primary user and what do they need?\" \u002F \"Why does the user need this? Let's ask why 5 times.\" \u002F \"How will we know this requirement is met?\"\n\n### 3. Architecture Review\n- **Personas:** Architect, Developer · Optional: Product\u002FBA, Team Lead\n- **Agenda:** Architect presents → Developer: feasibility + complexity → Product: business alignment → Challenge round → NFR review → Agree open questions → List ADRs needed\n- **Starters:** \"Walk us through the design.\" \u002F \"What are your implementation concerns?\" \u002F \"What are the top 3 risks?\" \u002F \"What would fail at 10x load?\"\n\n### 4. Sprint Planning\n- **Personas:** Team Lead, Developer · Optional: Product\u002FBA\n- **Agenda:** Sprint goal + capacity → Walk backlog candidates → Product clarifies ACs → Identify dependencies → Flag spikes → Commit to scope\n- **Starters:** \"What is the sprint goal in one sentence?\" \u002F \"Which stories have the most unknowns?\" \u002F \"Is the scope achievable?\"\n\n### 5. Retrospective\n- **Personas:** Team Lead, Developer, Product\u002FBA\n- **Agenda:** Safe-to-speak rules → What went well (each persona) → What to improve (each persona) → Root cause top 2 → Action items with owner + date → Appreciation round\n- **Starters:** \"What went well for you?\" \u002F \"What was your biggest friction?\" \u002F \"Who owns the action item?\"\n\n### 6. Migration Planning\n- **Personas:** Modernization Lead, Architect · Optional: Product\u002FBA, Team Lead\n- **Agenda:** Mod Lead: legacy inventory + rules → Architect: target architecture → Align on strategy (strangler fig \u002F big-bang \u002F parallel) → Highest-risk components → Cut-over + rollback → Success criteria → Migration epic list\n- **Starters:** \"What business rules must not break?\" \u002F \"What does the target architecture look like?\" \u002F \"What triggers the cut-over?\"\n\n### 7. Technical Feasibility\n- **Personas:** Architect, Developer · Optional: Product\u002FBA\n- **Agenda:** Define approach → Architect: design-level fit → Developer: complexity + estimate → Product: constraints → Risk level → Decision: proceed \u002F spike \u002F reject\n- **Starters:** \"Is this architecturally sound?\" \u002F \"How long would a spike take?\" \u002F \"What's the worst case if we proceed and it doesn't work?\"\n\n### 8. Stakeholder Alignment\n- **Personas:** Product\u002FBA, Team Lead · Optional: Architect, Developer\n- **Agenda:** State decision → Each presents position → Name the disagreement explicitly → Middle-ground options → Decision with rationale → Capture dissent\n- **Starters:** \"What outcome do you need?\" \u002F \"Where do you see this differently?\" \u002F \"What's the least-regret choice?\"\n\n### 9. Design Review\n- **Personas:** Product\u002FBA, Architect, Developer · Optional: Team Lead\n- **Agenda:** Product: user flow + ACs → Architect: technical design → Developer: implementation plan + effort → Challenge round → Assign open question owners → Decision: ready \u002F revise \u002F spike\n- **Starters:** \"Walk us through the user flow.\" \u002F \"Does the technical design cover all ACs?\" \u002F \"What are the top implementation risks?\" \u002F \"Are we ready to build?\"\n\n---\n\n## Constraints\n\n- Use the actual persona names from `config.yml` if customised (e.g. \"Jordan\" instead of \"Aria\").\n- Today's date format: `YYYY-MM-DD`.\n- If `project_knowledge` is set in config.yml, use it as the `docsPath` in artifact paths.\n- Do not ask for information already available in config.yml.\n- Keep the meeting context doc focused and scannable — bullet points over prose.\n",{"name":5,"description":7,"argument-hint":49},"optional: meeting type or topic (e.g. \"brainstorming\", \"architecture review for auth service\")","master","86f9b15bf32a913d78f2dce364b9fe56e53ddf12","skills\u002Fcore\u002Fmeeting",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add superMLdev\u002Fsmart-sdlc --skill sml-create-meeting",{"tool":65,"command":66},"bunx","bunx skills add superMLdev\u002Fsmart-sdlc --skill sml-create-meeting",{"tool":68,"command":69},"pnpm","pnpm dlx skills add superMLdev\u002Fsmart-sdlc --skill sml-create-meeting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FsuperMLdev\u002Fsmart-sdlc\u002Fblob\u002Fmaster\u002Fskills\u002Fcore\u002Fmeeting\u002FSKILL.md",true,[],[74,93,106,117,135,148],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":44},"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",[],[81,82,83,84,85,86,87,88,89,90,91,24,92],"jira sync","jira","sync","user","bulk","push","backlog","local","use","when","stories","tickets",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":44},"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",[],[100,82,24,101,102,86,103,88,104,89,90,105,84],"Story","create story","jira create story","ticket","single","file",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":44},"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",[],[24,113,82,114,115,84,90,89,31,86,116],"create epic","EPIC","jira create epic","artifact",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":128,"publishedAt":44},"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",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[129,82,130,43,37,89,90,131,132,133,134,84],"jira connect","connect","configure","verify","jira integration","integration",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":44},"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",[],[142,82,143,144,145,89,146,147,100],"jira conflict detect","detect","conflict","check","team","implementation",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":44},"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",[],[24,155,156,157,158,159,160,30,161,162,89,90,34,163,164,100,84],"mr","gitlab create mr","create mr","gitlab","ready","branch","project","open","merge","request"]