Requirements Analysis
RESERVED — Future BA role. Guide for gathering, analyzing, and documenting business requirements. Covers stakeholder analysis, use cases, and acceptance criteria.
Install
$ agentstack add skill-omnigentx-jarvis-requirements-analysis ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Requirements Analysis (BA)
> ⚠️ RESERVED: This skill is prepared for the future BA role. Not currently in use.
Purpose
Guide the Business Analyst role in:
- Gathering and clarifying requirements from stakeholders
- Translating business needs into technical specifications
- Writing acceptance criteria
- Managing scope and priorities
Requirements Process
1. Stakeholder Analysis
- Identify all stakeholders and their interests
- Understand business goals and constraints
- Map relationships between stakeholders
2. Requirements Gathering
- Ask open-ended questions to understand the "why"
- Document user stories: "As a [role], I want [action] so that [benefit]"
- Identify assumptions and constraints
- Prioritize: Must-have vs. Nice-to-have (MoSCoW method)
3. Acceptance Criteria
For each requirement, define:
- Given [precondition]
- When [action]
- Then [expected result]
4. Gap Analysis
- Compare current state vs. desired state
- Identify missing capabilities
- Estimate effort and impact
5. Documentation
- Requirements specification document
- Use case diagrams
- Process flow diagrams
- Traceability matrix
Quality Checks
- Is each requirement testable?
- Is each requirement unambiguous?
- Are requirements complete (no gaps)?
- Are there any contradictions?
- Is the scope clearly bounded?
In Meeting Context
As BA in a meeting:
- Present requirements clearly with acceptance criteria
- Validate that DEV's implementation matches requirements
- Clarify ambiguities when team has questions
- Flag scope creep early
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: omnigentx
- Source: omnigentx/jarvis
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.