aj-geddes/claude-code-bmad-skills▌
9 approved skills in this repository
ux-designer
Frontend
Role: Phase 2/3 - Planning and Solutioning UX specialist
product-manager
Productivity
Comprehensive requirements and planning specialist for PRDs, tech specs, feature prioritization, and epic breakdown. \n \n Creates Product Requirements Documents (PRDs) for complex projects and lightweight Technical Specifications for simpler ones, with structured functional and non-functional requirements \n Prioritizes features using MoSCoW, RICE scoring, and Kano frameworks; includes validation scripts and templates to ensure requirements are testable, measurable, and traceable \n Breaks down
scrum-master
Productivity
Role: Phase 4 - Implementation Planning specialist
developer
Productivity
Role: Phase 4 - Implementation (Execution) specialist
bmad-orchestrator
Productivity
Purpose: Core orchestrator for the BMAD Method (Breakthrough Method for Agile AI-Driven Development), managing workflows, tracking status, and routing users through structured development phases.
creative-intelligence
Productivity
Role: Creative Intelligence System specialist
business-analyst
Productivity
Product discovery and requirements analysis specialist for creating product briefs and validating problem-solution fit. \n \n Conducts structured stakeholder interviews, market research, and competitive analysis using frameworks like 5 Whys and Jobs-to-be-Done \n Generates comprehensive product briefs with problem definition, target users, solution scope, success metrics, and risk assessment \n Supports brainstorming sessions, requirements gathering, and discovery workflows with templates and va
builder
Frontend
Role: Builder Module specialist
system-architect
Productivity
Designs system architecture with justified tech stacks, component interfaces, and systematic non-functional requirement coverage. \n \n Transforms requirements into complete technical architecture by extracting functional and non-functional requirements, identifying architectural drivers, and selecting appropriate patterns (monolith, microservices, serverless, layered) \n Maps every NFR category (performance, scalability, security, reliability, maintainability, availability) to specific architec