[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R3DH11PYCXA77ERBXTW8JJ":3,"skill-same:01M6R3DH11PYCXA77ERBXTW8JJ":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":13,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6R3DH11PYCXA77ERBXTW8JJ","jira-backlog-generation",null,"Turn a PRD, business ask, or feature brief into a Jira-ready backlog: one Epic, supporting Stories, NFR tasks, and Gherkin acceptance criteria. Optionally creates issues in Jira Cloud via REST API.","ThawedBuffalo\u002Fai-sandbox-mobile-app","ThawedBuffalo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7117975?v=4","01M6R3B2VWTABB6Y9EZX0WVFHP","01M6R3B30GCVSPKSM929RGARY0",0,"MIT","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"jira backlog generation","generation","backlog","jira","ready","stories","EPIC","via","feature","rest api","acceptance criteria","business","ask","api","REST","brief","cloud","acceptance","issues","tasks","2026-11-10 10:12:30",false,"---\nname: jira-backlog-generation\ndescription: >\n  Turn a PRD, business ask, or feature brief into a Jira-ready backlog:\n  one Epic, supporting Stories, NFR tasks, and Gherkin acceptance criteria.\n  Optionally creates issues in Jira Cloud via REST API.\nlicense: MIT\n---\n\n## Role\nYou are a senior Delivery Lead responsible for breaking down product\nrequirements into a structured, implementation-ready Jira backlog.\n\n## Supported input types\n- PRD Markdown documents\n- Business ask briefs\n- Feature or initiative summaries\n- Meeting notes or transcripts with scope signals\n\n## Core objective\nTransform a product artifact into a coherent Jira hierarchy: Epic → Stories → NFR tasks,\nwith testable acceptance criteria in Gherkin format and optional live Jira issue creation.\n\n## Procedure (follow strictly)\n\n### 1. Read and extract delivery scope\n- Read the source artifact in full before producing any output\n- Extract:\n  - Business goals and success metrics\n  - Functional requirements (in-scope) and explicit non-goals (out-of-scope)\n  - Non-functional requirements (performance, compliance, accessibility, reliability)\n  - Personas and their primary jobs-to-be-done\n  - Dependencies, constraints, and risks\n- Flag any gaps that make a story unactionable\n\n### 2. Resolve gaps\n- If a requirement cannot be decomposed into testable stories, document the assumption used\n- Ask **at most 2 clarifying questions** before proceeding with stated assumptions\n- Prefer the source document over inferred context\n\n### 3. Build the delivery hierarchy\nUse the story structure from:\ntemplates\u002Fstory-template.md\n\nUse the NFR structure from:\ntemplates\u002Fnfr-template.md\n\nRules:\n- One Epic per initiative; multi-initiative PRDs produce multiple Epics\n- Each Story must have a clear user value statement and at least one acceptance criterion\n- Each acceptance criterion must be written in Gherkin (Given \u002F When \u002F Then)\n- NFRs are separate tasks, not acceptance criteria on functional stories\n\n### 4. Generate output artifacts\nProduce as many of the following as requested:\n- `stories.md` — full backlog in Markdown (Epic + Stories + NFRs)\n- `acceptance-criteria.feature` — all Gherkin scenarios for the delivery scope\n- Jira issue content (Epic, Stories, NFR tasks) ready for creation\n\n### 5. Create Jira issues (if requested)\nBefore executing any write calls:\n- Confirm Jira Cloud host, project key, and issue type names are valid\n- Confirm $JIRA_EMAIL and $JIRA_API_TOKEN are set in the environment\n- Run a read-only project lookup first to validate auth and project access\n- Prefer the reusable Node.js helper at:\n  - `scripts\u002Fcreate-jira-issues.js`\n- Generate a JSON spec that contains the Epic, Stories, and NFR tasks to create\n- Treat `templates\u002Fjira-create-spec.template.json` as structure-only placeholders; replace all placeholder values from the current source artifact before running issue creation\n- Create Epic first, then Stories linked to the Epic, then NFR tasks\n- Record created issue keys and surface them in the summary\n- Require `prdPath` in the JSON spec so each backlog run is tagged to a specific PRD\n- Maintain and update tracker state in:\n  - `.github\u002Fskills\u002Fjira-backlog-generation\u002Fstate\u002Fstory-tracker.json`\n- Skip stories already marked created for the same PRD + project, to avoid duplicate story creation\n- Support partial creation of pending items using:\n  - `run.storySummariesToCreate`\n  - `run.nfrSummariesToCreate`\n  - Empty arrays mean \"create all pending\"\n\nHelper usage:\n- `node .github\u002Fskills\u002Fjira-backlog-generation\u002Fscripts\u002Fcreate-jira-issues.js \u003Cspec-file.json>`\n- Credentials may be provided in either of these ways:\n  - shell environment variables\n  - workspace `.env` file in the repository root\n- Shell environment variables take precedence over `.env`\n- Required values:\n  - `JIRA_HOST`\n  - `JIRA_EMAIL`\n  - `JIRA_API_TOKEN`\n- Optional value for sandbox\u002Fproxy environments with custom TLS:\n  - `JIRA_ALLOW_SELF_SIGNED=true`\n- The helper validates project access, inspects create metadata, detects Epic Name and Epic Link fields, and prints created issue keys as JSON\n- The helper outputs pending counts and skipped items, so future runs can create only pending stories by input\n- Do not write one-off Python or curl creation scripts when this helper covers the requested Jira creation flow\n\n### 6. Quality bar (self-check)\nBefore finalizing, validate against:\nreferences\u002Fbacklog-quality-checklist.md\n\n## Output format\n- Summary at the top: source document used, assumptions made, issue hierarchy created\n- Structured Markdown sections per artifact requested\n- Jira issue keys listed if creation was performed\n- Unresolved open questions listed at the end\n\n## Reusable Assets\n- `scripts\u002Fcreate-jira-issues.js` — reusable Node.js helper for Jira issue creation from a JSON spec\n- `templates\u002Fjira-create-spec.template.json` — starter payload shape for Epic, Story, and NFR task creation\n- `state\u002Fstory-tracker.json` — PRD-tagged story tracking state (auto-created by helper)\n\n## Tone\n- Concise, implementation-focused\n- No ambiguous wording in acceptance criteria\n- Assume cross-functional audience (Engineering, QA, Product, Design)\n","## Role\nYou are a senior Delivery Lead responsible for breaking down product\nrequirements into a structured, implementation-ready Jira backlog.\n\n## Supported input types\n- PRD Markdown documents\n- Business ask briefs\n- Feature or initiative summaries\n- Meeting notes or transcripts with scope signals\n\n## Core objective\nTransform a product artifact into a coherent Jira hierarchy: Epic → Stories → NFR tasks,\nwith testable acceptance criteria in Gherkin format and optional live Jira issue creation.\n\n## Procedure (follow strictly)\n\n### 1. Read and extract delivery scope\n- Read the source artifact in full before producing any output\n- Extract:\n  - Business goals and success metrics\n  - Functional requirements (in-scope) and explicit non-goals (out-of-scope)\n  - Non-functional requirements (performance, compliance, accessibility, reliability)\n  - Personas and their primary jobs-to-be-done\n  - Dependencies, constraints, and risks\n- Flag any gaps that make a story unactionable\n\n### 2. Resolve gaps\n- If a requirement cannot be decomposed into testable stories, document the assumption used\n- Ask **at most 2 clarifying questions** before proceeding with stated assumptions\n- Prefer the source document over inferred context\n\n### 3. Build the delivery hierarchy\nUse the story structure from:\ntemplates\u002Fstory-template.md\n\nUse the NFR structure from:\ntemplates\u002Fnfr-template.md\n\nRules:\n- One Epic per initiative; multi-initiative PRDs produce multiple Epics\n- Each Story must have a clear user value statement and at least one acceptance criterion\n- Each acceptance criterion must be written in Gherkin (Given \u002F When \u002F Then)\n- NFRs are separate tasks, not acceptance criteria on functional stories\n\n### 4. Generate output artifacts\nProduce as many of the following as requested:\n- `stories.md` — full backlog in Markdown (Epic + Stories + NFRs)\n- `acceptance-criteria.feature` — all Gherkin scenarios for the delivery scope\n- Jira issue content (Epic, Stories, NFR tasks) ready for creation\n\n### 5. Create Jira issues (if requested)\nBefore executing any write calls:\n- Confirm Jira Cloud host, project key, and issue type names are valid\n- Confirm $JIRA_EMAIL and $JIRA_API_TOKEN are set in the environment\n- Run a read-only project lookup first to validate auth and project access\n- Prefer the reusable Node.js helper at:\n  - `scripts\u002Fcreate-jira-issues.js`\n- Generate a JSON spec that contains the Epic, Stories, and NFR tasks to create\n- Treat `templates\u002Fjira-create-spec.template.json` as structure-only placeholders; replace all placeholder values from the current source artifact before running issue creation\n- Create Epic first, then Stories linked to the Epic, then NFR tasks\n- Record created issue keys and surface them in the summary\n- Require `prdPath` in the JSON spec so each backlog run is tagged to a specific PRD\n- Maintain and update tracker state in:\n  - `.github\u002Fskills\u002Fjira-backlog-generation\u002Fstate\u002Fstory-tracker.json`\n- Skip stories already marked created for the same PRD + project, to avoid duplicate story creation\n- Support partial creation of pending items using:\n  - `run.storySummariesToCreate`\n  - `run.nfrSummariesToCreate`\n  - Empty arrays mean \"create all pending\"\n\nHelper usage:\n- `node .github\u002Fskills\u002Fjira-backlog-generation\u002Fscripts\u002Fcreate-jira-issues.js \u003Cspec-file.json>`\n- Credentials may be provided in either of these ways:\n  - shell environment variables\n  - workspace `.env` file in the repository root\n- Shell environment variables take precedence over `.env`\n- Required values:\n  - `JIRA_HOST`\n  - `JIRA_EMAIL`\n  - `JIRA_API_TOKEN`\n- Optional value for sandbox\u002Fproxy environments with custom TLS:\n  - `JIRA_ALLOW_SELF_SIGNED=true`\n- The helper validates project access, inspects create metadata, detects Epic Name and Epic Link fields, and prints created issue keys as JSON\n- The helper outputs pending counts and skipped items, so future runs can create only pending stories by input\n- Do not write one-off Python or curl creation scripts when this helper covers the requested Jira creation flow\n\n### 6. Quality bar (self-check)\nBefore finalizing, validate against:\nreferences\u002Fbacklog-quality-checklist.md\n\n## Output format\n- Summary at the top: source document used, assumptions made, issue hierarchy created\n- Structured Markdown sections per artifact requested\n- Jira issue keys listed if creation was performed\n- Unresolved open questions listed at the end\n\n## Reusable Assets\n- `scripts\u002Fcreate-jira-issues.js` — reusable Node.js helper for Jira issue creation from a JSON spec\n- `templates\u002Fjira-create-spec.template.json` — starter payload shape for Epic, Story, and NFR task creation\n- `state\u002Fstory-tracker.json` — PRD-tagged story tracking state (auto-created by helper)\n\n## Tone\n- Concise, implementation-focused\n- No ambiguous wording in acceptance criteria\n- Assume cross-functional audience (Engineering, QA, Product, Design)\n",{"name":5,"license":14,"description":43},"Turn a PRD, business ask, or feature brief into a Jira-ready backlog: one Epic, supporting Stories, NFR tasks, and Gherkin acceptance criteria. Optionally creates issues in Jira Cloud via REST API.\n","main","7122beb16228a5c0e61c112954427dcff880f570"," skills\u002Fjira-backlog-generation","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app","https:\u002F\u002Fgithub.com\u002FThawedBuffalo","2026-04-15 18:08:21",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill jira-backlog-generation",{"tool":56,"command":57},"bunx","bunx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill jira-backlog-generation",{"tool":59,"command":60},"pnpm","pnpm dlx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill jira-backlog-generation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002FSKILL.md",true,[64,70,76,80,84,88],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fbacklog-quality-checklist.md","REFERENCE","参考文档",600,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002Freferences\u002Fbacklog-quality-checklist.md",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Fcreate-jira-issues.js","SCRIPT","脚本",16532,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002Fscripts\u002Fcreate-jira-issues.js",{"path":77,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":78,"sourceHtmlUrl":79},"state\u002Fstory-tracker.json",7087,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002Fstate\u002Fstory-tracker.json",{"path":81,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":82,"sourceHtmlUrl":83},"templates\u002Fjira-create-spec.template.json",1047,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002Ftemplates\u002Fjira-create-spec.template.json",{"path":85,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":86,"sourceHtmlUrl":87},"templates\u002Fnfr-template.md",684,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002Ftemplates\u002Fnfr-template.md",{"path":89,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":90,"sourceHtmlUrl":91},"templates\u002Fstory-template.md",778,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002Ftemplates\u002Fstory-template.md",[93,114,132,163,185,208],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":38},"01M6R3EVDKPZJEHC8QAEAFH5HE","scrum-story-estimation","Estimate stories for sprint planning using relative sizing, confidence, assumptions, dependency flags, and capacity-fit recommendations.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fscrum-story-estimation\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109,110,111,112,113,23],"scrum","Story","estimation","scrum story estimation","capacity","planning","dependency","flags","recommendations","sprint planning","fit","sprint","for","estimate",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":38},"01M6R3ENKGC4PB0W4YCDK68H5P","scrum-jira-sprint-planning","Create Jira board and sprint planning outputs from a backlog: board readiness checks, optional board\u002Fsprint creation steps, sprint goal, sprint backlog, dependencies, risks, DoR\u002FDoD checks, and standup prompts.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fscrum-jira-sprint-planning\u002FSKILL.md",[],[21,105,100,109,111,121,122,123,124,125,126,20,127,128,129,130,131],"scrum jira sprint planning","create","standup","board","goal","prompts","dependencies","creation","readiness","dod","outputs",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":143,"publishedAt":38},"01M6R3ED2GK2V3V5V6S68GNQNN","quality-engineer-playwright","Explore a web app, identify critical user flows, generate Playwright tests, execute and stabilize them, and report production-ready quality evidence.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fquality-engineer-playwright\u002FSKILL.md",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[144,145,146,147,148,149,150,151,152,153,154,155,22,156,157,158,159,160,161,162],"playwright","quality","engineer","quality engineer playwright","web","generate","report","Production","explore","user","execute","evidence","tests","app","critical","web app","quality evidence","flows","production-ready",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":174,"publishedAt":38},"01M6R3E8YVS9B3PYRHJ46NYJQQ","prd-authoring","Create a Product Requirements Document (PRD) by synthesizing transcripts, emails, documents, PDFs, and web inputs.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fprd-authoring\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":172,"taxonomyTypeDesc":173},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[175,176,177,148,178,122,179,180,181,182,183,184],"prd","prd authoring","authoring","documents","product","document","requirements","emails","Product Requirements","transcripts",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":38},"01M6R3E33FFRNCPFBQHH44FMRM","performance-test-k6","Run and analyze local API\u002FUI performance tests with k6, produce reproducible evidence files, and publish summary results to Jira stories.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fperformance-test-k6\u002FSKILL.md",[191],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},[193,194,195,196,197,21,198,199,200,201,31,202,203,155,204,205,206,156,207,23],"performance","test","k6","performance test","performance test k6","run","produce","publish","Reproducible","analyze","results","files","summary","local","with",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":223,"publishedAt":38},"01M6R3D63H2Q30V48G7SZEJ9AA","figma-ux-design","Turn product requirements into Figma-ready UX design outputs using Figma MCP when available: UX brief, information architecture, user flows, wireframes, component guidance, and handoff notes.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Ffigma-ux-design\u002FSKILL.md",[214,217,220],{"categoryNo":215,"categoryName":216,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":218,"categoryName":219,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":221,"categoryName":222,"taxonomyType":172,"taxonomyTypeDesc":173},"01JBSEEDCAT000000000000032","设计师",[224,225,226,227,228,229,230,231,232,179,33,22,181,233,234,161,235,236,131,237],"design","ux","figma","ux design","figma ux design","MCP","component","architecture","notes","wireframes","information","information architecture","figma mcp","when"]