aj-geddes/claude-code-bmad-skills
3 skills3.4k installs1.3k starsGitHub
Install
npx skills add https://github.com/aj-geddes/claude-code-bmad-skillsSkills in this repo
1Business AnalystBusiness Analyst is a BMAD-aligned reference skill that equips your coding agent to conduct product discovery and requirements analysis like a business analyst—not jump straight to implementation tickets. Solo builders use it when they need to clarify who the user is, what job they hire the product for, and which constraints matter before Validate or Build work hardens. The guide centers interview frameworks including 5 Whys for root causes and Jobs-to-be-Done for motivation-level insight, plus question techniques, a staged discovery process, documentation habits, and anti-patterns. It fits agentic workflows where one person plays PM, engineer, and support. Complexity is intermediate because effective discovery depends on judgment and follow-up questions. Deliverables are structured findings and requirements-ready notes rather than shipped code.2kinstalls2Product Managerproduct-manager is a reference-oriented agent skill from the BMAD-style skills family that helps solo builders act as their own PM when scope threatens to swallow the calendar. It centers on MoSCoW—Must, Should, Could, Won't—and gives concrete tests for each bucket so agent-assisted requirements lists do not become everything-is-P0 soup. The material suits MVP definition on a fixed deadline, trimming a SaaS v1 before you open Cursor on the codebase, and documenting what is explicitly deferred so future-you does not relitigate scope mid-sprint. Because it is framework guidance rather than a ticket integration, it pairs naturally with brainstorming and writing-plans skills: you classify work here, then hand an approved slice to implementation skills. It is less about analytics dashboards and more about defensible prioritization when you are the only person saying no to features.895installs3System ArchitectSystem Architect is a BMAD-style reference skill that equips solo and indie builders—and their coding agents—with structured architectural decision material rather than ad-hoc stack debates. The readme catalogs application patterns such as monolith and modular monolith, when each fits small teams and MVPs, and the pros and cons around scaling, coupling, and operational simplicity. It extends into pattern selection criteria, NFR mapping, technology stack selection, trade-off analysis, and component design principles so conversations stay evidence-based. Use it during validation when you are still proving the idea and defining scope, and again during build and ship when you refine services, data boundaries, and performance expectations. The skill does not deploy infrastructure or generate code by itself; it shapes the spec your agent should follow. Intermediate complexity assumes you can read architecture trade-offs and apply them to a concrete product shape.566installs