[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CX79NRRSCZ5PWZ8714H8Z3":3,"skill-same:01M6CX79NRRSCZ5PWZ8714H8Z3":99},{"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":31,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6CX79NRRSCZ5PWZ8714H8Z3","mfse-user-stories-writing",null,"Create effective User Stories with step-by-step guidance. Use when: drafting new features, documenting requirements, writing acceptance criteria in standard BDD format (Given\u002FWhen\u002FThen). Generates complete, properly formatted User Stories.","MFSoftwareEngineering\u002Fmfse-softwarefactory","MFSoftwareEngineering","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266699757?v=4","01M6CX712369QYG0GP7SWKJKAY","MFSE","01M6CX716NCX9PV4F3DP4Y2E6F",3,"MIT","https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fmfse-user-stories-writing\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[32,33,34,35,36,37,38,39,40,41,42,43,44,45],"writing","user","mfse user stories writing","create","acceptance","format","bdd","write","user story","use","Story","guidance","acceptance criteria","requirements","2026-11-10 10:12:30",false,"---\r\nname: mfse-user-stories-writing\r\ndescription: 'Create effective User Stories with step-by-step guidance. Use when: drafting new features, documenting requirements, writing acceptance criteria in standard BDD format (Given\u002FWhen\u002FThen). Generates complete, properly formatted User Stories.'\r\nargument-hint: 'Requirement to write as a User Story'\r\n---\r\n\r\n# Azure DevOps User Story Creation\r\n\r\nCreate complete, well-structured User Stories following industry best practices. This skill guides you through each component and generates ready-to-use content.\r\n\r\n## When to Use\r\n\r\n- Writing new feature requirements for a product backlog\r\n- Documenting user-facing functionality that needs acceptance criteria\r\n- Converting requirements into properly formatted User Stories\r\n- Creating epics or nested stories with consistent structure\r\n\r\n## Before You Start\r\n\r\nGather these details about your feature:\r\n- Who uses this feature (user type\u002Fpersona)\r\n- What they want to accomplish (goal or outcome)\r\n- Why they need it (business value or reason)\r\n- Success criteria (testable conditions that prove completion)\r\n\r\n## Step-by-Step Procedure\r\n\r\n### 1. Define the User Persona\r\nIdentify the type of user: team member, admin, customer, stakeholder, etc.\r\n\r\nExample:\r\n- Product Manager\r\n- Development Team Lead\r\n- End-user \u002F Customer\r\n\r\n### 2. Write the User Story Statement\r\nUse the standard format you can find in the [reference](..\u002FMFSE-user-stories-writing\u002Freferences\u002FREFERENCE.md).\r\n\r\n\r\nBest Practices:\r\n- Each criterion should be testable\r\n- Write from a user perspective, not technical implementation\r\n- Include both happy path and edge cases\r\n- Use consistent language\r\n- Follow INVEST principles (Independent, Negotiable, Valuable, Estimable, Small, Testable)\r\n\r\n### 4. Add Supporting Details (Optional)\r\n\r\nInclude if relevant:\r\n- Dependencies: What must be completed first?\r\n- Notes: Technical constraints, performance targets, compliance requirements\r\n- Related Stories: Links to other stories \u002F features \u002F epics that are connected\r\n\r\n\r\n### 5. Output\r\n\r\nOnce complete, your User Story is ready to:\r\n- Share with user\r\n\r\n\r\n## Tips for Success\r\n\r\n1. User-centered language: Write for the person using the feature, not developers implementing it\r\n2. Keep implementation flexibility: describe the expected outcome and leave room for technical design choices\r\n3. Testability first: Every criterion should have a clear pass\u002Ffail condition\r\n4. Scenarios over bullets: Gherkin format (Given\u002FWhen\u002FThen) makes criteria unambiguous\r\n5. Keep it focused: One user story = one user goal; split large features into smaller stories\r\n","# Azure DevOps User Story Creation\r\n\r\nCreate complete, well-structured User Stories following industry best practices. This skill guides you through each component and generates ready-to-use content.\r\n\r\n## When to Use\r\n\r\n- Writing new feature requirements for a product backlog\r\n- Documenting user-facing functionality that needs acceptance criteria\r\n- Converting requirements into properly formatted User Stories\r\n- Creating epics or nested stories with consistent structure\r\n\r\n## Before You Start\r\n\r\nGather these details about your feature:\r\n- Who uses this feature (user type\u002Fpersona)\r\n- What they want to accomplish (goal or outcome)\r\n- Why they need it (business value or reason)\r\n- Success criteria (testable conditions that prove completion)\r\n\r\n## Step-by-Step Procedure\r\n\r\n### 1. Define the User Persona\r\nIdentify the type of user: team member, admin, customer, stakeholder, etc.\r\n\r\nExample:\r\n- Product Manager\r\n- Development Team Lead\r\n- End-user \u002F Customer\r\n\r\n### 2. Write the User Story Statement\r\nUse the standard format you can find in the [reference](..\u002FMFSE-user-stories-writing\u002Freferences\u002FREFERENCE.md).\r\n\r\n\r\nBest Practices:\r\n- Each criterion should be testable\r\n- Write from a user perspective, not technical implementation\r\n- Include both happy path and edge cases\r\n- Use consistent language\r\n- Follow INVEST principles (Independent, Negotiable, Valuable, Estimable, Small, Testable)\r\n\r\n### 4. Add Supporting Details (Optional)\r\n\r\nInclude if relevant:\r\n- Dependencies: What must be completed first?\r\n- Notes: Technical constraints, performance targets, compliance requirements\r\n- Related Stories: Links to other stories \u002F features \u002F epics that are connected\r\n\r\n\r\n### 5. Output\r\n\r\nOnce complete, your User Story is ready to:\r\n- Share with user\r\n\r\n\r\n## Tips for Success\r\n\r\n1. User-centered language: Write for the person using the feature, not developers implementing it\r\n2. Keep implementation flexibility: describe the expected outcome and leave room for technical design choices\r\n3. Testability first: Every criterion should have a clear pass\u002Ffail condition\r\n4. Scenarios over bullets: Gherkin format (Given\u002FWhen\u002FThen) makes criteria unambiguous\r\n5. Keep it focused: One user story = one user goal; split large features into smaller stories\r\n",{"name":5,"description":7,"argument-hint":51},"Requirement to write as a User Story","main","1f4cad1bec73e18ff3c76ad481916b391d48a555","skills\u002Fmfse-user-stories-writing",1,"https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory","https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering","https:\u002F\u002Fmicheleferracin.it","MFSE Resources for software engineering","2026-08-25 21:54:40",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add MFSoftwareEngineering\u002Fmfse-softwarefactory --skill mfse-user-stories-writing",{"tool":67,"command":68},"bunx","bunx skills add MFSoftwareEngineering\u002Fmfse-softwarefactory --skill mfse-user-stories-writing",{"tool":70,"command":71},"pnpm","pnpm dlx skills add MFSoftwareEngineering\u002Fmfse-softwarefactory --skill mfse-user-stories-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fmfse-user-stories-writing\u002FSKILL.md",true,[75,81,85,91,95],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Fuser-story-template-acceptance-criteria.md","ASSET","资产文件",1658,"https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fmfse-user-stories-writing\u002Fassets\u002Fuser-story-template-acceptance-criteria.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"assets\u002Fuser-story-template-descrption.md",154,"https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fmfse-user-stories-writing\u002Fassets\u002Fuser-story-template-descrption.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"examples.md","REFERENCE","参考文档",3252,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fhoneydew-ai\u002Fhoneydew-ai-coding-agents-plugins\u002Fskills\u002Fmetric-creation\u002Fexamples.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"reference.md",4327,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fhoneydew-ai\u002Fhoneydew-ai-coding-agents-plugins\u002Fskills\u002Fmetric-creation\u002Freference.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002FREFERENCE.md",196,"https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fmfse-user-stories-writing\u002Freferences\u002FREFERENCE.md",[100,118,129,149,164,183],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":46},"01M6CX7YHWT41CJKQD6SNXFJV6","to-prd","Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fswe\u002Fto-prd\u002FSKILL.md",[106],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[108,109,110,111,112,113,114,115,116,117],"prd","to prd","publish","just","interview","Synthesis","issue","tracker","conversation","project",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":46},"01M6CX7W1GG7MGWBJVXYK31KVR","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.","https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fswe\u002Fto-issues\u002FSKILL.md",[],[125,126,127,108,128,114,115,117],"to issues","issues","spec","plan",{"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":138,"publishedAt":46},"01M6CX7NHQG2YFVPTN4B0KZCBB","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fswe\u002Ftdd\u002FSKILL.md",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",[131,139,140,141,142,143,33,144,41,145,146,147,148],"refactor","integration","first","integration tests","development","fix","red-green-refactor","build","green","test",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":46},"01M6CX7KM38DT59GBJE5CAWJ87","grill-with-docs","A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.","https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fswe\u002Fgrill-with-docs\u002FSKILL.md",[],[156,157,158,159,160,161,128,162,163,112],"docs","grill with docs","grill","glossary","design","go","sharpen","adr",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":46},"01M6CX7GXFJPQW7E9CKAYB3V6A","domain-modeling","Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.","https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fswe\u002Fdomain-modeling\u002FSKILL.md",[],[171,172,146,173,162,174,175,176,33,41,177,178,179,180,181,182,117],"domain","domain modeling","ubiquitous language","pin","model","decision","language","maintain","terminology","record","another skill","domain model",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":187,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":193,"publishedAt":46},"01M6CX7D46Q5V7Z61KJ3P460R0","owasp-kubernetes","OWASP Kubernetes Top 10 vulnerability knowledge base for identifying, assessing, and remediating security risks in Kubernetes environments - Brought to you by MFSoftwareEngineering\u002Fmfse-softwarefactory","CC-BY-SA-4.0","https:\u002F\u002Fgithub.com\u002FMFSoftwareEngineering\u002Fmfse-softwarefactory\u002Fblob\u002Fmain\u002Fskills\u002Fowasp-kubernetes\u002FSKILL.md",[190],{"categoryNo":191,"categoryName":192,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[194,195,196,197,198,199,200,201,202,117],"owasp kubernetes","kubernetes","owasp","security","https","vulnerability","knowledge","base","knowledge base"]