Complete professional methodology for software and business requirements gathering.
Business Requirements Analyst is a Skill for Claude AI that implements a professional requirements gathering methodology, combining:
- β Business Analysis (BABOK) - Professional business analysis standards.
- β Design Thinking - User-centered idea validation.
- β Lean Startup - Rapid vision and MVP validation.
- β SDD (Specification-Driven Development) - AI-optimized technical documentation using EARS and ADR.
A master requirements document that includes:
- π Business Vision (Problem, value proposition, KPIs).
- π₯ Stakeholders & Personas.
- π Business Processes (Detailed flows).
- π Functional Requirements (EARS Syntax) - FR-001, FR-002...
- π Non-Functional Requirements (Performance, security, scalability).
- π Data Model (Auto-ERD) - Entites, relationships, and Mermaid diagrams.
- π Integrations (APIs, external services).
- π Architecture Decision Records (ADR).
- π Traceability Matrix (Cumulative tagging from business to code).
- βοΈ Quality Gates (Automated maturity scoring).
β οΈ Risks & Assumptions.- πΊοΈ Roadmap in Phases (MVP, Phase 2, Phase 3...).
This version includes advanced automation and traceability features inspired by the aidoc-flow-framework:
- π§ Smart Discovery: Automatically scans provided documents, images, and previous context to avoid repetitive questions.
- π EARS Methodology: Standardized syntax to eliminate ambiguity in functional requirements.
- οΏ½ ADR Support: Document the "Why" behind critical technical choices.
- π Cumulative Traceability: Embedded tags that create an audit trail from the Business Goal to the implementation code.
- π Mermaid.js Integration: Automatically generates visual Entity-Relationship Diagrams (ERD).
npx skills add gmdaos/business-requirements-analyst# Clone the repository
git clone https://github.com/gmdaos/business-requirements-analyst.git
# Copy to your project
cp -r business-requirements-analyst/business-requirements-analyst .agent/skills/- Download the business-requirements-analyst.skill file.
- Go to Settings β Features β Skills.
- Click on Upload Custom Skill.
- Select the
.skillfile.
import anthropic
client = anthropic.Anthropic(api_key="your-api-key")
# Upload the Skill
with open("business-requirements-analyst.skill", "rb") as f:
skill = client.skills.create(file=f)
# Use in conversation
message = client.messages.create(
model="claude-3-5-sonnet-20241022",
extra_headers={
"anthropic-beta": "code-execution-2025-08-25,skills-2025-10-02,files-api-2025-04-14"
},
tools=[{
"type": "code_execution_2025_08_25",
"container": {
"skill_id": "business-requirements-analyst"
}
}],
messages=[{
"role": "user",
"content": "Help me document my project"
}]
)The Skill activates automatically when:
- You mention "requirements gathering".
- You upload documents or images for analysis.
- You ask to "document a new project".
- You request "technical specifications" or "ADR".
- You need to "validate a business idea".
π€ User: "I need to document my food delivery app for home chefs. Here is a PDF with the concept."
π€ Claude (with active Skill): "Great! I'm your Business Requirements Analyst. To turn your idea into a production-ready blueprint, we'll follow this roadmap: Discovery β Vision β Processes β Specs β Data Model β Roadmap.
I've analyzed the PDF you uploaded. I've already captured the problem statement and the 3 types of users. Let's focus on the gaps:
- What specific business rules apply to the delivery fee calculation?
- Are there any specific architecture decisions (ADR) we should document regarding the payment gateway? ..."
This is a preview of the quality and structure generated by this setup:
Problem: Customers struggle to find diverse local food options with reliable, real-time tracking. Value Proposition: FastBite provides a unified marketplace with a high-performance delivery network and real-time GPS tracking.
- User places order via App.
- System validates payment.
- Restaurant accepts and prepares order.
- Courier is assigned and delivers.
| ID | Requirement | EARS Pattern | Traceability |
|---|---|---|---|
| FR-01 | WHEN the user confirms the order THE System shall initiate the payment process. | Event-Driven | @brd: BRD.01.01 |
| FR-02 | IF the payment fails THEN the System shall notify the user and allow a retry. | Unwanted Behavior | @brd: BRD.01.05 |
| FR-03 | WHILE the courier is in transit THE System shall update the GPS location every 5 seconds. | State-Driven | @brd: BRD.02.01 |
erDiagram
USER ||--o{ ORDER : places
RESTAURANT ||--o{ ORDER : receives
ORDER ||--o{ ORDER_ITEM : contains
ORDER ||--|| PAYMENT : has
COURIER ||--o{ ORDER : delivers
USER {
string id PK
string name
string email
}
ORDER {
string id PK
string status
float total_amount
timestamp created_at
}
COURIER {
string id PK
string vehicle_type
string current_lat
string current_lng
}
- ADR-001: PostgreSQL - Used for transactional integrity and ACID compliance.
- ADR-002: Stripe Integration - Used for PCI-DSS compliance and split payments.
- Maturity Evaluation: 100/100 (APPROVED)
- Cumulative Tags: Found
@brd,@prd,@ears.
SKILL.md- Core methodology and logic.references/- Detailed technical deep-dives.ears-methodology.md- Standard for non-ambiguous requirements.traceability-guide.md- Connecting business to implementation code.adr-template.md- Format for recording architectural decisions.process-mapping.md- BPMN and flow techniques.data-modeling.md- Patterns and normalization.use-cases.md- Detailed use cases with templates.
assets/- Templates and resources.requirements-template.md- Master template with Quality Gates.
examples/- Reference projects.food-delivery-app.md- Complete documentation example.
For idea validation and discovery:
- Empathize with users.
- Define the problem.
- Ideate solutions.
- Prototype and test.
For professional documentation:
- Business requirements.
- Functional & Non-Functional requirements.
- Business rules.
- Stakeholders and processes.
For quick vision and validation:
- Business Model Canvas.
- MVP (Minimum Viable Product) definition.
- Key metrics.
- π Startups - Validate and document business ideas.
- πΌ Consultants - Create professional specs for clients.
- π¨βπ» Developers - Understand scope before quoting.
- π’ Product Managers - Document product roadmaps.
- π° Investors - Evaluate project feasibility.
- E-commerce / Marketplaces
- SaaS / Web Platforms
- Mobile Apps
- Enterprise Systems (ERP, CRM)
- APIs and Microservices
This Skill is designed to be platform-agnostic and works with any AI, Agent, or IDE that supports the .agent/skills (or similar) framework.
- Clone this repository.
- Link the
business-requirements-analystfolder to your environment's skill or agent directory (usually.agent/skills/or.agent/workflows/).
- Status: Fully Supported.
- Ensure your project has the
.agent/skills/structure and the folder is present there.
- Status: Pro, Max, Team, or Enterprise plan required.
- Enable Code Execution in your profile settings to allow the agent to read the methodology.
- Status: Compatible with any system supporting Anthropic Beta headers:
code-execution-2025-08-25skills-2025-10-02files-api-2025-04-14
Contributions are welcome!
- Fork the repository.
- Create a branch:
git checkout -b feature/new-feature. - Commit changes:
git commit -m 'Add new feature'. - Push:
git push origin feature/new-feature. - Open a Pull Request.
This project is licensed under the MIT License - see the LICENSE file for details.
Developed by Gabriel Mayon
Based on:
- BABOK (Business Analysis Body of Knowledge)
- Design Thinking (IDEO, Stanford d.school)
- Lean Startup (Eric Ries)
- EARS (Easy Approach to Requirements Syntax)
- π Issues: GitHub Issues
- π§ Email: gmgmdaos@gmail.com
β If this Skill was useful, give it a star on GitHub!