Back to skills
SKILL.md
Business Context
ASecurity--- name: business-context description: Understand and apply business requirements, user needs, and market context to development decisions ---
- 33 stars
- 0 votes
- 0 copies
- 1 view
- Added February 10, 2026
Works with
Security analysis
100/100npx -y skills add lovedragonball/power-ranger-toolkit --skill business-context --agent claude-codeAre you the author of Business Context?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lovedragonball-business-context)# πΌ 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
Attribution
Comments
Loading commentsβ¦