[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMEQGFCZTP823ZJSYSA922":3,"skill-same:01M7EMEQGFCZTP823ZJSYSA922":47},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMEQGFCZTP823ZJSYSA922","business-analyst",null,"Perform business analysis — requirements gathering, process mapping, gap analysis, and stakeholder-ready documentation.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-business-analyst\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: business-analyst\ndescription: Perform business analysis — requirements gathering, process mapping, gap analysis, and stakeholder-ready documentation.\ncategory: business-marketing\n---\n\n## Overview\n\nBusiness analysts bridge business needs and solutions: eliciting requirements, mapping processes, analyzing gaps, and documenting specifications that teams can build from. This skill covers the BA toolkit — stakeholder analysis, requirements elicitation, process modeling, and the documentation standards that prevent expensive misunderstandings.\n\n## When to use\n\n- Gathering requirements for a new system or feature\n- Mapping and improving a business process\n- Writing BRDs, FRDs, or user stories with acceptance criteria\n- Analyzing gaps between current and desired state\n- Evaluating build-vs-buy or vendor options\n- Preparing stakeholder presentations on findings\n\n- Evaluating build-vs-buy decisions\n- Documenting as-is processes before automation\n- Facilitating prioritization across competing stakeholders\n## Core concepts\n\n**Stakeholder analysis.** Map stakeholders by influence and interest. High-influence stakeholders need active management; high-interest ones need information. Missing a key stakeholder early guarantees rework later.\n\n**Requirements elicitation.** Interviews, workshops, observation, document analysis, surveys. The 5 Whys get past stated wants to real needs. Distinguish business requirements (why), stakeholder requirements (what), and solution requirements (how, functional + non-functional).\n\n**SMART requirements.** Specific, Measurable, Achievable, Relevant, Time-bound — or at minimum: unambiguous, testable, and traceable. \"The system should be fast\" is not a requirement; \"95th percentile response under 2 seconds at 100 concurrent users\" is.\n\n**Process modeling.** As-is vs. to-be flows (swimlane diagrams showing handoffs between roles), pain points marked on the as-is, improvements designed into the to-be. Every handoff is a failure point — minimize them.\n\n**Gap analysis.** Current state → desired state → the gap → options to close it → recommendation with costs\u002Fbenefits\u002Frisks. Structured, comparable, decision-ready.\n\n**Traceability.** Every requirement traces to a business need and forward to a test case. Untraceable requirements are how scope creep and untested features happen.\n\n\n**RACI for requirements.** For each requirement or deliverable, define who is Responsible, Accountable, Consulted, and Informed. Requirement disputes usually trace to unclear accountability — RACI assigned at elicitation time prevents the \"I thought you were handling that\" failure mode.\n\n**Non-functional requirements (NFRs).** Performance, security, scalability, usability, accessibility, compliance, and maintainability. NFRs are where projects silently fail: the system works but is too slow, insecure, or unusable. Elicit NFRs with the same rigor as functional ones, and quantify every one.\n\n**MoSCoW prioritization.** Must have (non-negotiable for go-live) → Should have (important, not critical) → Could have (nice if time) → Won't have (explicitly out of scope).\nThe power is in the Won't list — explicit exclusion prevents scope creep disguised as clarification.\nRevisit MoSCoW at each phase gate; priorities legitimately shift as learning happens.\n**Traceability.** Link every requirement to its source (stakeholder, regulation, business goal) and to its test.\nWhen requirements change — and they will — traceability shows exactly what else is affected.\nTools help, but even a simple matrix beats tribal memory.\n**Gap analysis.** Current state → future state → the gap between them, itemized as changes required (process, people, technology).\nMost failed transformations skipped honest gap analysis and discovered the gaps mid-implementation.\n## Practical workflow\n\n1. **Define scope and stakeholders.** What's in\u002Fout, who's affected, who decides. Get scope sign-off in writing before elicitation.\n2. **Elicit requirements.** Run structured interviews and workshops. Ask about the current process, pain points, and what \"good\" looks like — not just feature requests. Observe the work being done; people omit steps they do unconsciously.\n3. **Model the processes.** Draw as-is swimlanes. Validate with the people who do the work. Design to-be with pain points addressed. Get sign-off on both.\n4. **Document specifications.** BRD (business need, scope, success criteria), functional requirements (numbered, testable), non-functional requirements (performance, security, usability, compliance), user stories with acceptance criteria for agile teams.\n5. **Validate and prioritize.** Walk through requirements with stakeholders. Prioritize with MoSCoW (Must\u002FShould\u002FCould\u002FWon't). Get formal sign-off — this is your change-control baseline.\n6. **Support delivery.** Answer builder questions, manage change requests (impact-assess every change), verify delivered work against acceptance criteria.\n\n**User story format:** As a [role], I want [capability], so that [benefit]. Acceptance criteria in Given\u002FWhen\u002FThen. Each story independently testable and sized for one sprint.\n\n\n**Workshop facilitation format (90 minutes):** 10 min framing and ground rules → 20 min current-state painstorm (silent writing, then share) → 25 min future-state vision (what does good look like?) → 20 min prioritization (dot voting on improvements) → 15 min next steps and owners. Send pre-reads; capture decisions live on a shared screen.\n\n**Requirements document structure:** background and objectives → scope (in and out) → stakeholders → functional requirements (numbered, testable) → non-functional requirements (quantified) → assumptions and constraints → acceptance criteria → glossary.\nNumber every requirement (REQ-001) — unnumbered requirements cannot be tracked, tested, or changed systematically.\n**Sign-off ritual:** walk stakeholders through requirements → capture objections live → revise → get explicit written sign-off.\nVerbal agreement evaporates; written sign-off (even an email) anchors accountability.\n## Common pitfalls\n\n- **Solutioneering.** Jumping to solutions before understanding the problem. Elicit needs, not features.\n- **Missing stakeholders.** The person who wasn't consulted becomes the person who blocks go-live.\n- **Vague requirements.** \"User-friendly\", \"robust\", \"flexible\" — untestable words that cause disputes. Quantify everything.\n- **No scope baseline.** Without signed-off scope, every new request feels reasonable and the project never ends.\n- **Skipping the as-is.** Designing to-be without understanding current reality produces elegant solutions to wrong problems.\n- **Documentation nobody reads.** 200-page BRDs gather dust. Right-size docs for the audience; visual models beat paragraphs.\n- **Weak change control.** \"Small\" changes accumulate into scope explosions. Impact-assess and approve every change.\n- **Accepting the first stated requirement.** Stakeholders describe solutions (\"we need a dashboard\") not needs (\"we need to spot at-risk accounts weekly\"). Keep asking why until you reach the real need.\n- **No definition of done.** Requirements without acceptance criteria are never truly finished. Every requirement ships with testable criteria.\n- **Gold-plating.** Adding nice-to-have requirements nobody asked for. Every requirement traces to a stakeholder need or it gets cut.\n- **Analysis paralysis.** Perfecting documentation while the project stalls. Timebox analysis; ship the 80% version and iterate.\n","## Overview\n\nBusiness analysts bridge business needs and solutions: eliciting requirements, mapping processes, analyzing gaps, and documenting specifications that teams can build from. This skill covers the BA toolkit — stakeholder analysis, requirements elicitation, process modeling, and the documentation standards that prevent expensive misunderstandings.\n\n## When to use\n\n- Gathering requirements for a new system or feature\n- Mapping and improving a business process\n- Writing BRDs, FRDs, or user stories with acceptance criteria\n- Analyzing gaps between current and desired state\n- Evaluating build-vs-buy or vendor options\n- Preparing stakeholder presentations on findings\n\n- Evaluating build-vs-buy decisions\n- Documenting as-is processes before automation\n- Facilitating prioritization across competing stakeholders\n## Core concepts\n\n**Stakeholder analysis.** Map stakeholders by influence and interest. High-influence stakeholders need active management; high-interest ones need information. Missing a key stakeholder early guarantees rework later.\n\n**Requirements elicitation.** Interviews, workshops, observation, document analysis, surveys. The 5 Whys get past stated wants to real needs. Distinguish business requirements (why), stakeholder requirements (what), and solution requirements (how, functional + non-functional).\n\n**SMART requirements.** Specific, Measurable, Achievable, Relevant, Time-bound — or at minimum: unambiguous, testable, and traceable. \"The system should be fast\" is not a requirement; \"95th percentile response under 2 seconds at 100 concurrent users\" is.\n\n**Process modeling.** As-is vs. to-be flows (swimlane diagrams showing handoffs between roles), pain points marked on the as-is, improvements designed into the to-be. Every handoff is a failure point — minimize them.\n\n**Gap analysis.** Current state → desired state → the gap → options to close it → recommendation with costs\u002Fbenefits\u002Frisks. Structured, comparable, decision-ready.\n\n**Traceability.** Every requirement traces to a business need and forward to a test case. Untraceable requirements are how scope creep and untested features happen.\n\n\n**RACI for requirements.** For each requirement or deliverable, define who is Responsible, Accountable, Consulted, and Informed. Requirement disputes usually trace to unclear accountability — RACI assigned at elicitation time prevents the \"I thought you were handling that\" failure mode.\n\n**Non-functional requirements (NFRs).** Performance, security, scalability, usability, accessibility, compliance, and maintainability. NFRs are where projects silently fail: the system works but is too slow, insecure, or unusable. Elicit NFRs with the same rigor as functional ones, and quantify every one.\n\n**MoSCoW prioritization.** Must have (non-negotiable for go-live) → Should have (important, not critical) → Could have (nice if time) → Won't have (explicitly out of scope).\nThe power is in the Won't list — explicit exclusion prevents scope creep disguised as clarification.\nRevisit MoSCoW at each phase gate; priorities legitimately shift as learning happens.\n**Traceability.** Link every requirement to its source (stakeholder, regulation, business goal) and to its test.\nWhen requirements change — and they will — traceability shows exactly what else is affected.\nTools help, but even a simple matrix beats tribal memory.\n**Gap analysis.** Current state → future state → the gap between them, itemized as changes required (process, people, technology).\nMost failed transformations skipped honest gap analysis and discovered the gaps mid-implementation.\n## Practical workflow\n\n1. **Define scope and stakeholders.** What's in\u002Fout, who's affected, who decides. Get scope sign-off in writing before elicitation.\n2. **Elicit requirements.** Run structured interviews and workshops. Ask about the current process, pain points, and what \"good\" looks like — not just feature requests. Observe the work being done; people omit steps they do unconsciously.\n3. **Model the processes.** Draw as-is swimlanes. Validate with the people who do the work. Design to-be with pain points addressed. Get sign-off on both.\n4. **Document specifications.** BRD (business need, scope, success criteria), functional requirements (numbered, testable), non-functional requirements (performance, security, usability, compliance), user stories with acceptance criteria for agile teams.\n5. **Validate and prioritize.** Walk through requirements with stakeholders. Prioritize with MoSCoW (Must\u002FShould\u002FCould\u002FWon't). Get formal sign-off — this is your change-control baseline.\n6. **Support delivery.** Answer builder questions, manage change requests (impact-assess every change), verify delivered work against acceptance criteria.\n\n**User story format:** As a [role], I want [capability], so that [benefit]. Acceptance criteria in Given\u002FWhen\u002FThen. Each story independently testable and sized for one sprint.\n\n\n**Workshop facilitation format (90 minutes):** 10 min framing and ground rules → 20 min current-state painstorm (silent writing, then share) → 25 min future-state vision (what does good look like?) → 20 min prioritization (dot voting on improvements) → 15 min next steps and owners. Send pre-reads; capture decisions live on a shared screen.\n\n**Requirements document structure:** background and objectives → scope (in and out) → stakeholders → functional requirements (numbered, testable) → non-functional requirements (quantified) → assumptions and constraints → acceptance criteria → glossary.\nNumber every requirement (REQ-001) — unnumbered requirements cannot be tracked, tested, or changed systematically.\n**Sign-off ritual:** walk stakeholders through requirements → capture objections live → revise → get explicit written sign-off.\nVerbal agreement evaporates; written sign-off (even an email) anchors accountability.\n## Common pitfalls\n\n- **Solutioneering.** Jumping to solutions before understanding the problem. Elicit needs, not features.\n- **Missing stakeholders.** The person who wasn't consulted becomes the person who blocks go-live.\n- **Vague requirements.** \"User-friendly\", \"robust\", \"flexible\" — untestable words that cause disputes. Quantify everything.\n- **No scope baseline.** Without signed-off scope, every new request feels reasonable and the project never ends.\n- **Skipping the as-is.** Designing to-be without understanding current reality produces elegant solutions to wrong problems.\n- **Documentation nobody reads.** 200-page BRDs gather dust. Right-size docs for the audience; visual models beat paragraphs.\n- **Weak change control.** \"Small\" changes accumulate into scope explosions. Impact-assess and approve every change.\n- **Accepting the first stated requirement.** Stakeholders describe solutions (\"we need a dashboard\") not needs (\"we need to spot at-risk accounts weekly\"). Keep asking why until you reach the real need.\n- **No definition of done.** Requirements without acceptance criteria are never truly finished. Every requirement ships with testable criteria.\n- **Gold-plating.** Adding nice-to-have requirements nobody asked for. Every requirement traces to a stakeholder need or it gets cut.\n- **Analysis paralysis.** Perfecting documentation while the project stalls. Timebox analysis; ship the 80% version and iterate.\n",{"name":5,"category":24,"description":7},"business-marketing","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-business-analyst",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill business-analyst",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill business-analyst",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill business-analyst","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-business-analyst\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]