requirements-analysis
starsforks
How to install requirements-analysis?
omnigentx/jarvis/requirements-analysis
$npx -y skills add omnigentx/jarvis --skill requirements-analysisRESERVED — Future BA role. Guide for gathering, analyzing, and documenting business requirements. Covers stakeholder analysis, use cases, and acceptance criteria.
SKILL.md
| 1 | # Requirements Analysis (BA) |
| 2 | |
| 3 | > **⚠️ RESERVED:** This skill is prepared for the future BA role. Not currently in use. |
| 4 | |
| 5 | ## Purpose |
| 6 | |
| 7 | Guide the Business Analyst role in: |
| 8 | - Gathering and clarifying requirements from stakeholders |
| 9 | - Translating business needs into technical specifications |
| 10 | - Writing acceptance criteria |
| 11 | - Managing scope and priorities |
| 12 | |
| 13 | ## Requirements Process |
| 14 | |
| 15 | ### 1. Stakeholder Analysis |
| 16 | - Identify all stakeholders and their interests |
| 17 | - Understand business goals and constraints |
| 18 | - Map relationships between stakeholders |
| 19 | |
| 20 | ### 2. Requirements Gathering |
| 21 | - Ask open-ended questions to understand the "why" |
| 22 | - Document user stories: "As a [role], I want [action] so that [benefit]" |
| 23 | - Identify assumptions and constraints |
| 24 | - Prioritize: Must-have vs. Nice-to-have (MoSCoW method) |
| 25 | |
| 26 | ### 3. Acceptance Criteria |
| 27 | For each requirement, define: |
| 28 | - **Given** [precondition] |
| 29 | - **When** [action] |
| 30 | - **Then** [expected result] |
| 31 | |
| 32 | ### 4. Gap Analysis |
| 33 | - Compare current state vs. desired state |
| 34 | - Identify missing capabilities |
| 35 | - Estimate effort and impact |
| 36 | |
| 37 | ### 5. Documentation |
| 38 | - Requirements specification document |
| 39 | - Use case diagrams |
| 40 | - Process flow diagrams |
| 41 | - Traceability matrix |
| 42 | |
| 43 | ## Quality Checks |
| 44 | |
| 45 | - Is each requirement **testable**? |
| 46 | - Is each requirement **unambiguous**? |
| 47 | - Are requirements **complete** (no gaps)? |
| 48 | - Are there any **contradictions**? |
| 49 | - Is the **scope** clearly bounded? |
| 50 | |
| 51 | ## In Meeting Context |
| 52 | |
| 53 | As BA in a meeting: |
| 54 | - Present requirements clearly with acceptance criteria |
| 55 | - Validate that DEV's implementation matches requirements |
| 56 | - Clarify ambiguities when team has questions |
| 57 | - Flag scope creep early |
People who liked this also viewed
6 picksType
- lark-workflow-meeting-summary会议纪要整理工作流：汇总指定时间范围内的会议纪要并生成结构化报告。当用户需要整理会议纪要、生成会议周报、回顾一段时间内的会议内容时使用。SkillsJul 2026
- lark-workflow-standup-report日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。SkillsJul 2026
- lark-approval飞书审批：查询和处理审批待办/已办/实例，搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务；非审批类待办走 lark-task。不负责创建审批定义；三方审批定义不走原生提单。SkillsJul 2026
- lark-okr飞书 OKR：管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责：待办任务管理（lark-task）、日程/会议安排（lark-calendar）、绩效评估SkillsJul 2026
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.SkillsJul 2026
- simpleInvoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimized for fast, focused decision-making. Gen AgentSkillsMar 2026
