--- name: business-context description: Understand and apply business requirements, user needs, and market context to development decisions ---
Scanned 2/12/2026
Install to Claude Code
npx -y skills add lovedragonball/power-ranger-toolkit --skill business-context --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Business Context?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lovedragonball-business-context)More formats (shields.io, HTML) on the badges page.
# 💼 Business Context Skill
---
name: business-context
description: Understand and apply business requirements, user needs, and market context to development decisions
---
## 🎯 Purpose
This skill helps understand business requirements, user personas, market positioning, and translate them into technical decisions.
## 📋 When to Use
- Starting a new project
- Making architecture decisions
- Prioritizing features
- Understanding user requirements
- Creating MVP specifications
## 🔧 Capabilities
### 1. Requirements Analysis
- Extract functional requirements from natural language
- Identify non-functional requirements (performance, security, scalability)
- Map user stories to technical tasks
### 2. User Persona Understanding
- Define target user demographics
- Understand user pain points
- Map user journeys
### 3. Market Context
- Analyze competitor features
- Identify market gaps
- Suggest differentiating features
### 4. MVP Definition
- Prioritize core features
- Define minimum viable scope
- Create phased roadmap
## 📝 Process
```
1. GATHER: Collect business requirements
- What problem are we solving?
- Who is the target user?
- What are the success metrics?
2. ANALYZE: Break down requirements
- Core features (must-have)
- Nice-to-have features
- Future considerations
3. TRANSLATE: Convert to technical specs
- Data models needed
- API endpoints required
- UI/UX requirements
4. PRIORITIZE: Create implementation order
- Phase 1: MVP core
- Phase 2: Essential additions
- Phase 3: Nice-to-haves
```
## 💡 Key Questions to Ask
| Category | Questions |
|----------|-----------|
| **Users** | Who uses this? What's their skill level? |
| **Problem** | What pain point does this solve? |
| **Value** | Why would someone pay for this? |
| **Competition** | What alternatives exist? |
| **Success** | How do we measure success? |
## 📊 Output Format
```markdown
## Business Requirements Summary
### Target Users
- Primary: [description]
- Secondary: [description]
### Core Problem
[Problem statement]
### Success Metrics
- [ ] Metric 1
- [ ] Metric 2
### Feature Priority
| Priority | Feature | Rationale |
|----------|---------|-----------|
| P0 | ... | ... |
| P1 | ... | ... |
| P2 | ... | ... |
```
## 🔗 Related Skills
- `project-setup` - After understanding context
- `api-design` - Designing APIs based on requirements
- `documentation` - Documenting business logic
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!