Claude-skill-registry business-context

๐Ÿ’ผ Business Context Skill

install
source ยท Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code ยท Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/business-context" ~/.claude/skills/majiayu000-claude-skill-registry-business-context && rm -rf "$T"
manifest: skills/data/business-context/SKILL.md
source content

๐Ÿ’ผ 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

CategoryQuestions
UsersWho uses this? What's their skill level?
ProblemWhat pain point does this solve?
ValueWhy would someone pay for this?
CompetitionWhat alternatives exist?
SuccessHow 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