How do I install the Business Context skill?

Run npx skillmds add majiayu000/business-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Business Context safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Business Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Business Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Business Context?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Business Context by majiayu000 — Agent Skill

Name: Business Context
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

💼 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

## 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

---name: business-contextdescription: This skill helps understand business requirements, user personas, market positioning, and translate them into technical decisions.--- # 💼 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

Frequently asked questions